From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: foreground menu bug
Date: Mon, 27 Jun 2005 10:22:15 +0200 [thread overview]
Message-ID: <uhdfk5hvs.fsf@gmail.com> (raw)
In-Reply-To: E1DmP2F-0006rG-0k@fencepost.gnu.org
"Richard M. Stallman" <rms@gnu.org> writes:
> Or, it could just warn the user that the highlighting will not be
> visible since font lock is enabled?
>
> It would be possible, but why be so complicated?
> This change seems to do the right job.
Assuming the user notices that we disabled the menu item, your fix
might work. What about users who use M-x apropos or similar to find
commands and then used enter the commands with M-x, how would they
know that this comment is currently "disabled", or not meant to be
used?
Also, what does a disabled menu item tell the user? He might not
understand that it is because font lock is enabled. He might wonder if
he is doing something wrong seeing that menu item disabled.
I think this is a bad idea which just avoids solving the real
problem. If we disable the menu item, which is one way for the user to
execute the command, we should also disabled the other ways to execute
that command. Or make the command warn the user in some way.
next prev parent reply other threads:[~2005-06-27 8:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 5:16 foreground menu bug Werner LEMBERG
2005-06-15 13:28 ` Mathias Dahl
2005-06-16 4:07 ` Richard Stallman
2005-06-20 9:08 ` Lute Kamstra
2005-06-21 8:09 ` Mathias Dahl
2005-06-26 4:46 ` Richard M. Stallman
2005-06-26 10:30 ` Lute Kamstra
2005-06-26 22:42 ` Richard M. Stallman
2005-06-27 8:22 ` Mathias Dahl [this message]
2005-06-28 4:16 ` Richard M. Stallman
2005-06-28 8:18 ` Mathias Dahl
2005-06-16 11:51 ` Lute Kamstra
2005-06-17 4:38 ` Richard Stallman
2005-06-17 11:19 ` Lute Kamstra
2005-06-20 8:38 ` Lute Kamstra
2005-06-27 13:14 ` Werner LEMBERG
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uhdfk5hvs.fsf@gmail.com \
--to=brakjoller@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.