From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, jp@neverwas.me, philipk@posteo.net,
emacs-devel@gnu.org
Subject: Re: New Eglot release
Date: Sun, 12 Mar 2023 19:12:01 +0000 [thread overview]
Message-ID: <87a60hrdha.fsf@gmail.com> (raw)
In-Reply-To: <83ttyqv67f.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Mar 2023 08:23:16 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: João Távora <joaotavora@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, jp@neverwas.me, philipk@posteo.net,
>> emacs-devel@gnu.org
>> Date: Sat, 11 Mar 2023 20:16:07 +0000
>>
>> Michael Albinus <michael.albinus@gmx.de> writes:
>>
>> > There is the samll disadvantage that it shows the file readonly. But
>> > that's an annoyance only for somebody who wants to edit the file, and it
>> > can be fixed then by "M-x emacs-news-mode".
>>
>> I'm tempted to do that, but the annoyance might be too much, methings.
>
> Doesn't "C-x C-q" solve that with a single command?
That's why I was tempted, but thinking that this file is to be edited by
other users, like the ones proposing new features over at bug#62116 and
github#839, and knowing that these users are not always familiar with
Emacs' development, this could be a source of confusion. As in "should
I be editing this read-only file?". A small hindrance, of course, but
the somewhat frivolous cosmetics we gain in exchange aren't worth it,
IMO. Better to fix emacs-news-mode.
João
prev parent reply other threads:[~2023-03-12 19:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 20:02 New Eglot release João Távora
2023-03-05 5:50 ` Eli Zaretskii
2023-03-05 9:09 ` Michael Albinus
2023-03-05 15:30 ` João Távora
2023-03-05 15:37 ` Dmitry Gutov
2023-03-05 15:47 ` Eli Zaretskii
2023-03-05 15:56 ` Philip Kaludercic
2023-03-05 22:15 ` João Távora
2023-03-06 17:33 ` Philip Kaludercic
2023-03-06 17:33 ` Philip Kaludercic
2023-03-07 14:54 ` F. Jason Park
2023-03-10 11:38 ` João Távora
2023-03-10 12:23 ` Eli Zaretskii
2023-03-10 12:50 ` João Távora
2023-03-10 13:06 ` Eli Zaretskii
2023-03-10 13:42 ` João Távora
2023-03-11 15:11 ` Michael Albinus
2023-03-11 20:16 ` João Távora
2023-03-12 6:23 ` Eli Zaretskii
2023-03-12 19:12 ` João Távora [this message]
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=87a60hrdha.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jp@neverwas.me \
--cc=michael.albinus@gmx.de \
--cc=philipk@posteo.net \
/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).