unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 8158@debbugs.gnu.org, Reuben Thomas <rrt@sc3d.org>
Subject: bug#8158: Definition of auto-mode-alist
Date: Thu, 21 Oct 2021 13:29:08 -0700	[thread overview]
Message-ID: <CADwFkmnqPWWX-c=g8GF_Cn6oMfHC4sGzbK9=wy8a3zDdSept6A@mail.gmail.com> (raw)
In-Reply-To: <jwvvczzwmdi.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 03 Mar 2011 23:22:03 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>   ;; Note: The entries for the modes defined in cc-mode.el (c-mode,
>>   ;; c++-mode, java-mode and more) are added through autoload
>>   ;; directives in that file.  That way is discouraged since it
>>   ;; spreads out the definition of the initial value.
>
>> Isn't this a bit unmodular as Emacs continues to grow, and given loaddefs.el?
>
> I agree, but I think Richard disagrees.  Also, order of entries in
> auto-mode-alist can be important, so autoloading those entries does not
> work for all cases.  But for 90% of the cases, it's perfectly fine and
> indeed we do use it already in several cases.
>
> Such ordering conflicts are difficult to detect automatically: detecting
> them when we compile Emacs requires checking which regexps overlap
> (which is perfectly doable in theory, but we'd need a "regexp-to-DFA
> compiler" for that, basically), detecting them at run-time is too late
> (often it'd be wrong to ask the user to resolve such conflicts).

Does anyone object to just removing the above comment?  And similarly
for `interpreter-mode-alist', I suppose.





  reply	other threads:[~2021-10-21 20:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 22:02 bug#8158: Definition of auto-mode-alist Reuben Thomas
2011-03-02 22:18 ` Lennart Borgman
2011-03-02 22:22   ` Reuben Thomas
2011-03-02 22:30     ` Lennart Borgman
2011-03-02 22:35       ` Reuben Thomas
2011-03-02 23:14         ` Lennart Borgman
2011-03-02 23:21           ` Reuben Thomas
2011-03-02 23:39             ` Lennart Borgman
2011-03-02 23:41               ` Reuben Thomas
2011-03-02 23:42                 ` Lennart Borgman
2011-03-02 23:43                   ` Reuben Thomas
2011-03-03  0:30                     ` Lennart Borgman
2011-03-03 11:43                       ` Reuben Thomas
2011-03-04  4:22           ` Stefan Monnier
2011-03-04  4:22 ` Stefan Monnier
2021-10-21 20:29   ` Stefan Kangas [this message]
2021-10-22 14:31     ` Lars Ingebrigtsen
2022-01-27  3:14       ` Stefan Kangas
2021-10-22 23:45     ` Richard Stallman
2021-10-23  0:15       ` Stefan Kangas

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='CADwFkmnqPWWX-c=g8GF_Cn6oMfHC4sGzbK9=wy8a3zDdSept6A@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=8158@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rrt@sc3d.org \
    /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).