all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Le Wang <l26wang@gmail.com>
To: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: command chains feature request
Date: Mon, 29 Oct 2012 23:23:53 +0800	[thread overview]
Message-ID: <CAM=K+io8Skn5w8wYqDhjck2DpszPVPMRhb5Xg0nu7VCB13PS0A@mail.gmail.com> (raw)

Hi all,

Here is an example scenario: I have multiple minor-modes that bind to
space key.

In xxx if I'm at the beginning of a comment, then it indents the whole
comment.  In mode yyy if I'm at the beginning of paired delimiters, it
adds padding spaces to the end as well.  The exact details of these
modes aren't crucial.

Now xxx and yyy authors are smarty pantsesses.  They decided to write
their commands such that if the context doesn't require special
action, instead of inserting spaces, they'd just lookup the current
key-binding the the last input event (taking their minor-mode out of
consideration).  In this way both modes share the space key very
happily.

However when I do "C-h k SPC", the help documentation does not show me
this current state of things.  Instead it shows me the help for
whichever command currently has higher priority.

Autopair does some on the fly doc generation magic to say what the
fallback command is, but that's not ideal since the fallback could
have its own fallback.

Can Emacs have some features that make writing inter-operable commands
easier, as well as generating help that explains the chain of commands
in fallback order?

I'm sure this isn't the right forum for a feature request.  But we can
discuss it here first.

-- 
Le



             reply	other threads:[~2012-10-29 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 15:23 Le Wang [this message]
     [not found] <mailman.11925.1351524250.855.help-gnu-emacs@gnu.org>
2012-10-31 14:58 ` command chains feature request Stefan Monnier

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='CAM=K+io8Skn5w8wYqDhjck2DpszPVPMRhb5Xg0nu7VCB13PS0A@mail.gmail.com' \
    --to=l26wang@gmail.com \
    --cc=help-gnu-emacs@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.