unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Xu Chunyang <mail@xuchunyang.me>, 30001@debbugs.gnu.org
Subject: bug#30001: 27.0.50; Outdated info on save-excursion in (info "(cl) Modify Macros")
Date: Sat, 06 Jan 2018 13:12:37 +0100	[thread overview]
Message-ID: <87r2r3rxsa.fsf@gmx.net> (raw)
In-Reply-To: <83efn39wuv.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Jan 2018 11:10:00 +0200")

On Sat, 06 Jan 2018 11:10:00 +0200 Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Xu Chunyang <mail@xuchunyang.me>
>> Date: Sat, 06 Jan 2018 13:29:57 +0800
>> 
>> 'C-h S cl-letf' or (info "(cl) Modify Macros") has the following:
>> 
>>   Note that `cl-letf' on `(point)' is not quite like a
>>   `save-excursion', as the latter effectively saves a marker which
>>   tracks insertions and deletions in the buffer.
>> 
>> but 'save-excursion' is no longer saving marker since Emacs 25.1
>> according to 'C-h f save-excursion'.
>
> save-excursion doesn't save the _mark_, but it still saves a _marker_
> that tracks point, as opposed to just the value of point at the moment
> of the call.

It looks like the doc string of save-excursion contains a few typos:

  Before Emacs 25.1, ‘save-excursion’ used to save the mark state.
  To save the marker state as well as the point and buffer, use
              ^^^^^^                  ^^^           ^^^^^^
  ‘save-mark-and-excursion’.

Shouldn't that be: "To save the mark state as well as point and the
buffer"?

Steve Berman





  reply	other threads:[~2018-01-06 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06  5:29 bug#30001: 27.0.50; Outdated info on save-excursion in (info "(cl) Modify Macros") Xu Chunyang
2018-01-06  9:10 ` Eli Zaretskii
2018-01-06 12:12   ` Stephen Berman [this message]
2018-01-06 15:15     ` Eli Zaretskii
     [not found]   ` <m2efn3xj73.fsf@xuchunyang.me>
2018-01-06 15:16     ` Eli Zaretskii

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=87r2r3rxsa.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=30001@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mail@xuchunyang.me \
    /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).