[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8984: second emacsclient file argument ends up in buried buffer
From: |
Juanma Barranquero |
Subject: |
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@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