From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Hackney Subject: Regression in `fill-paragraph' behavior Date: Tue, 12 Mar 2013 21:10:06 -0400 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40981) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFaDA-0000yI-GG for emacs-orgmode@gnu.org; Tue, 12 Mar 2013 21:10:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UFaD6-0001pU-FV for emacs-orgmode@gnu.org; Tue, 12 Mar 2013 21:10:32 -0400 Received: from mail-ia0-x22f.google.com ([2607:f8b0:4001:c02::22f]:34018) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFaD6-0001pO-7K for emacs-orgmode@gnu.org; Tue, 12 Mar 2013 21:10:28 -0400 Received: by mail-ia0-f175.google.com with SMTP id o25so390374iad.34 for ; Tue, 12 Mar 2013 18:10:27 -0700 (PDT) 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 A while ago, I reported a bug in `fill-paragraph' when in org-mode which caused filling to behave incorrectly in the presence of leading characters. This comes up when filling paragraphs of email replies, such as #+BEGIN_EXAMPLE > Here is some text > to be filled to a single line #+END_EXAMPLE In the version of org-mode which comes with Emacs 24.3, running `fill-paragraph' on this yields #+BEGIN_EXAMPLE > Here is some text > to be filled to a single line #+END_EXAMPLE Whereas filling the same text in `text-mode' results in #+BEGIN_EXAMPLE > Here is some text to be filled to a single line #+END_EXAMPLE Notice the lack of the > symbol in the `text-mode' fill. Steps to reproduce: 1. Install Emacs 24.3 2. Launch with "emacs -Q" 3. Create a buffer in `org-mode' 4. Type/yank in the example text from above 5. Press M-q for `fill-paragraph' I probably should have checked this before the release of 24.3. -- Daniel Hackney