From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: hoppe Newsgroups: gmane.emacs.bugs Subject: bug#21505: 24.4; Buffer order Date: Thu, 17 Sep 2015 10:59:41 -0400 Message-ID: References: <8337yd7hgn.fsf@gnu.org> <877fnppmk0.fsf@gnu.org> <83y4g55yat.fsf@gnu.org> <87zj0lo52a.fsf@gnu.org> <83twqtqene.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7bd75cf8528a6b051ff2abc6 X-Trace: ger.gmane.org 1442502088 5372 80.91.229.3 (17 Sep 2015 15:01:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 17 Sep 2015 15:01:28 +0000 (UTC) Cc: 21505@debbugs.gnu.org, tsdh@gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Sep 17 17:01:16 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZcagV-0000Yf-Ro for geb-bug-gnu-emacs@m.gmane.org; Thu, 17 Sep 2015 17:01:16 +0200 Original-Received: from localhost ([::1]:59219 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZcagV-0000Yn-Hw for geb-bug-gnu-emacs@m.gmane.org; Thu, 17 Sep 2015 11:01:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58073) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZcagO-0000Yb-A7 for bug-gnu-emacs@gnu.org; Thu, 17 Sep 2015 11:01:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZcagI-0004OW-BW for bug-gnu-emacs@gnu.org; Thu, 17 Sep 2015 11:01:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:44032) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZcagI-0004OS-6g for bug-gnu-emacs@gnu.org; Thu, 17 Sep 2015 11:01:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1ZcagI-0007rx-1k for bug-gnu-emacs@gnu.org; Thu, 17 Sep 2015 11:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: hoppe Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 17 Sep 2015 15:01:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21505 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 21505-submit@debbugs.gnu.org id=B21505.144250201030122 (code B ref 21505); Thu, 17 Sep 2015 15:01:01 +0000 Original-Received: (at 21505) by debbugs.gnu.org; 17 Sep 2015 15:00:10 +0000 Original-Received: from localhost ([127.0.0.1]:36242 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1ZcafP-0007pk-BU for submit@debbugs.gnu.org; Thu, 17 Sep 2015 11:00:09 -0400 Original-Received: from mail-ig0-f175.google.com ([209.85.213.175]:38095) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1ZcafJ-0007ol-BZ for 21505@debbugs.gnu.org; Thu, 17 Sep 2015 11:00:04 -0400 Original-Received: by igxx6 with SMTP id x6so15904751igx.1 for <21505@debbugs.gnu.org>; Thu, 17 Sep 2015 08:00:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=y7aRRC3RSjVj+/ZvwtzNMMIyRuWawHuIMQBTuWjdw2Q=; b=w7SogZkPCiDjVpO4d4sJ9JKiJVrRLswKV0vRLMfCOg58Z2LRn/0Ays6QPFDqEjAr8i u1bted5c/+thWRsWx/ixMphJXPpm9jtWEWDJoPiNeEGJ18a99d1apo8B5pg+mhqJqTo/ qLBRIpm2Fhp20Upiv32KxlX1YlTbCmfOxWwfQ8VVaSs2MtsNh0T5pqI6v99umTseDwxk 2aEivqzznAVTgAa/A57WVa87lpCcy8BTYbQXzHdi6ntsnsH54pu6y4BQcYsryc/Fcz3+ l9rVA2HzS9wnxhBZ+QA3JzHt9xcNMUINpvqmvO/AhHKi+TOXMqRn894yv4afmQSSSHIp Sk7Q== X-Received: by 10.50.64.210 with SMTP id q18mr26357257igs.15.1442502000411; Thu, 17 Sep 2015 08:00:00 -0700 (PDT) Original-Received: by 10.107.142.133 with HTTP; Thu, 17 Sep 2015 07:59:41 -0700 (PDT) In-Reply-To: <83twqtqene.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:106689 Archived-At: --047d7bd75cf8528a6b051ff2abc6 Content-Type: text/plain; charset=UTF-8 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]. On Thu, Sep 17, 2015 at 10:55 AM, Eli Zaretskii wrote: > > From: Stefan Monnier > > Cc: Eli Zaretskii , 21505@debbugs.gnu.org, > travis.hoppe@gmail.com > > Date: Thu, 17 Sep 2015 08:50:33 -0400 > > > > > 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. > > > > That's right. And same for "emacs x a b". > > > > 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). > > The questions I asked the OP still stand. The required feature is not > defined in sufficient detail. If only the initial order is required, > it's probably relatively easy, but then that order is very fragile and > could easily break as soon as the user issues the first command. > --047d7bd75cf8528a6b051ff2abc6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In r= esponse to the first question, I'd like this to be the "easy"= request, that this behavior is only for when emacs opens and not continuou= sly during the session. I agree, it does not need to be maintained during t= he session.=C2=A0

= Re: Tassilo Horn:=C2=A0I purposely showed my = example with a wildcard since emacs could be given any expansion from the s= hell. 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 th= e messages and scratch buffer. Opening the files in the order given from th= e 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=C2=A0[b,c,*messages*,*scratch*, a].=C2=A0


On Thu, Sep 17, 2015 at= 10:55 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org= >,=C2=A0 21505@debbugs.gnu.org<= /a>,=C2=A0 travis.hoppe@gmail.com=
> Date: Thu, 17 Sep 2015 08:50:33 -0400
>
> > No, it should always be as given to emacs/emacsclient, i.e., when= I
> > invoke
> >
> >=C2=A0 =C2=A0$ 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.=C2=A0 Right now, x will be selected, but a and b are far = away.
>
> That's right.=C2=A0 And same for "emacs x a b".
>
> The precise behavior is a bit more complex since those commands, rathe= r
> 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).

The questions I asked the OP still stand.=C2=A0 The required feature= is not
defined in sufficient detail.=C2=A0 If only the initial order is required,<= br> it's probably relatively easy, but then that order is very fragile and<= br> could easily break as soon as the user issues the first command.

--047d7bd75cf8528a6b051ff2abc6--