From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: what happened to the #+OPTIONS: \n:t ? Date: Tue, 5 Apr 2011 10:26:26 +0200 Message-ID: <56FEE231-C326-4F51-BCD0-27889810DC17@gmail.com> References: <4D99D8E1.4060406@gmail.com> <09466A6F-B1BD-4197-AAC7-8A9B360E8D9D@gmail.com> <4D9ACFB1.70105@gmail.com> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=49378 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q71ap-0006eJ-R5 for emacs-orgmode@gnu.org; Tue, 05 Apr 2011 04:26:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q71ao-0005Ey-G3 for emacs-orgmode@gnu.org; Tue, 05 Apr 2011 04:26:31 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:49978) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q71ao-0005Eo-93 for emacs-orgmode@gnu.org; Tue, 05 Apr 2011 04:26:30 -0400 Received: by eyd9 with SMTP id 9so38942eyd.0 for ; Tue, 05 Apr 2011 01:26:29 -0700 (PDT) In-Reply-To: <4D9ACFB1.70105@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: katepano Cc: emacs-orgmode@gnu.org On Apr 5, 2011, at 10:15 AM, katepano wrote: > Dear Dominik. > I see your point and it is accepted, of course. I admit, I should = write my email more clearly. Anyway, thanks for your time. >=20 > On the other hand I really would like to see #+OPTIONS: \n:t working, = if this possible and do not cause much frustration. If you read the threads I have linked to you will see that this is not at all simple. An option like this would always be a dirty hack that forces a backend into a state it was not made for. Using special markup and environments for code, poems, you name it, on the other hand, is perfectly fine. - Carsten >=20 > thanks anyway >=20 > Katepano >=20 > On 04/05/2011 11:04 AM, Carsten Dominik wrote: >> Dear katepano, >>=20 >> as you can see, it has taken 11 emails on a high volume email list >> to get the answer to your simple question. More than 1100 people = have >> subscribed to this mailing list, an unknown number of people >> read it on aggregators like gmane. That is a lot of time and energy >> spent unnecessarily. >>=20 >> Please take more care when formulating a question to the list >> and try to give all necessary information from the start. >> Here is an example on how you *could* have formulated your >> initial mail: >>=20 >>=20 >>=20 >> ---------------------------------------------------------------- >>=20 >> Dear Org- mode people, >>=20 >> I am trying to write a poem in Orgmode, but when I am exporting >> the poem to LaTeX or HTML, all the line breaks are lost! I would = like >> to export the poem with the line break preserved. >>=20 >> I have studied the manual and have found that >>=20 >> #+OPTIONS: \n:t >>=20 >> might be a way to achieve what I want. But the feature is marked as >> DOES NOT WORK in the manual. Does anyone know why this is the case? >> I have also search for "preserve breaks" in the mailing list archive: >>=20 >> = http://search.gmane.org/?query=3Dpreserve+breaks&author=3D&group=3Dgmane.e= macs.orgmode&sort=3Drelevance&DEFAULTOP=3Dand&xP=3Dorg%09mode >>=20 >> and found a number of threads which match this query, but the results >> have been confusing to me. So I am wondering if someone here could >> enlighten me what the best way is to achieve my goal. >>=20 >> Here is an example Org-file: >>=20 >> #+STARTUP: showall >> #+TITLE: 5-006 =CE=A4=CF=83=CE=B9=CE=B3=CE=AC=CF=81=CE=BF = =CE=B1=CF=84=CE=AD=CE=BB=CE=B5=CE=B9=CF=89=CF=84=CE=BF >> #+OPTIONS: H:3 num:nil toc:nil \n:t >>=20 >> *=CE=A3=CF=85=CE=BD=CE=B8=CE=AD=CF=84=CE=B7=CF=82:* =CE=A3=CF=89=CE=BA=CF= =81=CE=AC=CF=84=CE=B7=CF=82 =CE=9C=CE=AC=CE=BB=CE=B1=CE=BC=CE=B1=CF=82 >> *=CE=A3=CF=84=CE=B9=CF=87=CE=BF=CF=85=CF=81=CE=B3=CF=8C=CF=82:* = =CE=93=CE=B9=CF=8E=CF=81=CE=B3=CE=BF=CF=82 =CE=91=CE=B8=CE=B1=CE=BD=CE=B1=CF= =83=CF=8C=CF=80=CE=BF=CF=85=CE=BB=CE=BF=CF=82 >> *=CE=88=CF=84=CE=BF=CF=82:* 1993 >>=20 >> #+BEGIN_QUOTE >> =CE=98=CE=B1 =CF=80=CE=B5=CF=81=CF=80=CE=B1=CF=84=CE=AE=CF=83=CF=89 = =CE=BC=CE=BF=CE=BD=CE=B1=CF=87=CF=8C=CF=82 =CE=BA=CE=B9 =CE=B1=CF=85=CF=84= =CF=8C =CF=84=CE=BF =CE=B2=CF=81=CE=AC=CE=B4=CF=85 >> =CE=BC=CE=AE=CF=80=CF=89=CF=82 =CE=BA=CE=B1=CE=B9 =CE=B2=CF=81=CF=89 = =CF=84=CE=B7=CF=82 =CE=BB=CE=B7=CF=83=CE=BC=CE=BF=CE=BD=CE=B9=CE=AC=CF=82 = =CF=83=CE=BF=CF=85 =CF=84=CE=BF =CE=BD=CE=B5=CF=81=CF=8C >> =CE=BA=CE=B1=CE=B9 =CF=83=CE=B5 =CF=85=CF=80=CF=8C=CE=B3=CE=B5=CE=B9=CE= =B1 =CF=83=CE=BA=CE=BF=CF=84=CE=B5=CE=B9=CE=BD=CE=AC =CE=B8=CE=B1 =CE=B2=CF= =81=CF=89 =CF=83=CE=B7=CE=BC=CE=AC=CE=B4=CE=B9 >> =CE=BC' =CE=AD=CE=BD=CE=B1 =CF=80=CE=BF=CF=84=CE=AE=CF=81=CE=B9 =CF=89=CF= =82 =CF=84=CE=B7=CF=82 =CE=B1=CF=85=CE=B3=CE=AE=CF=82 =CF=84=CE=BF=CE=BD = =CF=80=CE=B1=CE=BD=CE=B9=CE=BA=CF=8C >> #+END_QUOTE >> = --------------------------------------------------------------------------= -------------- >>=20 >> I guess you would have gotten the right reply immediately. >>=20 >>=20 >> On Apr 4, 2011, at 4:42 PM, katepano wrote: >>=20 >>> what happen to the #+OPTIONS: \n:t ? we need it back please!!! why = it does not work???? >>>=20 >>> By the way nobody responded to my message!!! >>>=20 >>> http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40104.html >>> why? is it a stupid question or it can't be implemented? >>=20 >> That was actually a much better message, and, as Bastien indicates, >> there is no simple answer/solution at this time. >>=20 >> Regards >>=20 >> - Carsten >>=20 >>=20 >>> Regards >>>=20 >>> katepano >>>=20 >> - Carsten >>=20 >>=20 >>=20 >>=20 - Carsten