From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: elisp mouse programming problems
Date: Fri, 22 Aug 2003 09:24:21 -0600 [thread overview]
Message-ID: <3F4635A5.1000009@yahoo.com> (raw)
In-Reply-To: L7adnTTa6o979diiRTvUqw@texas.net
David Vanderschel wrote:
> "Kevin Rodgers" <ihs_4664@yahoo.com> wrote in message
> news:3F4504F2.60600@yahoo.com...
>
>>David Vanderschel wrote:
>>
>
>>>I think I have now figured this one out. Changing the
>>>mode-map itself is not sufficient. You must again
>>>invoke (use-local-map whatever-mode-map).
>>>
>
>
>>That is not true. As Alex explained, when you modify the keymap, you
>>are modifying a part of its list structure that is shared by the
>>variable and the mode.
>>
>
>
> Then I still do not understand how to get emacs to use
> the revised keymap. For one thing I am not modifying
> _the_ keymap - I am creating a new one.
Ah, I didn't realize that.
> I am sorry if
> I am being a bit dense here. I think the implication
> must be that replacing the map pointed to by my
> variable still leaves the system with a pointer to the
> old cdr.
Sorry, I was the dense one. You are correct.
> So are you saying that it is essential to
> replace the cdr _in_ the old list, as opposed to
> replacing the entire list itself?
>
> Eg., (setf (cdr my-map) (cdr new-map)), as opposed to
> (setq my-map new-map).
>
> Why wouldn't invoking use-local-map again also
> accomplish the same goal?
It would.
--
Kevin Rodgers
next prev parent reply other threads:[~2003-08-22 15:24 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 [this message]
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
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=3F4635A5.1000009@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).