From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH 3/6] Show layer description with newlines in layer detail
Date: Tue, 20 Feb 2018 16:45:55 +1300 [thread overview]
Message-ID: <20180220034558.14341-3-paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <20180220034558.14341-1-paul.eggleton@linux.intel.com>
A lot of people enter line breaks in their layer descriptions hoping
that these will show up in the layer description, but of course since
they are being displayed as part of an HTML document, they don't by
default. Use a style in the description paragraph to ensure that they
do.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
templates/layerindex/detail.html | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/templates/layerindex/detail.html b/templates/layerindex/detail.html
index 0747421..3081ef3 100644
--- a/templates/layerindex/detail.html
+++ b/templates/layerindex/detail.html
@@ -76,9 +76,7 @@
<div class="row-fluid">
<div class="description span7">
- <p>
- {{ layeritem.description }}
- </p>
+ <p style="white-space: pre">{{ layeritem.description }}</p>
<p>
{% if layeritem.usage_url %}
<span class="label label-info">
--
2.14.3
next prev parent reply other threads:[~2018-02-20 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 3:45 [layerindex-web][PATCH 1/6] update.py: fix Ctrl+C behaviour Paul Eggleton
2018-02-20 3:45 ` [layerindex-web][PATCH 2/6] Add statistics page Paul Eggleton
2018-02-20 3:45 ` Paul Eggleton [this message]
2018-02-20 3:45 ` [layerindex-web][PATCH 4/6] requirements.txt: add missing dependencies Paul Eggleton
2018-02-20 3:45 ` [layerindex-web][PATCH 5/6] requirements.txt: update some dependency versions Paul Eggleton
2018-02-20 3:45 ` [layerindex-web][PATCH 6/6] README: update " Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180220034558.14341-3-paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.