bug#10729: 24.0.93; On MS-Windows: emacsclientw.exe -n -c does create a new frame, but does not always display the requested file or the requested directory (24.0.92 does)

[Juanma Barranquero <lekktu@gmail.com>]

On Sun, Feb 5, 2012 at 00:41, Albert <ab.for.lists@gmail.com> wrote:

> My shortcut in SendTo using emacsclientw -n -c no longer works in
> emacs 24.0.93 (it did work in 24.0.92)

What does it mean that it did work in .92? It always started a new frame?

> This is a simpler reproducible example:
>
> 1. command window started from emacs/bin
> 2. start runemacs -Q
> 3. M-x server-start
> 4. start emacsclientw -n -c test.txt
> ==> (small existing file) this works as expected (a new frame with test.txt)
> 5. repeat 4.: does not work: the second frame now displays an extra instance
>   of *scratch*
> 6. repeat 4.: does work: a new frame with test.txt
> 7. repeat 4.: does not work: the last frame now shows *scratch* (and
> all other frames also)
> 8. ... this repeats itself; I tried until I had 4 frames showing
> *scratch* and then the next repeat gives a new frame with test.txt
> again.

OK, I can reproduce it. And it does not depend on emacsclientw.exe, it
also fails with emacsclient.exe.

> Doing this in 24.0.92: no new frame is created, even after repeating
> there is only one frame, but always with test.txt in it

Yes. There was a change in .93 to fix a problem with -n, and also make
-c -and -t always start a new frame on Windows. It's more consistent,
and allows the users to run emacsclientw?.exe with -c or -t and not
have to worry whether the Emacs server was started as a GUI or console
application.

> (This is strange: in the scenario with my shortcut I always get a new
> frame with 24.0.92)

If you're seeing different behavior between running emacsclientw.exe
from a console and running it as a shortcut, please file another bug
with a step-by-step recipe, so I can reproduce it and test it.

> I hope this is a useful example.

Yes, thanks. I'll try to fix it ASAP.

    Juanma