From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wes Hardaker Subject: Re: Orgmode[PATCH 4/4] Add handling of blockquote and output formats that must be flowed. Date: Thu, 29 Apr 2010 06:54:13 -0700 Message-ID: References: <1272490799-22448-1-git-send-email-rpgoldman@sift.info> <1272490799-22448-2-git-send-email-rpgoldman@sift.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O7UC7-0006a8-7Q for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 09:54:23 -0400 Received: from [140.186.70.92] (port=45504 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O7UC3-0006ZP-0e for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 09:54:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O7UC1-0004JL-1k for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 09:54:18 -0400 Received: from mail.hardakers.net ([168.150.236.43]:39385) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O7UC0-0004Iq-Rk for emacs-orgmode@gnu.org; Thu, 29 Apr 2010 09:54:17 -0400 In-Reply-To: <1272490799-22448-2-git-send-email-rpgoldman@sift.info> (Robert P. Goldman's message of "Wed, 28 Apr 2010 16:39:59 -0500") 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: "Robert P. Goldman" Cc: "Robert P. Goldman" , dominik@uva.nl, emacs-orgmode@gnu.org >>>>> On Wed, 28 Apr 2010 16:39:59 -0500, "Robert P. Goldman" said: RPG> Added a handler for blockquotes. That looks great. Thanks! RPG> Also added :body-newline-paragraph to the org-set-generic-type. I'm fine with that too, but in the end couldn't you just put a "\n" in the format strings? I thought about what to do about newlines when I wrote the code base and in the end I decided that with the existing methods you could always add "\n"s everywhere you needed them which provided the maximum flexibility. The downside is that reading "\n"s everywhere isn't exactly pretty on the specification side :-/ (Carsten, go ahead and apply it on your end) -- Wes Hardaker My Pictures: http://capturedonearth.com/ My Thoughts: http://pontifications.hardakers.net/