all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: master 0161c9d 1/2: Load all generic-x.el modes unconditionally
Date: Wed, 10 Feb 2021 10:44:35 -0600	[thread overview]
Message-ID: <CADwFkmkXJWpTfstcBjLaNTEVAotf1o=V_jT4DtBQ_wKWSFv3FQ@mail.gmail.com> (raw)
In-Reply-To: <83sg64hqzj.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> > What do we tell all those (myself included) who require generic-x in
>> > their init files?
>>
>> I don't know what they need to be told.
>> Can you clarify what broke or risks breaking because of the change?
>
> I thought it was clear: suddenly those users will have a gazillion
> modes defined they never intended to use or load or even know about.

Could we perhaps take another step back here and ask: why is that a
problem?

To my mind, I only run the risk of getting some unexpected syntax
highlighting (which would actually be welcome in my use).

If the generic modes themselves are worse than having no syntax
highlighting, they should either be fixed or removed.

What am I missing?



  reply	other threads:[~2021-02-10 16:44 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210209160550.18823.10795@vcs0.savannah.gnu.org>
     [not found] ` <20210209160551.832FB20AD1@vcs0.savannah.gnu.org>
2021-02-09 17:16   ` master 0161c9d 1/2: Load all generic-x.el modes unconditionally Lars Ingebrigtsen
2021-02-09 17:53     ` Eli Zaretskii
2021-02-09 19:45       ` Stefan Kangas
2021-02-09 20:08         ` Eli Zaretskii
2021-02-09 20:47           ` Stefan Kangas
2021-02-09 21:08             ` Eli Zaretskii
2021-02-09 21:51               ` Stefan Kangas
2021-02-09 22:00           ` Stefan Monnier
2021-02-10  3:26             ` Eli Zaretskii
2021-02-10 14:00               ` Stefan Monnier
2021-02-10 15:39                 ` Eli Zaretskii
2021-02-10 16:44                   ` Stefan Kangas [this message]
2021-02-10 17:07                     ` Stefan Monnier
2021-02-10 17:31                       ` Eli Zaretskii
2021-02-10 17:10                     ` Eli Zaretskii
2021-02-10 17:45                       ` Stefan Monnier
2021-02-10 18:29                         ` Matt Armstrong
2021-02-10 19:14                           ` Eli Zaretskii
2021-02-11 14:06                             ` Stefan Kangas
2021-02-11 14:22                           ` Stefan Kangas
2021-02-11 14:47                             ` Eli Zaretskii
2021-02-11 15:10                               ` Stefan Kangas
2021-02-11 14:38                         ` Stefan Kangas
2021-02-11 15:07                           ` Stefan Monnier
2021-02-11 17:02                             ` Stefan Kangas
2021-02-11 17:12                               ` Eli Zaretskii
2021-02-11 18:00                                 ` Stefan Kangas
2021-02-11 19:29                                   ` Eli Zaretskii
2021-02-11 21:28                                     ` Stefan Kangas
2021-02-12  6:55                                       ` Eli Zaretskii
2021-02-12 13:43                                         ` Stefan Monnier
2021-02-12 14:40                                           ` Eli Zaretskii
2021-02-12 14:46                                             ` Stefan Monnier
2021-02-12 15:07                                               ` Eli Zaretskii
2021-02-12 15:23                                                 ` Stefan Monnier
2021-02-12 15:41                                                   ` Eli Zaretskii
2021-02-12 16:17                                                     ` Stefan Monnier
2021-02-10 16:50                   ` Stefan Monnier
2021-02-10 17:22                     ` Eli Zaretskii
2021-02-10 19:22                       ` Matt Armstrong
2021-02-09 19:00     ` Stefan Monnier

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='CADwFkmkXJWpTfstcBjLaNTEVAotf1o=V_jT4DtBQ_wKWSFv3FQ@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --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 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.