From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Enforcing newlines in plain text export Date: Sat, 27 Sep 2014 08:59:41 -0700 Message-ID: <87iok99hqq.fsf@berkeley.edu> References: <87r3yybcqs.fsf@berkeley.edu> <87ppehao11.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]:60791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XXuQu-00045h-TI for emacs-orgmode@gnu.org; Sat, 27 Sep 2014 12:01:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XXuQn-0006DI-Cp for emacs-orgmode@gnu.org; Sat, 27 Sep 2014 12:01:16 -0400 Received: from plane.gmane.org ([80.91.229.3]:47566) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XXuQn-0006C1-5g for emacs-orgmode@gnu.org; Sat, 27 Sep 2014 12:01:09 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XXuQh-0007F7-2b for emacs-orgmode@gnu.org; Sat, 27 Sep 2014 18:01:03 +0200 Received: from c-67-169-117-151.hsd1.ca.comcast.net ([67.169.117.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 27 Sep 2014 18:01:03 +0200 Received: from richard.lawrence by c-67-169-117-151.hsd1.ca.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 27 Sep 2014 18:01:03 +0200 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: emacs-orgmode@gnu.org Cc: Kaushal Hi Kaushal, Kaushal 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