GNU bug report logs - #21505
24.4; Buffer order

Previous Next

Package: emacs;

Reported by: hoppe <travis.hoppe <at> gmail.com>

Date: Thu, 17 Sep 2015 04:57:04 UTC

Severity: wishlist

Tags: confirmed, moreinfo

Found in version 24.4

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 21505 <at> debbugs.gnu.org (full text, mbox):

From: hoppe <travis.hoppe <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 21505 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>,
 tsdh <at> gnu.org
Subject: Re: bug#21505: 24.4; Buffer order
Date: Thu, 17 Sep 2015 11:23:58 -0400
[Message part 1 (text/plain, inline)]
No, and this is why it's a little weird. On my computer when I create the
files a,b,c and run

> emacs a b c

the prompt of C-x b gives:

c
b
a
*scratch*
*Messages*

with file c opened first. BUT, the order of NextBuffer goes
[c->b->*Messages*->*scratch->a]

On Thu, Sep 17, 2015 at 11:19 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: hoppe <travis.hoppe <at> gmail.com>
> > Date: Thu, 17 Sep 2015 10:59:41 -0400
> > Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, tsdh <at> gnu.org,
> 21505 <at> debbugs.gnu.org
> >
> > In response to the first question, I'd like this to be the "easy"
> request, that
> > this behavior is only for when emacs opens and not continuously during
> the
> > session. I agree, it does not need to be maintained during the session.
> >
> > Re: Tassilo Horn: I purposely showed my example with a wildcard since
> emacs
> > could be given any expansion from the shell. To me it, and for my usual
> use
> > case, it doesn't matter. I have a bunch of files I'd like to edit and I
> often
> > miss those that are past the messages and scratch buffer. Opening the
> files in
> > the order given from the command line seems very natural to me.
> >
> > So to be clear, given the command run on the shell:
> >
> > > emacs a c b
> >
> > The buffer order should be [a,c,b,*messages*,*scratch*]. Currently the
> default
> > behavior looks something like [b,c,*messages*,*scratch*, a].
>
> So it's just an issue with the order in which buffers are presented in
> the prompt of "C-x b"?
>
[Message part 2 (text/html, inline)]

This bug report was last modified 3 years and 91 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.