From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Le Wang Newsgroups: gmane.emacs.help Subject: command chains feature request Date: Mon, 29 Oct 2012 23:23:53 +0800 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1351524254 27422 80.91.229.3 (29 Oct 2012 15:24:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Oct 2012 15:24:14 +0000 (UTC) To: GNU Emacs List Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Oct 29 16:24:23 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TSrCQ-0002HC-3e for geh-help-gnu-emacs@m.gmane.org; Mon, 29 Oct 2012 16:24:22 +0100 Original-Received: from localhost ([::1]:40951 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSrCH-0006Fg-PQ for geh-help-gnu-emacs@m.gmane.org; Mon, 29 Oct 2012 11:24:13 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43730) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSrC7-0006Ec-QI for help-gnu-emacs@gnu.org; Mon, 29 Oct 2012 11:24:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TSrBy-0005Hm-AJ for help-gnu-emacs@gnu.org; Mon, 29 Oct 2012 11:24:03 -0400 Original-Received: from mail-qc0-f169.google.com ([209.85.216.169]:49871) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TSrBy-0005He-6f for help-gnu-emacs@gnu.org; Mon, 29 Oct 2012 11:23:54 -0400 Original-Received: by mail-qc0-f169.google.com with SMTP id t2so3189098qcq.0 for ; Mon, 29 Oct 2012 08:23:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=xN8Q2XglaHvGrRGAx625cHhjHWPZdaeovaYANEoB9ys=; b=t3MaApsKdpEDtJb4Nio1kgnnOpf4oJw6aqixgBK3qkX5h86XbIe/CyhZYeh+cAjsJ4 DunV6AcQUrSk2SxGl0200TyLZyklVmUk7ICHDFqkZt0VbmMpu93X6E8wcyr3x/vcXCKO iK9ikPh+WdX5WunMsQQV8zxzZNVltf4CZkNmZmX11w+00jmVtCgGRVVj8+Bw8jEvypvl 1u88NX3RKuJkKAaUpQG7LqS6n6hnAR3ub1xonEmUWg5V/2BbaDuVfc7j1WBXARpAxcsC lSKl6gm4S6SBphsctzJK+Uwgrk/F+R8SC3FkzTAnVVph5wA9v2m8cQvCu4eGYq/YnkMH ToiQ== Original-Received: by 10.224.27.140 with SMTP id i12mr16399038qac.15.1351524233806; Mon, 29 Oct 2012 08:23:53 -0700 (PDT) Original-Received: by 10.49.94.48 with HTTP; Mon, 29 Oct 2012 08:23:53 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.216.169 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:87484 Archived-At: 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