From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Cc: Kaushal <kaushal.modi@gmail.com>
Subject: Re: Enforcing newlines in plain text export
Date: Sat, 27 Sep 2014 08:59:41 -0700 [thread overview]
Message-ID: <87iok99hqq.fsf@berkeley.edu> (raw)
In-Reply-To: CAFyQvY0KkSyts+FWc+bjaFuFLFbC4b32MxQRDCsWztcP0KZsXQ@mail.gmail.com
Hi Kaushal,
Kaushal <kaushal.modi@gmail.com> writes:
> I am requesting a consistent solution.
>
> If "//" at the end of a line inserts newline when exporting in all formats,
> then it should do the same when used in between a line too for ALL export
> formats.
>
> Example: #+TITLE: Line one // Line two
>
> I am simply trying to explain why we need another solution for the sake of
> consistency across all org exported formats.
Like I said, I agree that something like this would be useful; I
occasionally would like "\\" to have more general behavior, too.
Anyway, it seems worth discussing.
My point is that this would be a new feature, which is technically
*inconsistent* with the currently-documented behavior. Implementing it
would take some work and would involve breaking backward
compatibility. (At least in theory -- I don't know if anyone out there
relies on "\\" *not* being translated when it does not appear at the end
of a line, but someone might be.) So it's not something to be taken
lightly.
Does anyone know why the behavior of "\\" is presently restricted to
appearing at the end of the line in a paragraph? Does anyone need it to
be exported literally when it appears elsewhere?
Best,
Richard
next prev parent reply other threads:[~2014-09-27 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFyQvY2PtupGAuDX_UDMHiJgSvTUYYGKeVqfvCzZFAU9m-KJ7g@mail.gmail.com>
2014-09-26 15:52 ` Fwd: Enforcing newlines in plain text export Richard Lawrence
2014-09-26 16:04 ` Kaushal
2014-09-26 16:14 ` Kaushal
2014-09-27 0:46 ` Richard Lawrence
2014-09-27 3:59 ` Kaushal
2014-09-27 15:59 ` Richard Lawrence [this message]
2014-09-27 21:17 ` Nicolas Goaziou
2014-09-27 21:37 ` Kaushal
2014-09-28 1:30 ` Alexis
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=87iok99hqq.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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).