all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Mike Kupfer <mkupfer@alum.berkeley.edu>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
	50743@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#50743: Emacsclient not tested vs. Local Variables prompt
Date: Sun, 26 Sep 2021 13:34:11 +1300	[thread overview]
Message-ID: <b75b3aca7e6204b7812cf37a02e1d173@webmail.orcon.net.nz> (raw)
In-Reply-To: <25731.1632610542@alto>

On 2021-09-26 11:55, Mike Kupfer wrote:
> I don't use icewm, but I can reproduce the problem with MATE,
> using either the marco window manager or Openbox, on Debian 10.

Thanks for confirming Mike.

I can now reproduce this as well.  (In fact I'd failed to follow
the correct recipe previously, and was side-stepping the issue.)

The key appears to be whether or not we're using a pre-existing
client frame.  If a new frame is created, the problem does not
occur (for me).  If we're switching to a pre-existing frame, then
I can reproduce the problem.

Here's an alternative recipe:

emacs -Q --daemon=bug50743 # start a new server
emacsclient -sbug50743 -c & # create a GUI frame
emacsclient -sbug50743 <file>

If <file> contains file-local variables then the pre-existing
client frame does not get focus; but otherwise it does.

I tested with both:

M-x add-file-local-variable
M-x add-file-local-variable-prop-line



-Phil






  parent reply	other threads:[~2021-09-26  0:34 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 20:16 bug#50743: Emacsclient not tested vs. Local Variables prompt 積丹尼 Dan Jacobson
2021-09-22 20:40 ` Lars Ingebrigtsen
2021-09-23  5:43   ` 積丹尼 Dan Jacobson
2021-09-23  6:54     ` Phil Sainty
2021-09-24  8:23       ` 積丹尼 Dan Jacobson
2021-09-24 14:11     ` Phil Sainty
2021-09-24 14:42       ` 積丹尼 Dan Jacobson
2021-09-25  1:12         ` Phil Sainty
2021-09-25  4:18           ` 積丹尼 Dan Jacobson
2021-09-25  5:07             ` Phil Sainty
2021-09-25  5:46               ` 積丹尼 Dan Jacobson
2021-09-25  8:33                 ` Phil Sainty
2021-09-25 13:06                   ` 積丹尼 Dan Jacobson
2021-09-25 14:02                     ` Phil Sainty
2021-09-25 22:55                       ` Mike Kupfer
2021-09-26  0:19                         ` Mike Kupfer
2021-09-26  2:57                           ` Mike Kupfer
2021-09-26  0:34                         ` Phil Sainty [this message]
2021-09-26  2:48                           ` Mike Kupfer
2021-09-26  6:25                           ` Eli Zaretskii
2021-09-26  9:12                             ` martin rudalics
2021-09-26  9:19                               ` Eli Zaretskii
2021-09-26  9:59                                 ` martin rudalics
2021-09-26 11:03                                   ` Eli Zaretskii
2021-09-26 17:50                                     ` martin rudalics
2021-09-26 18:19                                       ` Eli Zaretskii
2021-09-27  8:50                                         ` martin rudalics
2021-09-27 14:32                                           ` Jean Louis
2021-09-27 17:15                                             ` martin rudalics
2021-09-26 17:51                                     ` Mike Kupfer
2021-09-26 18:26                                       ` Eli Zaretskii
2021-09-26 22:08                                         ` Mike Kupfer
2021-09-27  4:48                                           ` Eli Zaretskii
2021-09-27  8:50                                       ` martin rudalics
2021-09-27 14:35                               ` Jean Louis
2021-09-26 17:02                             ` Mike Kupfer
2021-09-26  6:53 ` 積丹尼 Dan Jacobson
2021-09-26  7:12   ` Eli Zaretskii
2021-09-26  7:20     ` 積丹尼 Dan Jacobson
2021-09-26  7:31 ` 積丹尼 Dan Jacobson
2021-09-26  7:41 ` 積丹尼 Dan Jacobson
2021-09-26 20:49 ` 積丹尼 Dan Jacobson
2021-09-27  4:43   ` Eli Zaretskii
2021-09-27 17:30   ` 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

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

  git send-email \
    --in-reply-to=b75b3aca7e6204b7812cf37a02e1d173@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=50743@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    --cc=mkupfer@alum.berkeley.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.