[Emacs-bug-tracker] bug#8984: closed (second emacsclient file argument ends up in buried buffer)

[GNU bug Tracking System]

Your message dated Thu, 07 Jul 2011 09:38:16 +0800
with message-id <address@hidden>
and subject line Re: bug#8984: second emacsclient file argument ends up in 
buried buffer
has caused the GNU bug report #8984,
regarding second emacsclient file argument ends up in buried buffer
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
8984: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8984
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> 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.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> 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 <address@hidden> writes:
> JB> On Thu, Jul 7, 2011 at 02:03,  <address@hidden> 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.
>
>
> --- End Message ---