all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 54993@debbugs.gnu.org
Subject: bug#54993: 28.1; Editing etc/NEWS on master with Emacs 28 signals an error
Date: Mon, 18 Apr 2022 11:34:59 +0200	[thread overview]
Message-ID: <87y202ka4c.fsf@gnus.org> (raw)
In-Reply-To: <83ee1uwxl5.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 Apr 2022 12:27:18 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Really, I very much object to this disruption of my long-time workflow
> of working on Emacs, which is that I almost always use the released
> version of Emacs and not the development version.  I can work around
> this, but the need to come up with a good workaround is in itself
> almost an insult.  And it goes against the basic principle that people
> who want a feature should bear the burden of having it.

You're seeing insults where there aren't any.  And I've posted code that
you can use to avoid having your work flow disrupted.

You're demanding that all Emacs developers that want to use the new and
handy mode alter their .emacs files, instead of doing so yourself.
Isn't that almost an insult?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-04-18  9:34 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17 17:44 bug#54993: 28.1; Editing etc/NEWS on master with Emacs 28 signals an error Eli Zaretskii
2022-04-17 18:38 ` Lars Ingebrigtsen
2022-04-17 18:49   ` Eli Zaretskii
2022-04-17 18:54     ` Lars Ingebrigtsen
2022-04-17 19:15       ` Eli Zaretskii
2022-04-17 19:37         ` Lars Ingebrigtsen
2022-04-17 20:12           ` Eli Zaretskii
2022-04-18  8:40         ` Michael Albinus
2022-04-18  8:45           ` Lars Ingebrigtsen
2022-04-18  8:48             ` Michael Albinus
2022-04-18  8:56               ` Michael Albinus
2022-04-18  9:35                 ` Lars Ingebrigtsen
2022-04-18  9:27           ` Eli Zaretskii
2022-04-18  9:34             ` Lars Ingebrigtsen [this message]
2022-04-18  9:36               ` Eli Zaretskii
2022-04-18 10:08             ` Michael Albinus
2022-04-18 10:45               ` Eli Zaretskii
2022-04-18 11:12                 ` Lars Ingebrigtsen
2022-04-18 14:15                   ` Eli Zaretskii
2022-04-19 12:04                     ` Lars Ingebrigtsen
2022-04-17 20:17 ` Jim Porter
2022-04-17 20:27   ` Lars Ingebrigtsen
2022-04-17 21:32   ` Lars Ingebrigtsen
2022-04-18  8:41     ` Lars Ingebrigtsen
2022-04-18  8:44       ` Lars Ingebrigtsen
2022-04-18 19:05         ` Juri Linkov
2022-04-19 12:10           ` Lars Ingebrigtsen
2022-04-19 13:18             ` Michael Albinus
2022-04-19 13:21               ` Lars Ingebrigtsen
2022-04-19 19:15             ` Juri Linkov
2022-04-20  6:22               ` Kévin Le Gouguec
2022-04-20 10:49                 ` Lars Ingebrigtsen
2022-04-18 16:48       ` Jim Porter
2022-04-19 12:08         ` Lars Ingebrigtsen
2022-04-19 13:56           ` Lars Ingebrigtsen
2022-04-19 14:24             ` Lars Ingebrigtsen
2022-04-19 16:06               ` Eli Zaretskii
2022-04-20  6:14                 ` Kévin Le Gouguec
2022-04-20  6:46                   ` Eli Zaretskii
2022-04-20 10:45                 ` Lars Ingebrigtsen
2022-04-20 12:28                   ` Eli Zaretskii
2022-04-21 11:32                     ` Lars Ingebrigtsen
2022-04-19 16:09               ` Lars Ingebrigtsen

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=87y202ka4c.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=54993@debbugs.gnu.org \
    --cc=eliz@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 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.