From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Enforcing newlines in plain text export Date: Fri, 26 Sep 2014 17:46:18 -0700 Message-ID: <87ppehao11.fsf@berkeley.edu> References: <87r3yybcqs.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57630) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XXgAp-0002ZQ-2v for emacs-orgmode@gnu.org; Fri, 26 Sep 2014 20:47:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XXgAh-00005K-JO for emacs-orgmode@gnu.org; Fri, 26 Sep 2014 20:47:43 -0400 Received: from mail-pa0-f41.google.com ([209.85.220.41]:48563) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XXgAh-00004y-De for emacs-orgmode@gnu.org; Fri, 26 Sep 2014 20:47:35 -0400 Received: by mail-pa0-f41.google.com with SMTP id fa1so5810033pad.0 for ; Fri, 26 Sep 2014 17:47:29 -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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Kaushal Cc: emacs-orgmode@gnu.org Kaushal writes: > Interesting thing is that `\\` work fine at the end of the lines. Yes, this is the behavior documented in the manual. > I need to force line breaks in cases like these > > ----- > For example, to execute the =example_1= test and run in the {{{NEWLINE}}} > > =/some/long/path/that/wouldn't/fit/along/with/the/above/line/in/the/same/line= > directory, > do the following.. > ----- > > In the above example, org-export will not wrap the text between the > verbatim formatting characters "=". > To ensure that the exported formats (html/pdf/ascii) look clean, I have to > force a newline character just before that long string. > > Now using "\\" here instead of {{{NEWLINE}}} works but then I have to > ensure that I place the "\\" character at the very end. If they are placed > mid-line then they will be interpreted as newline by latex but simply "\\" > character by html exporter. As you say, "\\" at the end of the line works fine in this case. So it seems you do not have a need for another solution. > For consistency, the {{{NEWLINE}}} approach looks better; hoping that > org-mode will support a special newline character for ascii exports at some > time: > > ----- > #+MACRO: NEWLINE @@latex:\\@@ @@html:
@@ @@ascii:NEWLINE_CHARACTERS_ > FOR_ASCII_EXPORT@@ > ----- This would really not be a great solution, and I don't think you should expect Org mode to support it. If you really need something like this, you could write an export filter for yourself (e.g., one that replaces the string "ASCII_NEWLINE_CHARACTER" with "\n" in the exported buffer). See the "Advanced configuration" section of the Exporting chapter in the manual. A better and more general solution, I think, would be to allow "\\" to be used in other contexts, such as in headlines, title/author/date declarations, etc. But that is a change to the currently documented syntax, and it is probably a fair amount of work to implement, so it probably isn't going to happen unless a variety of users really need it and the maintainers think it would be an improvement to Org. Best, Richard