From: "J.P." <jp@neverwas.me>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-erc@gnu.org, 63662@debbugs.gnu.org
Subject: bug#63662: 30.0.50; ERC 5.6: Document how to connect over SOCKS
Date: Fri, 02 Jun 2023 07:02:46 -0700 [thread overview]
Message-ID: <87ttvqm06x.fsf__44434.5571960852$1685714625$gmane$org@neverwas.me> (raw)
In-Reply-To: <878rd3fnv7.fsf@gmx.de> (Michael Albinus's message of "Thu, 01 Jun 2023 13:01:00 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
>>> "J.P." <jp@neverwas.me> writes:
>>>>
>>>>>> I've also taken the liberty of adding a command to view etc/ERC-NEWS
>>>>>
>>>>> Shouldn't this file be in `emacs-news-mode' (or in `emacs-news-view-mode'
>>>>> when being viewed), like etc/NEWS?
>>>>
>>>> The command I've added tries to activate `emacs-news-view-mode' if
>>>> defined, but I'm not sure we can change the actual prop line because
>>>> older Emacs versions we support (27+) don't seem to have the file
>>>> emacs-news-mode.el.
It sure took me long enough, but I think I finally understand what you
meant about changing the mode declared in the file. I guess I didn't
realize Emacs gracefully falls back to trying other listed major modes
(despite that being clearly explained in "(emacs) Specifying File
Variables"). So, unless anyone has a problem with my doing so, I'll go
ahead and update etc/ERC-NEWS accordingly. Thanks!
>>> So we might release it on GNU ELPA?
>>
>> You mean convert emacs-news-mode.el into a :core package? No clue about
>> that, I'm afraid. Apologies if I left you with a different impression.
>
> Yes. It wouldn't be useful not only for ERC-NEWS, but for all other
> packages providing a *-NEWS file. If they are willing to follow the
> conventions.
If emacs-news-mode.el does become another :core package, I suppose ERC,
eglot, and co. would be expected to add it to our ";; Package-Requires:"
headers? Another option might be to print a message upon failing to load
`emacs-news-view-mode' that informs people of its availability on GNU
ELPA.
next prev parent reply other threads:[~2023-06-02 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h6s3rwlu.fsf@neverwas.me>
2023-05-30 14:18 ` bug#63662: 30.0.50; ERC 5.6: Document how to connect over SOCKS J.P.
2023-05-30 15:23 ` Michael Albinus
2023-05-31 1:53 ` J.P.
2023-05-31 12:05 ` Michael Albinus
2023-05-31 12:47 ` Corwin Brust
2023-06-01 10:44 ` Michael Albinus
2023-05-31 14:15 ` J.P.
2023-06-01 11:01 ` Michael Albinus
2023-06-02 14:02 ` J.P. [this message]
[not found] ` <87ttvqm06x.fsf@neverwas.me>
2023-06-02 14:31 ` Michael Albinus
2023-05-23 13:44 J.P.
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='87ttvqm06x.fsf__44434.5571960852$1685714625$gmane$org@neverwas.me' \
--to=jp@neverwas.me \
--cc=63662@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
--cc=michael.albinus@gmx.de \
/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).