From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21505@debbugs.gnu.org, travis.hoppe@gmail.com
Subject: bug#21505: 24.4; Buffer order
Date: Thu, 17 Sep 2015 09:53:01 +0200 [thread overview]
Message-ID: <87zj0lo52a.fsf@gnu.org> (raw)
In-Reply-To: <83y4g55yat.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Sep 2015 09:56:26 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Tassilo Horn <tsdh@gnu.org>
>> Cc: hoppe <travis.hoppe@gmail.com>, 21505@debbugs.gnu.org
>> Date: Thu, 17 Sep 2015 08:49:51 +0200
>>
>> And to me, the order a, b, c seems to be the only right one.
>
> You do realize that the command line said just "*", and the order of
> the files Emacs saw was determined by the expansion of that wildcard
> by the shell, yes?
Yes, I've seen that and I assumed that the usual shell expansion is
alphabetical.
> Or are you saying that the order of the buffers should always be
> alphabetical?
No, it should always be as given to emacs/emacsclient, i.e., when I
invoke
$ emacsclient x a b
I want to have the buffer x selected and using `next-buffer' I'd switch
to a and then b, and then to the other buffers which have existed
before. Right now, x will be selected, but a and b are far away.
Bye,
Tassilo
next prev parent reply other threads:[~2015-09-17 7:53 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 [this message]
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
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
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=87zj0lo52a.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=21505@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=travis.hoppe@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).