From: David Kastrup <David.Kastrup@t-online.de>
Subject: Re: save-excursion doesn't always work
Date: 16 Dec 2002 18:43:26 +0100 [thread overview]
Message-ID: <x5isxt3lmp.fsf@lola.goethe.zz> (raw)
In-Reply-To: 5lu1hdew66.fsf@rum.cs.yale.edu
"Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:
> >> It might do a few things slightly differently, but it will modify the
> >> buffer anyway, even if the end result is exactly the same as the
> >> starting point (e.g. it will first turn all \n into spaces and then
> >> turn them back into \n).
> > We are not talking about modification of the buffer, but about marks
> > being moved around in seemingly random manner.
>
> Unless they're explicitly moved, marks only move in response to
> buffer modifications.
Yes. But if you do modifications that end up doing nothing, the
marks may move or not. The former is more of a nuisance than the
latter.
> Maybe the default filling function works better than AUCTeX in this
> regard (I don't know) but even if it does, it doesn't work 100% as
> the user wants it to.
Come off it. Nobody uses M-q as a substitute for forward-paragraph on
filled text. It is a text-changing command. I don't think people
will complain much if it changes text. They will complain if regions
and marks end up on the wrong side of (maybe adjusted) white space,
though. _Regardless_ of whether there were indeed formatting changes
or not.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2002-12-16 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 5:38 save-excursion doesn't always work Ittay Freiman
2002-12-15 10:37 ` David Kastrup
2002-12-16 16:02 ` Stefan Monnier <foo@acm.com>
2002-12-16 16:21 ` David Kastrup
2002-12-16 17:00 ` Stefan Monnier <foo@acm.com>
2002-12-16 17:43 ` David Kastrup [this message]
2002-12-16 18:28 ` Stefan Monnier <foo@acm.com>
2002-12-16 18:46 ` David Kastrup
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5isxt3lmp.fsf@lola.goethe.zz \
--to=david.kastrup@t-online.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.