* bug#8984: second emacsclient file argument ends up in buried buffer
@ 2011-07-01 21:26 jidanni
2011-07-06 19:35 ` Juanma Barranquero
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: jidanni @ 2011-07-01 21:26 UTC (permalink / raw)
To: 8984
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#8984: second emacsclient file argument ends up in buried buffer
2011-07-01 21:26 bug#8984: second emacsclient file argument ends up in buried buffer jidanni
@ 2011-07-06 19:35 ` Juanma Barranquero
2011-07-07 0:03 ` jidanni
2011-07-07 1:38 ` jidanni
2 siblings, 0 replies; 5+ messages in thread
From: Juanma Barranquero @ 2011-07-06 19:35 UTC (permalink / raw)
To: jidanni; +Cc: 8984
On Fri, Jul 1, 2011 at 23:26, <jidanni@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#8984: second emacsclient file argument ends up in buried buffer
2011-07-01 21:26 bug#8984: second emacsclient file argument ends up in buried buffer jidanni
2011-07-06 19:35 ` Juanma Barranquero
@ 2011-07-07 0:03 ` jidanni
2011-07-07 0:23 ` Juanma Barranquero
2011-07-07 1:38 ` jidanni
2 siblings, 1 reply; 5+ messages in thread
From: jidanni @ 2011-07-07 0:03 UTC (permalink / raw)
To: lekktu; +Cc: 8984
>>>>> "JB" == Juanma Barranquero <lekktu@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!
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#8984: second emacsclient file argument ends up in buried buffer
2011-07-07 0:03 ` jidanni
@ 2011-07-07 0:23 ` Juanma Barranquero
0 siblings, 0 replies; 5+ messages in thread
From: Juanma Barranquero @ 2011-07-07 0:23 UTC (permalink / raw)
To: jidanni; +Cc: 8984
On Thu, Jul 7, 2011 at 02:03, <jidanni@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#8984: second emacsclient file argument ends up in buried buffer
2011-07-01 21:26 bug#8984: second emacsclient file argument ends up in buried buffer jidanni
2011-07-06 19:35 ` Juanma Barranquero
2011-07-07 0:03 ` jidanni
@ 2011-07-07 1:38 ` jidanni
2 siblings, 0 replies; 5+ messages in thread
From: jidanni @ 2011-07-07 1:38 UTC (permalink / raw)
To: lekktu; +Cc: 8984-done
>>>>> "JB" == Juanma Barranquero <lekktu@gmail.com> writes:
JB> On Thu, Jul 7, 2011 at 02:03, <jidanni@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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-07-07 1:38 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-01 21:26 bug#8984: second emacsclient file argument ends up in buried buffer jidanni
2011-07-06 19:35 ` Juanma Barranquero
2011-07-07 0:03 ` jidanni
2011-07-07 0:23 ` Juanma Barranquero
2011-07-07 1:38 ` jidanni
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).