all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Reducing mouse-dependency In Emacs.
Date: Wed, 13 Aug 2003 20:04:20 -0500 (CDT)	[thread overview]
Message-ID: <200308140104.h7E14Kq26672@raven.dms.auburn.edu> (raw)
In-Reply-To: <16186.49695.437995.793551@nick.uklinux.net> (message from Nick Roberts on Wed, 13 Aug 2003 23:56:31 +0100)

Nick Roberts wrote:

   In the mouseless scenario, the help is displayed in the echo
   area. However, this doesn't happen when point is over a widget but
   when the user types <tab> (widget-forward) or <S-tab>
   (widget-backward). This is less distracting and fits well with
   earlier comments about emacspeak. Could you not do something
   similar with next-help-echo-region and previous-help-echo-region?

Nobody is going to be distracted without asking to be.  The
information would only show up either on explicit demand or through a
customizable option, where even some extra flexibility would be
provided, and that would not be enabled by default.

I believe that I will indeed make `next-help-echo-region' and
`previous-help-echo-region' automatically call `print-local-help',
since the user probably wants it, if he is calling those functions.  I
do not really believe this is a _substitute_ for call on demand,
however.  Moreover, some people may want the information shown
automatically, especially in the case of `keymap' and `local-map'
properties, which are both not that frequent and important to know
about.  I believe I am going to provide an option to show automatic
help only if one of those two properties are present, as well as
options to show all help automatically or no help automatically (the
default).

Sincerely,

Luc.

  parent reply	other threads:[~2003-08-14  1:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13  5:36 Reducing mouse-dependency In Emacs Luc Teirlinck
2003-08-13  7:47 ` Miles Bader
2003-08-13 12:59   ` Luc Teirlinck
2003-08-13 22:56     ` Nick Roberts
2003-08-14  0:35       ` Luc Teirlinck
2003-08-14  1:42         ` Miles Bader
2003-08-14  1:04       ` Luc Teirlinck [this message]
2003-08-13 14:32   ` Luc Teirlinck
  -- strict thread matches above, loose matches on Subject: below --
2003-08-12  2:49 Luc Teirlinck
2003-08-12  1:29 Luc Teirlinck
2003-08-12  1:43 ` Luc Teirlinck
2003-08-10  3:42 Luc Teirlinck
2003-08-10  6:08 ` Eli Zaretskii
2003-08-10 14:53   ` Luc Teirlinck
2003-08-11 12:53   ` Richard Stallman
2003-08-10 16:50 ` Stefan Monnier
2003-08-10 23:09   ` Luc Teirlinck
2003-08-11  4:05     ` Luc Teirlinck
2003-08-11 23:16       ` Richard Stallman
2003-08-11  6:04     ` Eli Zaretskii
2003-08-11 15:52       ` Luc Teirlinck
2003-08-11 17:52         ` Eli Zaretskii
2003-08-11 14:54     ` Stefan Monnier
2003-08-12  2:30       ` Luc Teirlinck
2003-08-12  6:28         ` Eli Zaretskii
2003-08-12 16:08           ` Luc Teirlinck

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=200308140104.h7E14Kq26672@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    /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.