From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: brownts@troybrown.dev, monnier@iro.umontreal.ca, 73280@debbugs.gnu.org
Subject: bug#73280: 30.0.90; Eglot: eglot-workspace-configuration might not be found in .dir-locals.el
Date: Mon, 16 Sep 2024 21:43:50 +0300 [thread overview]
Message-ID: <8634lzcuc9.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm50eujnBd7nrUJWHKbcmtZkmp52Z7kNHGUOnfvMSEb4hmQ@mail.gmail.com> (message from João Távora on Mon, 16 Sep 2024 19:39:03 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 16 Sep 2024 19:39:03 +0100
> Cc: Troy Brown <brownts@troybrown.dev>, monnier@iro.umontreal.ca, 73280@debbugs.gnu.org
>
> On Mon, Sep 16, 2024 at 7:15 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > I'd like to think that in a not-so-distant future, _everyone_ will
> > guess that. Why not? it makes perfect sense to me.
>
> I mean, we can fix this one if we really want to. Or make a separate
> entry just for sh-mode. In fact the user can do that if she is very
> bothered by this: this is defcustom after all. I must say I don't find
> any compelling arguments to worry much about this bug, except
> that maybe some note in the documentation could be
> added.
Fixing documentation is fine by me, thanks.
next prev parent reply other threads:[~2024-09-16 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 19:54 bug#73280: 30.0.90; Eglot: eglot-workspace-configuration might not be found in .dir-locals.el Troy Brown
2024-09-16 11:38 ` Eli Zaretskii
2024-09-16 13:48 ` João Távora
2024-09-16 17:07 ` Troy Brown
2024-09-16 18:15 ` Eli Zaretskii
2024-09-16 18:39 ` João Távora
2024-09-16 18:43 ` Eli Zaretskii [this message]
2024-09-16 18:53 ` Troy Brown
2024-09-16 19:07 ` João Távora
2024-09-16 21:34 ` Troy Brown
2024-09-16 19:17 ` Eli Zaretskii
2024-09-16 21:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8634lzcuc9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73280@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).