From: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Multiple bugs in lisp-mode M-q on paragraphs within #|..|# comments
Date: Sun, 25 Mar 2007 10:13:16 -0400 [thread overview]
Message-ID: <17926.33660.189148.964115@rgrjr.dyndns.org> (raw)
In-Reply-To: <46064C69.1010807@gmx.at>
From: martin rudalics <rudalics@gmx.at>
Date: Sun, 25 Mar 2007 12:18:17 +0200
. . .
> It might be better to recognize Lisp "#|...|#" comments explicitly at
> a point where we know we're dealing with Lisp. The attached patch is a
> total hack, but it seems to relieve the symptoms of the first three bugs
> (and changes that of the fourth). This style of comment can be nested,
> so the hack will get confused if still inside a comment but after an
> inner comment. The changed symptoms of the fourth bug suggest that the
> bounds passed to the fill-region-as-paragraph call are wrong. But I'll
> bet someone else can do better.
I'm afraid this problem is not restricted to the Lisp case . . .
Anyway please try the attached patch. I'm confident Stefan will find
a better solution soon.
It corrects all four syndromes for me; thanks. (In my ignorance, I had
tried rebinding comment-end, but around a fill-comment-paragraph call,
which did nothing.)
-- Bob
next prev parent reply other threads:[~2007-03-25 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 19:32 Multiple bugs in lisp-mode M-q on paragraphs within #|..|# comments Bob Rogers
2007-03-24 19:40 ` Bob Rogers
2007-03-24 19:51 ` Lennart Borgman (gmail)
2007-03-24 20:04 ` Chong Yidong
2007-03-24 20:59 ` Bob Rogers
2007-03-24 22:07 ` martin rudalics
2007-03-25 0:23 ` Bob Rogers
2007-03-25 10:18 ` martin rudalics
2007-03-25 14:13 ` Bob Rogers [this message]
2007-03-25 19:53 ` Stefan Monnier
2007-03-25 23:05 ` Bob Rogers
2007-03-28 2:57 ` Stefan Monnier
2007-03-31 0:42 ` Bob Rogers
2007-03-31 20:30 ` Stefan Monnier
2007-04-01 22:45 ` Bob Rogers
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17926.33660.189148.964115@rgrjr.dyndns.org \
--to=rogers-emacs@rgrjr.dyndns.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.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).