From: "Stefan Monnier" <monnier@IRO.UMontreal.CA>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: [herring@lanl.gov: LaTeX paragraphs]
Date: 17 Sep 2003 09:49:46 -0400 [thread overview]
Message-ID: <jwvk787wmmd.fsf@vor.iro.umontreal.ca> (raw)
In-Reply-To: <E19zYSO-0005LI-AR@fencepost.gnu.org>
> [I sent this message a month ago but did not get a response.]
> Can you please look at this, and ack?
This bug has existed for ever (virtually) and is due to the fact
that the filling code still doesn't understand comments well enough.
We can trivially fix his problem by removing the %-lines from
the paragraph-separators, but then other problems start showing up.
Stefan
> From: Davis Herring <herring@lanl.gov>
> Subject: LaTeX paragraphs
> To: bug-gnu-emacs@gnu.org
> Date: Fri, 15 Aug 2003 11:27:44 -0600 (MDT)
> For GNU Emacs 21.2.1 (powerpc-apple-darwin, X toolkit) of 2003-06-06:
> The regexps used by LaTeX mode for `paragraph-start' and
> `paragraph-separate' seem a bit too general: namely, using
> `forward-paragraph' and then `backward-paragraph' on
> a
> %b
> c
> with point on "b"'s line puts point after c and then just before c (this
> is because, if I read the regexps correctly, the %comment is considered a
> paragraph separator and thus skippable). Similarly back then forth moves
> across a both times. This means, most notably, that `fill-paragraph'
> won't work on comments. Moreover, `fill-region' on a comment doesn't seem
> to deduce the comment's fill-prefix properly -- not sure why on that,
> though.
> Thanks in advance,
> Davis Herring
> - --
> This product is sold by volume, not by mass. If it seems too dense or too
> sparse, it means mass-energy conversion has occurred during shipping.
> _______________________________________________
> Bug-gnu-emacs mailing list
> Bug-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs
> ----------
parent reply other threads:[~2003-09-17 13:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E19zYSO-0005LI-AR@fencepost.gnu.org>]
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=jwvk787wmmd.fsf@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=bug-gnu-emacs@gnu.org \
/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).