From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "R. Michael Weylandt" <michael.weylandt@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Prepare release 8.2.6
Date: Thu, 17 Apr 2014 21:58:47 +0200 [thread overview]
Message-ID: <87mwfj20eg.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ha65jvb6.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 07 Apr 2014 12:19:41 +0200")
Hi Michael and Nicolas,
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> It needs to be discussed, but I tend to think that it would be better to
> allow newlines characters in macros and inline babel calls, even if it
> means replacing them with a space when needed.
I've given this another thought and I agree here.
Prevent line breaks here would look weird, and adding
the space when needed looks easy enough (at least,
it's easy enough to suppose it is easy... not sure
about the details.)
--
Bastien
next prev parent reply other threads:[~2014-04-17 19:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 6:37 Prepare release 8.2.6 Bastien
2014-04-04 9:05 ` Sebastien Vauban
2014-04-04 11:51 ` Michael Weylandt
2014-04-05 16:41 ` R. Michael Weylandt
2014-04-05 19:18 ` Nicolas Goaziou
2014-04-07 1:48 ` R. Michael Weylandt
2014-04-07 10:19 ` Nicolas Goaziou
2014-04-17 19:58 ` Bastien [this message]
2014-04-04 14:32 ` Michael Weylandt
2014-04-05 16:45 ` R. Michael Weylandt
2014-04-05 19:27 ` Nicolas Goaziou
2014-04-05 21:48 ` York Zhao
2014-04-06 17:51 ` R. Michael Weylandt
2014-04-06 18:03 ` Nicolas Goaziou
2014-04-11 2:43 ` Eric Schulte
2014-04-13 17:02 ` R. Michael Weylandt
2014-04-17 6:26 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2014-04-03 7:53 Bastien
2014-04-03 9:17 ` Alan Schmitt
2014-04-03 10:13 ` KDr2
2014-04-03 11:47 ` Rainer M Krug
2014-04-03 11:47 ` Rainer M Krug
2014-04-18 12:04 ` Bastien
2014-04-28 13:40 ` Rainer M Krug
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=87mwfj20eg.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=michael.weylandt@gmail.com \
--cc=n.goaziou@gmail.com \
/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).