unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: James Thomas <jimjoe@gmx.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: buffer list sequence
Date: Fri, 10 Nov 2023 16:17:53 -0700	[thread overview]
Message-ID: <CAJcAo8tOzekGEmr+yrwH3Cqo5mpLVJeTn2FRH69t0=BRmJ2jCQ@mail.gmail.com> (raw)
In-Reply-To: <87sf5d20li.fsf@gmx.net>

thanks.

do you maen visit all other windows?  or bury them?  ugh.

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.

On 11/10/23, James Thomas <jimjoe@gmx.net> wrote:
> Samuel Wales wrote:
>
>> when i do delete-other-windows, soimetims i wasnt to go to the bufeer
>> iwhose window i  just deelted .  but i dont knoww hwat it is.
>
> If it's the last buffer you were in before switching to the current one,
> it'll be next in the list.
>
>> i'[d like for it to be in the buffer list right next tot the current
>> buffer so i can just do prev or next buffer.
>
> The previous buffer will be last one you buried.
>
>> sometimes it is not there.  there is fancy burying or special cases of
>> *buffer* and maybe more things like that [certainly also with "
>> buffer"].
>
> You'll probably have to customize/advice `delete-other-windows' to do
> one of the above, if you want it consistently.
>
> --
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



  reply	other threads:[~2023-11-10 23:17 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 [this message]
2023-11-12  9:07     ` James Thomas

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='CAJcAo8tOzekGEmr+yrwH3Cqo5mpLVJeTn2FRH69t0=BRmJ2jCQ@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jimjoe@gmx.net \
    /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).