From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: New ELPA package ada-lite
Date: Wed, 17 Aug 2022 18:08:48 -0700 [thread overview]
Message-ID: <86k076fjdr.fsf@stephe-leake.org> (raw)
In-Reply-To: <8335dvdqku.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 17 Aug 2022 15:04:01 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stephen Leake <stephen_leake@stephe-leake.org>
>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
>> Date: Wed, 17 Aug 2022 02:56:58 -0700
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > Would it make sense to have the lite mode in core?
>>
>> I don't think so; that would mean any use of ada-mode would cause a
>> conflict in auto-mode-alist.
>
> Why would they conflict? Or, IOW, why wouldn't it be possible to make
> them not conflict, assuming that no one will activate both modes in
> the same buffer?
ada-mode does this:
(add-to-list 'auto-mode-alist '("\\.ad[abs]\\'" . ada-mode))
ada-lite-mode does this:
(add-to-list 'auto-mode-alist '("\\.ad[abs]\\'" . ada-lite-mode))
Whichever is done last ends up first in auto-mode-alist, and is the one
that (assoc ".ads" auto-mode-alist) returns.
See also Stefan's reply.
--
-- Stephe
next prev parent reply other threads:[~2022-08-18 1:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 17:56 New ELPA package ada-lite Stephen Leake
2022-08-15 19:04 ` Stefan Monnier
2022-08-16 2:25 ` Eli Zaretskii
2022-08-17 9:56 ` Stephen Leake
2022-08-17 12:04 ` Eli Zaretskii
2022-08-18 1:08 ` Stephen Leake [this message]
2022-08-18 6:33 ` Eli Zaretskii
2022-08-17 9:50 ` Stephen Leake
2022-08-17 10:56 ` Rudolf Schlatte
2022-08-17 11:49 ` Stefan Monnier
2022-08-18 1:23 ` Stephen Leake
2022-08-18 2:02 ` Stefan Monnier
2022-08-19 11:05 ` Felician Nemeth
2022-08-19 14:24 ` [SPAM UNSURE] " Stephen Leake
2023-01-05 22:53 ` Fernando Oleo Blanco
2023-01-07 0:38 ` Stephen Leake
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=86k076fjdr.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 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).