From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Li DebugFan <debugfanli@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: No explicit way to add blank lines to the beginning or end of example or source blocks
Date: Sat, 29 Apr 2017 14:34:24 +0200 [thread overview]
Message-ID: <87r30bxui7.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALtqGOaiW5a+0YQmEkaKzAcZAiseZJkwVGXViProQa3QQgG_ew@mail.gmail.com> (Li DebugFan's message of "Thu, 6 Apr 2017 14:27:40 +0800")
Hello,
Li DebugFan <debugfanli@gmail.com> writes:
> No explicit way to add blank lines to the beginning or end of example or
> source blocks.
> For example: describing HTTP header:
> -------------------------------------------------------------------
> HTTP header consists of colon-separated name-value pairs,
> and terminated by a CRLF character sequence, e.g.:
>
> #+BEGIN_EXAMPLE
> GET / HTTP/1.1
> Host: www.example.com
>
> #+END_EXAMPLE
>
> This is line break at the end of HTTP header.
> -------------------------------------------------------------------
> But the blank line at end of example block is not exported, and neither in
> src block,
> I check the source, and found it maybe because of the function
> `org-split-string',
> its description as follow:
> (defun org-split-string (string &optional separators)
> "Splits STRING into substrings at SEPARATORS.
> No empty strings are returned if there are matches at the beginning
> and end of string."
> ...)
> It means `org-split-string' will ignore all blank lines at the beginning
> and the end,
> but what if I need some blank lines in the beginning or the end?
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2017-04-29 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 6:27 No explicit way to add blank lines to the beginning or end of example or source blocks Li DebugFan
2017-04-29 12:34 ` Nicolas Goaziou [this message]
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r30bxui7.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=debugfanli@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).