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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: jidanni <at> jidanni.org
Subject: bug#8984: closed (Re: bug#8984: second emacsclient file argument
 ends up in buried buffer)
Date: Thu, 07 Jul 2011 01:39:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#8984: second emacsclient file argument ends up in buried buffer

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 8984 <at> debbugs.gnu.org.

-- 
8984: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8984
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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.

[Message part 3 (message/rfc822, inline)]

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.

Previous Next

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