From: Bernt Hansen <bernt@norang.ca>
To: katepano <katepano@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: what happened to the #+OPTIONS: \n:t ?
Date: Mon, 04 Apr 2011 14:02:41 -0400 [thread overview]
Message-ID: <87wrj9nbcu.fsf@norang.ca> (raw)
In-Reply-To: <874o6doqn3.fsf@norang.ca> (Bernt Hansen's message of "Mon, 04 Apr 2011 13:47:12 -0400")
Bernt Hansen <bernt@norang.ca> writes:
> katepano <katepano@gmail.com> writes:
>
>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why it
>> does not work????
>
> Something happened to it? This feature was not removed intentionally.
Actually I stand corrected. Carsten added the "DOES NOT WORK" text to
the info manual for this feature.
-\n: @r{turn on/off line-break-preservation}
+\n: @r{turn on/off line-break-preservation (DOES NOT WORK)}
so it seems this functionality has been orphaned (over a year ago)
--8<---------------cut here---------------start------------->8---
commit 0776eab890a7352144dd6c56523dbf3ab3f1b71d
Author: Carsten Dominik <carsten.dominik@gmail.com>
Date: Wed Dec 9 22:27:38 2009 +0100
Preserving line breaks for export no longer works
ASCII export always preserves them - no other export format does.
--8<---------------cut here---------------end--------------->8---
Regards,
Bernt
next prev parent reply other threads:[~2011-04-04 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 14:42 what happened to the #+OPTIONS: \n:t ? katepano
2011-04-04 17:44 ` Nick Dokos
2011-04-05 7:07 ` katepano
2011-04-05 7:18 ` Jambunathan K
2011-04-05 7:31 ` katepano
2011-04-05 7:52 ` Christian Moe
2011-04-05 7:56 ` katepano
2011-04-05 8:09 ` Carsten Dominik
2011-04-04 17:47 ` Bernt Hansen
2011-04-04 17:57 ` Nick Dokos
2011-04-04 18:44 ` Carsten Dominik
2011-04-04 18:02 ` Bernt Hansen [this message]
2011-04-04 23:28 ` Bastien
2011-04-05 8:04 ` Carsten Dominik
2011-04-05 8:15 ` katepano
2011-04-05 8:26 ` Carsten Dominik
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=87wrj9nbcu.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=katepano@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).