GNU bug report logs - #8984
second emacsclient file argument ends up in buried buffer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 8984 in the body.
You can then email your comments to 8984 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
Subject: second emacsclient file argument ends up in buried buffer
Date: Sat, 02 Jul 2011 05:26:20 +0800

Wben one gives more than one filename argument to emacsclient (-n), the
second file ends up in a buried buffer. One would instead expect them
both to be visible. Well at least the emacsclient man page should
document what will happen. I'm trying to say
$ emacsclient ... ...
should act the same as
$ emacs ... ...
in how the files end up displayed.

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: jidanni <at> jidanni.org
Cc: 8984 <at> debbugs.gnu.org
Subject: Re: bug#8984: second emacsclient file argument ends up in buried
	buffer
Date: Wed, 6 Jul 2011 21:35:31 +0200

On Fri, Jul 1, 2011 at 23:26,  <jidanni <at> jidanni.org> wrote:

> $ emacsclient ... ...
> should act the same as
> $ emacs ... ...
> in how the files end up displayed.

How does emacs ... ... acts for you?

For me, both 23.3 and trunk do this:

- emacs -q A  => splits the frame between A and *GNU Emacs*
- emacs -q A (B...) Z  => splits the frame between Z and *GNU Emacs*,
(B...) files are buried
- emacs -Q A  => displays A
- emacs -Q A B => displays B, A is buried
- emacs -Q A (B...) Z => splits the frame between Z and *Buffer List*,
(B...) are buried.

Does it work differently for you?

    Juanma

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

From: jidanni <at> jidanni.org
To: lekktu <at> gmail.com
Cc: 8984 <at> debbugs.gnu.org
Subject: Re: bug#8984: second emacsclient file argument ends up in buried
	buffer
Date: Thu, 07 Jul 2011 08:03:51 +0800

>>>>> "JB" == Juanma Barranquero <lekktu <at> gmail.com> writes:
JB> How does emacs ... ... acts for you?
JB> For me, both 23.3 and trunk do this:
JB> - emacs -q A  => splits the frame between A and *GNU Emacs*

This reveals another big problem that confuses our testing: -nw.

If you add -nw, the behavior becomes different once again!

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: jidanni <at> jidanni.org
Cc: 8984 <at> debbugs.gnu.org
Subject: Re: bug#8984: second emacsclient file argument ends up in buried
	buffer
Date: Thu, 7 Jul 2011 02:23:56 +0200

On Thu, Jul 7, 2011 at 02:03,  <jidanni <at> jidanni.org> wrote:

> This reveals another big problem that confuses our testing: -nw.
>
> If you add -nw, the behavior becomes different once again!

The point is that IMHO it's not worth the trouble to try to force
server.el to duplicate the behavior of "emacs xxx yyy zzz..." because
that behavior depends on several factors. There are already several
variables (server-window, server-visit-hook, server-switch-hook, etc.)
that can be used to adapt server.el to specific needs.

    Juanma

Message #19 received at 8984-done <at> debbugs.gnu.org (full text, mbox):

From: jidanni <at> jidanni.org
To: lekktu <at> gmail.com
Cc: 8984-done <at> debbugs.gnu.org
Subject: Re: bug#8984: second emacsclient file argument ends up in buried
	buffer
Date: Thu, 07 Jul 2011 09:38:16 +0800

>>>>> "JB" == Juanma Barranquero <lekktu <at> gmail.com> writes:
JB> On Thu, Jul 7, 2011 at 02:03,  <jidanni <at> jidanni.org> wrote:

>> This reveals another big problem that confuses our testing: -nw.
>> 
>> If you add -nw, the behavior becomes different once again!

JB> The point is that IMHO it's not worth the trouble to try to force
JB> server.el to duplicate the behavior of "emacs xxx yyy zzz..." because
JB> that behavior depends on several factors. There are already several
JB> variables (server-window, server-visit-hook, server-switch-hook, etc.)
JB> that can be used to adapt server.el to specific needs.

OK, agreed. I'll close this bug and open a -nw bug. Thanks.

Previous Next

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