emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-fill-paragraph seems broken
Date: Fri, 27 Apr 2012 19:21:20 +0200	[thread overview]
Message-ID: <87sjfpw0of.fsf@gnu.org> (raw)
In-Reply-To: <719.1335546013@alphaville> (Nick Dokos's message of "Fri, 27 Apr 2012 13:00:13 -0400")

[-- Attachment #1: Type: text/plain, Size: 506 bytes --]

Hi Nick,

Nick Dokos <nicholas.dokos@hp.com> writes:

> Running M-q in a draft message with orgstruct++-mode enabled gives me
> the appended backtrace.
>
> The problem seems to have been introduced by commit 84a358e3.  Git blame
> fingers the following two as the most recent commits that affected
> org-fill-paragraph:
>
> 187f77a2 2012-04-04
> 84a358e3 2012-04-26
>
> With the first one in force, I don't get the problem; with
> the second, I do.

Can you try this patch against sendmail.el and report?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sendmail.el.patch --]
[-- Type: text/x-patch, Size: 415 bytes --]

=== modified file 'lisp/mail/sendmail.el'
--- lisp/mail/sendmail.el	2012-04-27 03:10:38 +0000
+++ lisp/mail/sendmail.el	2012-04-27 17:18:43 +0000
@@ -803,7 +803,7 @@
 	      t)))
     (do-auto-fill)))
 
-(defun mail-mode-fill-paragraph (arg)
+(defun mail-mode-fill-paragraph (&optional arg)
   ;; Do something special only if within the headers.
   (if (< (point) (mail-header-end))
       (let (beg end fieldname)

[-- Attachment #3: Type: text/plain, Size: 14 bytes --]


-- 
 Bastien

  reply	other threads:[~2012-04-27 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 17:00 [BUG] org-fill-paragraph seems broken Nick Dokos
2012-04-27 17:21 ` Bastien [this message]
2012-04-27 17:54   ` Nick Dokos
2012-04-27 21:09     ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjfpw0of.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).