unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21505@debbugs.gnu.org, hoppe <travis.hoppe@gmail.com>
Subject: bug#21505: 24.4; Buffer order
Date: Thu, 17 Sep 2015 08:49:51 +0200	[thread overview]
Message-ID: <877fnppmk0.fsf@gnu.org> (raw)
In-Reply-To: <8337yd7hgn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 17 Sep 2015 08:17:12 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Let's say I have a Linux directory that looks like
>> 
>> -rw-r--r-- 1 hooked se 0 Sep 16 16:02 a
>> -rw-r--r-- 1 hooked se 0 Sep 16 16:02 b
>> -rw-r--r-- 1 hooked se 0 Sep 16 16:02 c
>> When I type emacs * it opens all three files but it puts me in the middle of
>> the buffer chain. For example when I run it, I start off at c and NextBuffer
>> takes me along the chain
>> 
>> c -> b -> *Messages* -> *scratch* -> a ->
>> This is really, really annoying. I'd like to open up emacs and have the order
>> be any of the permutations
>> 
>> c -> b -> a -> *Messages* -> *scratch* -> 
>> b -> a -> c -> *Messages* -> *scratch* -> 
>> a -> b -> c -> *Messages* -> *scratch* -> 
>> 
>> This behavior is the most natural one IMHO (user @Stefan
>> agrees). This is a feature request to make this the default behavior.
>
> Is the feature request to produce the above buffer order only once,
> upon entry to Emacs in this scenario, or is it more general,
> i.e. should hold at any arbitrary point in time during the Emacs
> session? [...]
>
> In any case, the latter possibility is much harder to accomplish; the
> former is relatively easy, but I question its usefulness, given that
> it's limited to the initial entry.

IMO it could and should apply also to emacsclient invocations.  And to
me, the order a, b, c seems to be the only right one.

Bye,
Tassilo





  reply	other threads:[~2015-09-17  6:49 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 [this message]
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
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=877fnppmk0.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).