From: Lennart Borgman <lennart.borgman@gmail.com>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>,
5062@emacsbugs.donarmstrong.com
Cc: bug-gnu-emacs@gnu.org
Subject: bug#5062: image-toggle-display overwrites nxml-mode local key map
Date: Thu, 3 Dec 2009 04:31:15 +0100 [thread overview]
Message-ID: <e01d8a50912021931s36dce597y2c884de8e9a3fe1d@mail.gmail.com> (raw)
In-Reply-To: <hf7a39$set$1@ger.gmane.org>
On Thu, Dec 3, 2009 at 4:08 AM, Kevin Rodgers <kevin.d.rodgers@gmail.com> wrote:
> Lennart Borgman wrote:
>>
>> On Thu, Dec 3, 2009 at 1:59 AM, Juri Linkov <juri@jurta.org> wrote:
>>>>>
>>>>> Or did you mean a joint mode like `c-mode-and-image-minor-mode',
>>>>> `nxml-mode-and-image-minor-mode', `ps-mode-and-doc-view-minor-mode'?
>>>>> Wouldn't this be too clumsy?
>>>>
>>>> Yes, why would it be too clumsy?
>>>>
>>>> A more flexibel way might be to use define-globalized-minor-mode. The
>>>> turn on function there could make any check. It could for example look
>>>> in a list similar to auto-mode-alist, but for minor modes.
>>>>
>>>> But maybe that would take too long time?
>>>
>>> I think Stefan's idea of allowing auto-mode-alist to have entries like
>>> ("regexp" (major-mode minor-mode-1 minor-mode-2 ...)) is more universal.
>>
>>
>> Why not allow a form there then:
>>
>> ("regexp" '(progn (major-mode) (mino-mode-1 1) (minor-mode-2 1) ...))
>
> Because it's no longer a declarative data structure that can be queried and
> modified, rather an imperative program.
Hm, yes. I use to think it is bad to put a (lambda () ...) in a hook,
because you may want to remove it later. And actually I do modify this
list to in majmodpri.el so you are right. A simple format is better.
next prev parent reply other threads:[~2009-12-03 3:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878wdixvgt.fsf@mail.jurta.org>
2009-11-28 0:44 ` bug#5062: 23.1.50; image-toggle-display overwrites nxml-mode local key map Brent Goodrick
2009-11-28 2:25 ` Stefan Monnier
2009-11-28 15:26 ` Brent Goodrick
2009-11-28 17:49 ` Juri Linkov
2009-11-28 20:21 ` Stefan Monnier
2009-11-28 22:54 ` Juri Linkov
2009-11-29 15:36 ` Stefan Monnier
2009-11-29 16:03 ` Juri Linkov
2009-11-29 18:33 ` Stefan Monnier
2009-11-29 22:00 ` Lennart Borgman
2009-11-29 22:08 ` Juri Linkov
2009-11-29 23:16 ` Lennart Borgman
2009-12-03 0:59 ` bug#5062: " Juri Linkov
2009-12-03 1:37 ` Lennart Borgman
2009-12-03 3:08 ` Kevin Rodgers
2009-12-03 3:31 ` Lennart Borgman [this message]
2009-12-03 3:30 ` Stefan Monnier
2009-12-03 0:57 ` bug#5062: 23.1.50; " Juri Linkov
2009-12-03 3:28 ` Stefan Monnier
2009-12-03 5:00 ` Jason Rumney
2009-12-04 0:05 ` Juri Linkov
2009-12-04 22:00 ` bug#5062: marked as done (23.1.50; image-toggle-display overwrites nxml-mode local key map) Emacs bug Tracking System
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=e01d8a50912021931s36dce597y2c884de8e9a3fe1d@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=5062@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=kevin.d.rodgers@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).