unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Problems with whole buffer Custom functions.
Date: Sun, 22 Jan 2006 12:44:02 -0500	[thread overview]
Message-ID: <E1F0jFy-00063z-MG@fencepost.gnu.org> (raw)
In-Reply-To: <877j8tcsyt.fsf@jurta.org> (message from Juri Linkov on Sun, 22 Jan 2006 02:45:17 +0200)

    I'd reserve M-n and M-p in editable fields for history navigation.

I don't think this is necessary, because there is already an undo
mechanism (the "backup value").

Instead I think it should preserve the ordinary undo list when you set
the variable.  Currently, setting the variable discards the undo list,
which is more or less a bug.

However, I now see that TAB does work for moving from an editable
field to the next button.  So we don't need M-n to do that.
We can stick with TAB as the one recommended way to do that.

    S-TAB is the preferable key binding, but currently it's impossible to
    specify a preferable key binding in the docstring.

The way to do that is to use two different command names.  Look at
`advertised-undo', for instance.  We could use that same technique to
make sure that S-TAB is what appears in a doc string.

However, arranging to present only S-TAB would have a drawback,
that it would not give any way to do this on a tty.

I find that M-TAB is bound to complete-symbol in custom buffers.  That
is not useful, so we could change it to widget-backwards.  However,
M-TAB in an editable field is bound to widget-complete, and we
certainly do not want to change that.

This means that no variant of TAB is suitable to be the universal way
to move to the previous widget, from all buffer positions, on all
terminals.  That is too bad.

Maybe we should define M-n and M-p for this, just to have a consistent
set of commands that move in both directions.

Or maybe we should settle for having S-TAB available only on graphics
terminals.

  reply	other threads:[~2006-01-22 17:44 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
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 [this message]
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=E1F0jFy-00063z-MG@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=teirllm@dms.auburn.edu \
    /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).