unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Problems with whole buffer Custom functions.
Date: Tue, 17 Jan 2006 17:29:09 -0700	[thread overview]
Message-ID: <dqk24o$bng$1@sea.gmane.org> (raw)
In-Reply-To: <87mzhuy0z7.fsf@jurta.org>

Juri Linkov wrote:
>>Of course, ordinary self-inserting characters _should_ self-insert in
>>editable fields.  But note that TAB still moves to next button or
>>editable field (I guess that list should now also include "link").
>>S-TAB also has its regular meaning, but the recently added M-TAB does
>>not, because it has another (completion related) meaning in editable
>>fields.
> 
> 
> I think this is mostly a documentation problem.  `C-h m' on a customization
> buffer suggests using `n' and `p' instead of better `TAB' and `S-TAB':
> 
>   Move to next button or editable field.     n
>   Move to previous button or editable field. p
>   Complete content of editable text field.   M-TAB

Would M-n and M-p be better?

> Adding `\\<widget-keymap>\' before first two lines above in the docstring
> of `custom-mode' to force displaying keybindings from `widget-keymap', the
> output of `C-h m' is still not good:
> 
>   Move to next button or editable field.     TAB
>   Move to previous button or editable field. M-TAB
>   Complete content of editable text field.   M-TAB
> 
> Note duplicate `M-TAB' for different contexts.

Would that go away if M-n and M-p were in front of (i.e. added later
than) TAB and M-TAB in widget-keymap?

-- 
Kevin Rodgers

  reply	other threads:[~2006-01-18  0:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13  3:32 Problems with whole buffer Custom functions Luc Teirlinck
2006-01-17  1:27 ` Juri Linkov
2006-01-17  4:13   ` Luc Teirlinck
2006-01-17 21:54     ` Juri Linkov
2006-01-18  0:29       ` Kevin Rodgers [this message]
2006-01-23  0:10       ` Richard M. Stallman
2006-01-22  0:45     ` Juri Linkov
2006-01-22  1:46       ` Luc Teirlinck
2006-01-23  1:42         ` Juri Linkov
2006-01-24 16:46           ` Richard M. Stallman
2006-01-24 21:45             ` Juri Linkov
2006-01-24 23:11               ` Lennart Borgman
2006-01-25  7:55                 ` Juri Linkov
2006-01-25 15:45               ` Richard M. Stallman
2006-01-22  1:55       ` Luc Teirlinck
2006-01-23  1:43         ` Juri Linkov
2006-01-22  0:45     ` Juri Linkov
2006-01-22 17:44       ` Richard M. Stallman
2006-01-19 17:44   ` Richard M. Stallman
2006-01-22  0:45     ` Juri Linkov
2006-01-22 17:44       ` Richard M. Stallman
2006-01-22 21:28         ` Drew Adams
2006-01-23  1:47           ` Juri Linkov
2006-01-23  2:58             ` Drew Adams
2006-01-23  6:17               ` Juri Linkov
2006-01-24 16:47           ` Richard M. Stallman
2006-01-23  1:47         ` Juri Linkov
2006-01-24 16:46           ` Richard M. Stallman
2006-01-23 18:04         ` martin rudalics
2006-01-25  3:28           ` Richard M. Stallman
2006-01-22 17:44       ` Richard M. Stallman
  -- strict thread matches above, loose matches on Subject: below --
2006-01-25  8:58 LENNART BORGMAN

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='dqk24o$bng$1@sea.gmane.org' \
    --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.
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).