unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Jacobson <jidanni@jidanni.org>
Subject: describe-mode should first summarize all modes in effect
Date: Sat, 27 Sep 2003 12:59:57 +0800	[thread overview]
Message-ID: <87wubux1v6.fsf_-_@jidanni.org> (raw)
In-Reply-To: <3F7301EF.5030701@yahoo.com> (Kevin Rodgers's message of "Thu, 25 Sep 2003 08:55:43 -0600")

Indeed, emacs lacks a command to show concisely what all those mode
abbreviations crammed in the modeline stand for.  There should be a
function explain-modeline-modes, that puts them in the minibuffer.
Kevin's function below could be enhanced to do that.

Better yet, have describe-mode output Kevin's  list at the top of its
output, before getting mired in detail.

K> Dan Jacobson wrote:
>>>> By the way, aside from blabberous describe-mode, and staring at the
>>>> mode line, where is a concise list of the current modes in effect?
>>>> There is no list-modes, show-modes, etc.
K> C-x C-b (list-buffers) shows each buffer's major mode.
>> I meant a list of all the modes in effect for this buffer.  Yes,
>> there
>> they are mostly in the modeline, but how about a lisp list?


K> If you need it, you could write it yourself:

K> (defun buffer-mode-list ()
K>    "Return a list of the current buffer's major mode and minor modes."
K>    (interactive)
K>    (let ((modes (cons major-mode
K>                       (apply 'nconc
K>                              (mapcar (lambda (key-value)
K>                                        (let ((variable (car key-value)))
K>                                          (if (and (boundp variable)
K>                                                   (symbol-value variable))
K>                                              (list (symbol-name variable)))))
K>                                      minor-mode-alist)))))
K>      (if (interactive-p)
K>          (message "%s" modes)
K>        modes)))

  parent reply	other threads:[~2003-09-27  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.443.1064004252.21628.bug-gnu-emacs@gnu.org>
2003-09-22 15:29 ` report-emacs-bug could also list current modes Kevin Rodgers
2003-09-24 21:46   ` stop rewriting Message-IDs Dan Jacobson
2003-09-24 21:50   ` report-emacs-bug could also list current modes Dan Jacobson
     [not found]   ` <mailman.677.1064447066.21628.bug-gnu-emacs@gnu.org>
2003-09-25 14:55     ` Kevin Rodgers
2003-09-25 16:16       ` Andreas Schwab
2003-09-27  4:59       ` Dan Jacobson [this message]
     [not found]       ` <mailman.819.1064714879.21628.bug-gnu-emacs@gnu.org>
2003-09-29 17:10         ` describe-mode should first summarize all modes in effect Kevin Rodgers
2003-10-02 22:27           ` Dan Jacobson

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=87wubux1v6.fsf_-_@jidanni.org \
    --to=jidanni@jidanni.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 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).