From mboxrd@z Thu Jan 1 00:00:00 1970 From: GRAWeeLD Subject: Re: Specifying document-specific settings: line breaks and unusual spacing Date: Wed, 26 Apr 2017 14:33:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113eca761adb8e054e12ba19 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34595) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d3O0p-00078C-Rl for emacs-orgmode@gnu.org; Wed, 26 Apr 2017 10:33:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d3O0l-0005BD-L0 for emacs-orgmode@gnu.org; Wed, 26 Apr 2017 10:33:47 -0400 Received: from mail-io0-x235.google.com ([2607:f8b0:4001:c06::235]:36111) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d3O0l-0005Au-Dh for emacs-orgmode@gnu.org; Wed, 26 Apr 2017 10:33:43 -0400 Received: by mail-io0-x235.google.com with SMTP id p80so3808930iop.3 for ; Wed, 26 Apr 2017 07:33:43 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org --001a113eca761adb8e054e12ba19 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable AsciiDoc also used the [literal] style for inordinately formatted blocks of text. Maybe something like #+UNFORMATTED_TEXT could be an OrgMode property which handles this. Or maybe OrgMOde already has something to handle free-floating text and I just missed it? On Tue, Apr 25, 2017 at 7:13 PM, GRAWeeLD wrote: > I tried something like this: > > #+FREE_FLOW > U n res train ed text > #+FREE_FLOW > > and while this did admittedly came somewhat closer to what I desire by ex= porting the escaped characters and new lines as being a little smaller than= those which were typed normally. This, however, still wasn't a full free t= ext formatting. > > > On Tue, Apr 25, 2017 at 6:18 PM, GRAWeeLD wrote: > >> Hello Org-Mode community, >> >> I am rather new to Org-mode itself and have still a lot to read about in >> the official manual, but I cannot seem to find a method for specifying >> document specific behaviour in Org-Mode. >> >> For example, if I want all line breaks to be exported exactly with the >> same indentation as I have for them in my specific document, there seems= to >> be no way to do this. >> >> Sure, I can use \\ to create a new line break, and that works great, but >> if I indent my text differently, >> >> for >> example >> like >> >> >> a straircase >> >> this indentation will not be preserved as such upon PDF export. >> >> Now, I found that AsciiDoc solved this somewhat by allowing the user to >> insert >> >> [/hardbreaks] >> >> format your text o d d l y >> >> >> [hardbreaks/] >> >> at the beginning of a particular section within a document, and if this = is inserted, then everything would be rendered as it is seen on screen upon= export as well. >> >> Granted, I am not suggesting that this preservation should be Org-Mode's= default behaviour, not at all. I want only certain portions of my book to = be formatted in this odd way, the rest should be perfectly precisely aligne= d, as is the case at this very time. >> >> >> Thank you for your time and considerations towards this proposal. >> >> > --001a113eca761adb8e054e12ba19 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
AsciiDoc also used the=C2=A0[literal] style for inordi= nately formatted blocks of text. Maybe something like #+UNFORMATTED_TEXT co= uld be an OrgMode property which handles this. Or maybe OrgMOde already has= something to handle free-floating text and I just missed it?=

On Tue, Apr 25, 2017 at 7:13 PM, GRAWeeLD= <graweeld@gmail.com> wrote:
I tried something like this:

#+FREE_FLOW
U n res train                      ed text
#+FREE_FLOW
and while this did admittedly came some=
what closer to what I desire by exporting the escaped characters and new li=
nes as being a little smaller than those which were typed normally. This, h=
owever, still wasn't a full free text formatting.

On Tue, Apr 25, 2017 at 6:18 PM, GRAWeeLD <graweeld@g= mail.com> wrote:
Hello Org-Mode community,

I am rather new to Or= g-mode itself and have still a lot to read about in the official manual, bu= t I cannot seem to find a method for specifying document specific behaviour= in Org-Mode.

For example, if I want all line brea= ks to be exported exactly with the same indentation as I have for them in m= y specific document, there seems to be no way to do this.

Sure, I can use \\ to create a new line break, and that works great= , but if I indent my text differently,=C2=A0

=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 for
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 example=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 like

=C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0a straircase

this i= ndentation will not be preserved as such upon PDF export.

Now, I found that AsciiDoc solved this somewhat by allowing the use= r to insert=C2=A0

=09 =09 =09 
[/hardbreaks]
=
                   format                       your   text o d d l y
= 

[hardbrea=
ks/]
at the beginning of a particular sect=
ion within a document, and if this is inserted, then everything would be re=
ndered as it is seen on screen upon export as well.
Granted, I am not suggesting that this preservation should be Org=
-Mode's default behaviour, not at all. I want only certain portions of =
my book to be formatted in this odd way, the rest should be perfectly preci=
sely aligned, as is the case at this very time.

Thank you for your time and con=
siderations towards this proposal.


--001a113eca761adb8e054e12ba19--