all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 25054@debbugs.gnu.org
Subject: bug#25054: 25.1; bury-buffer makes bad choice of next buffer
Date: Sat, 29 Jan 2022 17:35:03 +0100	[thread overview]
Message-ID: <87ee4q8pqg.fsf@gnus.org> (raw)
In-Reply-To: <5846CB28.7090104@gmx.at> (martin rudalics's message of "Tue, 06 Dec 2016 15:28:56 +0100")

martin rudalics <rudalics@gmx.at> writes:

>> Can you suggest a way?
>
> Yes.  We have two functions: ‘set-window-prev-buffers’ and
> ‘set-window-next-buffers’.  Whenever you bury a buffer and an option
> whose name you have to invent is non-nil, use these functions to remove
> the buried buffer from these lists.  Either for all windows or for the
> selected window only - depending on whether you want to reserve two or
> three values for the option.

Skimming this thread, it seems like Emacs is working as designed, and
has the required options to allow customising the actions according to
how the user wants them to work, so I'm closing this bug report.  (If I
misunderstood and there's something that should be fixed here, please
respond to the debbugs address and we'll reopen.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-01-29 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 18:51 bug#25054: 25.1; bury-buffer makes bad choice of next buffer Francesco Potortì
2016-11-28 19:14 ` martin rudalics
2016-11-28 20:32   ` Francesco Potortì
2016-11-29  8:09     ` martin rudalics
2016-11-29 20:44       ` Francesco Potortì
2016-11-30  7:53         ` martin rudalics
2016-12-06 11:48           ` Francesco Potortì
2016-12-06 14:28             ` martin rudalics
2022-01-29 16:35               ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ee4q8pqg.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=25054@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.