From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: elisp mouse programming problems
Date: Fri, 22 Aug 2003 09:20:01 -0600 [thread overview]
Message-ID: <3F4634A1.1060506@yahoo.com> (raw)
In-Reply-To: 5vucncb0uK2Q-NiiRTvUqw@texas.net
David Vanderschel wrote:
> "Alex Schroeder" <alex@emacswiki.org> wrote in message
> news:87y8xnfbip.fsf@emacswiki.org...
>
>>"David Vanderschel" <DJV1@Austin.RR.com> writes:
>>
>
>>>How can a general purpose program like I am trying to make know, in
>>>general, which minor modes it must disable in order to work
>>>properly? I feel that I must still be missing something here.
>>>
>
>>I think you have just discovered one of the weaker points in the Emacs
>>user interface design. The problem is, nobody knows what to do about
>>it. :) ...
>>
>
> One possibility that did occur to me last night was
> that my program could itself introduce a new minor
> mode, invoke it, and do something to assure that its
> keymap is at the front of the list. Then it _could_
> override the bindings of other minor modes. Yet you
> did not suggest this solution. Is there some reason
> why it would not work?
Since another minor mode might prepend its (VARIABLE . KEYMPAP) entry to
minor-mode-map-alist later, you would have to continually check and possibly
modify it, perhaps with post-command-hook. It'd be a bit of a performance hit,
and not very elegant.
--
Kevin Rodgers
next prev parent reply other threads:[~2003-08-22 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 3:17 elisp mouse programming problems David Vanderschel
2003-08-20 10:34 ` Alex Schroeder
2003-08-21 1:46 ` David Vanderschel
2003-08-21 2:37 ` Johan Bockgård
2003-08-21 3:24 ` David Vanderschel
2003-08-21 17:44 ` Kevin Rodgers
2003-08-22 0:50 ` David Vanderschel
2003-08-22 15:24 ` Kevin Rodgers
2003-08-20 11:40 ` Eli Zaretskii
[not found] ` <mailman.542.1061395718.29551.help-gnu-emacs@gnu.org>
2003-08-21 3:12 ` David Vanderschel
2003-08-21 12:19 ` Alex Schroeder
2003-08-22 0:34 ` David Vanderschel
2003-08-22 15:20 ` Kevin Rodgers [this message]
2003-08-27 17:45 ` Kai Großjohann
2003-08-27 20:27 ` Kai Großjohann
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=3F4634A1.1060506@yahoo.com \
--to=ihs_4664@yahoo.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.
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).