From: storm@cua.dk (Kim F. Storm)
Subject: Re: Shall menu_bar_items and tool_bar_items look at text property keymaps?
Date: 15 Feb 2002 12:39:45 +0100 [thread overview]
Message-ID: <5xk7tfgeim.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200202151036.g1FAacl07300@santafe.santafe.edu>
Richard Stallman <rms@gnu.org> writes:
> Since it doesn't really work, I doubt anyone is actually using it.
>
> So my proposal is to remove the "look for keymaps at PT" from those
> functions.
>
> Why change this at all? Is there a bug that needs fixing here?
> If so, what is it?
It is a bug: If a programmer puts a menu-bar or tool-bar binding into
a keymap or local-map text property, that will not work realiable.
Instead of trying to make it work (which will involve a severe performance
penalty), I suggest to remove the code and document in the Elisp manual
that those text property maps don't support menu-bar and tool-bar bindings.
In the specific situation, I was investigating how to add a new type
of keymap (details may follow later :-) when I stumbled across the
(seemingly) bogus code in keyboard.c. So I decided to ask my fellow
developers whether that code was really needed -- or it could be
removed -- to simplify the task of adding the new type of keymap - in
which case I could just remove the bogus code instead of adding more
(bogus) code.
>
> I'm concerned because Emacs developers are putting a large fraction of
> their time into areas that are attractive for programmers to work on,
> but not a large fraction into areas that really help users. We need
> to shift the effort to places where it will make Emacs more
> powerful or more convenient or easier to learn and use.
I know you regularly express this concern, and I fully agree with you!
There is no need to spend time on features which are not visible to
the user.
However, I feel that this concern sometimes is used to reject changes
to the "core" emacs that would subsequently make it *significantly*
easier (for the programmer) to write packages which *does* make emacs
better (for the user) in the ways you express above.
And with emacs, a lisp package programmer (like me) is also a user!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-15 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 0:01 Shall menu_bar_items and tool_bar_items look at text property keymaps? Kim F. Storm
2002-02-13 16:52 ` Stefan Monnier
2002-02-13 21:26 ` Kim F. Storm
2002-02-14 3:12 ` Richard Stallman
2002-02-14 8:57 ` Kim F. Storm
2002-02-15 10:36 ` Richard Stallman
2002-02-15 11:39 ` Kim F. Storm [this message]
2002-02-16 21:56 ` Richard Stallman
2002-02-20 15:28 ` Kim F. Storm
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=5xk7tfgeim.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
/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).