From: Reuben Thomas <rrt@sc3d.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 8158@debbugs.gnu.org
Subject: bug#8158: Definition of auto-mode-alist
Date: Wed, 2 Mar 2011 22:35:37 +0000 [thread overview]
Message-ID: <AANLkTinbUZAci5cXQ12ppc_3WeDcFkFxZHL4fLz1CX1k@mail.gmail.com> (raw)
In-Reply-To: <AANLkTike=fMJOJPu-=DUA7WYn28yGKBuPS3r=6WwBcdS@mail.gmail.com>
On 2 March 2011 22:30, Lennart Borgman <lennart.borgman@gmail.com> wrote:
>
> I think the control of this must be given to the user and that
> requires a central system.
From the point of view of the user, the system is centralised:
auto-mode-alist and friends, which can be redefined at will.
> Just loading a new elisp file should not
> override old choices. (See above for clarification.)
Sure, but autoloaded lines from mode files aren't rerun when the mode
is loaded, are they? (At least, it seems not, because modes I have
autoloaded still only have one entry per file suffix in
auto-mode-alist.)
--
http://rrt.sc3d.org
next prev parent reply other threads:[~2011-03-02 22:35 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 [this message]
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
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=AANLkTinbUZAci5cXQ12ppc_3WeDcFkFxZHL4fLz1CX1k@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=8158@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/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).