From: James Thomas <jimjoe@gmx.net>
To: Samuel Wales <samologist@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: buffer list sequence
Date: Sun, 12 Nov 2023 14:37:43 +0530 [thread overview]
Message-ID: <87zfzjibkw.fsf@gmx.net> (raw)
In-Reply-To: <CAJcAo8tOzekGEmr+yrwH3Cqo5mpLVJeTn2FRH69t0=BRmJ2jCQ@mail.gmail.com> (Samuel Wales's message of "Fri, 10 Nov 2023 16:17:53 -0700")
Samuel Wales wrote:
> apropos of nothing, in old code [i am less capable of coding now]
> sometimes i do (switch-to-buffer (current-buffer)) which sometimes
> fixes buffer liust problems. i do not know why as it looks like it
> should be a no-op but i ahve no idea.
One reason I can think of for that is if a `switch-to-buffer' somewhere
used the NORECORD option. Your code would undo that.
You should also read (info "(elisp) Buffer List")
--
prev parent reply other threads:[~2023-11-12 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 3:30 buffer list sequence Samuel Wales
2023-11-10 13:34 ` James Thomas
2023-11-10 23:17 ` Samuel Wales
2023-11-12 9:07 ` James Thomas [this message]
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=87zfzjibkw.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=help-gnu-emacs@gnu.org \
--cc=samologist@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.
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).