From: Phil Sainty <psainty@orcon.net.nz>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 50743@debbugs.gnu.org
Subject: bug#50743: Emacsclient not tested vs. Local Variables prompt
Date: Thu, 23 Sep 2021 18:54:20 +1200 [thread overview]
Message-ID: <1a7a85b02fbc99ae5df066453d57b531@webmail.orcon.net.nz> (raw)
In-Reply-To: <87ilyr978n.5.fsf@jidanni.org>
On 2021-09-23 17:43, 積丹尼 Dan Jacobson wrote:
> All I know is with these
> https://www.jidanni.org/comp/configuration/
> files, and this file:
> $ cat /tmp/m
> ## -- -*- so-long-action: normal-mode; -*-
> $ emacsclient -n /tmp/m
> reproduces the bug.
1. Do you see the same thing with ANY file-local variable?
2. Do you see the same thing if you use '-Q' when starting the server?
3. Do you see the same thing without the '-n' option?
For (1) please test with something like -*- foo: bar; -*- (i.e. any
name which isn't a known variable) so that we have an idea of whether
this is connected to so-long.el in any way.
Also, per our conversation the other day, that 'normal-mode' is a
misleading value -- unless you've defined a custom action by that
name, it's no different to specifying any other invalid action, and
merely means that so-long won't do very much.
-Phil
next prev parent reply other threads:[~2021-09-23 6:54 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 [this message]
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
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
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=1a7a85b02fbc99ae5df066453d57b531@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=50743@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
/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).