unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Albert <ab.for.lists@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 10729@debbugs.gnu.org
Subject: 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)
Date: Mon, 6 Feb 2012 18:47:46 +0100	[thread overview]
Message-ID: <CAJs9Ju-REG8LROwr88PT4ThPXWsSW2e6q6GfQJt-cTEarARftw@mail.gmail.com> (raw)
In-Reply-To: <CAAeL0SQtM+VcpatPkk06N34rKixa3Ut6EVUWw3VfHfa9ajZYqA@mail.gmail.com>

Hi,

Is it ok to reply like this? (To you and to the bugnumber)

Thanks for the explanation and for the workaround tip. It seems to
work (also for my original problem).

In my original report I made a remark about the shortcut behaving
differently than my command prompt experiments.
I have now found the reason: I had set server-window to
switch-to-buffer-other-frame in my customization files. In that case a
new frame is created, but the frame contains the original buffer
instead of the new one (the new one is also not listed in the buffer
list). Repeating the procedure gives the same result. I suspect that
with the new code in 24.0.93 the reason for using
switch-to-buffer-other-frame has disappeared, but the new buffer also
in that case ought to end up at least somewhere. Since I suspect that
the mechanism behind this behaviour is the same as in the original
case I post this remark here, instead of reporting a new bug.

Albert.





  reply	other threads:[~2012-02-06 17:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 23:41 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) Albert
2012-02-05 15:48 ` Juanma Barranquero
2012-02-06 17:03   ` Juanma Barranquero
2012-02-06 17:47     ` Albert [this message]
2012-02-06 21:06       ` Juanma Barranquero
2012-02-06 17:57     ` martin rudalics
2012-02-06 21:11       ` Juanma Barranquero
2012-02-07  7:53         ` martin rudalics
2012-02-07 13:08           ` Juanma Barranquero
2012-02-07 13:31             ` Juanma Barranquero
2012-02-07 13:33               ` Juanma Barranquero
2012-02-07 14:32                 ` martin rudalics
2012-02-07 14:35                   ` Juanma Barranquero
2012-02-07 15:21                     ` martin rudalics
2012-02-07 15:28                       ` Juanma Barranquero
2012-02-07 17:05                         ` martin rudalics
2012-02-07 17:27                   ` Stefan Monnier
2012-02-08 12:24                     ` Juanma Barranquero
2012-02-07 15:22             ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJs9Ju-REG8LROwr88PT4ThPXWsSW2e6q6GfQJt-cTEarARftw@mail.gmail.com \
    --to=ab.for.lists@gmail.com \
    --cc=10729@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).