From: Eli Zaretskii <eliz@gnu.org>
To: rswgnu@gmail.com
Cc: 48294@debbugs.gnu.org
Subject: bug#48294: Use 'with-current-buffer' byte-compiler warning seems wrong
Date: Sun, 09 May 2021 19:11:13 +0300 [thread overview]
Message-ID: <83zgx37uqm.fsf@gnu.org> (raw)
In-Reply-To: <CA+OMD9h2nUocnLksc7zMnVjY_itGM9xOaz3RL5adUvnPca21dw@mail.gmail.com> (message from Robert Weiner on Sun, 9 May 2021 11:57:25 -0400)
> From: Robert Weiner <rsw@gnu.org>
> Date: Sun, 9 May 2021 11:57:25 -0400
> Cc: 48294@debbugs.gnu.org
>
> Thanks for the feedback. Everything you wrote is very clear. The issue, however, is that I want to save
> point in the current buffer prior to switching context to the 'with-current-buffer' buffer, just as my
> (save-excursion (set-buffer ...)) code does. If I move the save-excursion into the with-current-buffer body,
> then it applies to the new buffer not the original one and if in that same body we change buffers again to the
> original and move point, then that movement will stay in place. So the question is, what is the appropriate
> code that the byte-compiler will accept when you want to save your original place before switching buffers.
I don't understand: with-current-buffer doesn't change point of the
original buffer, so why do you need to save it?
next prev parent reply other threads:[~2021-05-09 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 20:14 bug#48294: Use 'with-current-buffer' byte-compiler warning seems wrong Robert Weiner
2021-05-09 8:05 ` Eli Zaretskii
2021-05-09 15:57 ` Robert Weiner
2021-05-09 16:11 ` Eli Zaretskii [this message]
2021-05-09 18:09 ` Robert Weiner
2021-05-09 18:24 ` 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=83zgx37uqm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48294@debbugs.gnu.org \
--cc=rswgnu@gmail.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.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).