From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: travis.hoppe@gmail.com, 21505@debbugs.gnu.org,
Tassilo Horn <tsdh@gnu.org>
Subject: bug#21505: 24.4; Buffer order
Date: Sun, 20 Feb 2022 13:57:03 +0100 [thread overview]
Message-ID: <87v8x9u25c.fsf@gnus.org> (raw)
In-Reply-To: <jwvbnd1w6tc.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Thu, 17 Sep 2015 08:50:33 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The precise behavior is a bit more complex since those commands, rather
> than just showing the first file may/will also show the buffer-list,
> but if exactly one of the files is shown it should be the first in the
> list and next-buffer should go in the order in which the file names
> were given (until reaching the end of this list at which point it'll
> hit things like *Messages* and friends and that's fine).
This behaviour is still present in Emacs 29.
But I'm wondering -- why is Emacs popping up a *Buffer List* window when
you ask it to open two files? I'd have thought the obvious thing to do
in this situation is to open as many windows as there are files (if
possible)? Or open a single window displaying the first file specified
(and then have the rest be in the next-buffer order you describe).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-20 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 2:57 bug#21505: 24.4; Buffer order hoppe
2015-09-17 5:17 ` Eli Zaretskii
2015-09-17 6:49 ` Tassilo Horn
2015-09-17 6:56 ` Eli Zaretskii
2015-09-17 7:53 ` Tassilo Horn
2015-09-17 12:50 ` Stefan Monnier
2015-09-17 14:55 ` Eli Zaretskii
2015-09-17 14:59 ` hoppe
2015-09-17 15:19 ` Eli Zaretskii
2015-09-17 15:23 ` hoppe
2015-09-17 15:44 ` Eli Zaretskii
2015-09-17 15:48 ` hoppe
2015-09-17 16:20 ` Eli Zaretskii
2022-02-20 12:57 ` Lars Ingebrigtsen [this message]
2022-02-20 13:20 ` Eli Zaretskii
2022-02-21 13:38 ` Lars Ingebrigtsen
2022-02-21 13:55 ` Eli Zaretskii
2022-02-21 14:43 ` Lars Ingebrigtsen
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=87v8x9u25c.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21505@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=travis.hoppe@gmail.com \
--cc=tsdh@gnu.org \
/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.