all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: describe-mode should mention the .el file of the mode
Date: Tue, 31 Aug 2004 13:56:15 -0600	[thread overview]
Message-ID: <4134D7DF.7060209@yahoo.com> (raw)
In-Reply-To: mailman.887.1093976083.1998.bug-gnu-emacs@gnu.org

Dan Jacobson wrote:
 > K> No, that would be overkill.  If you want to see the source code of the
 > K> major mode function, type `C-h v major-mode', click on the function
 > K> name, then click on the file name.  You suggestion would only save the
 > K> user 1 mouse click, hardly worth it.
 >
 > We examine the differences,

Between the output of `C-h m' in Text mode and in Makefile mode --
why?

...

 > As we see, with the present C-h m, we are denied the juicy link.
 > Instead Mr. Rodgers proposes the user translate "Makefile" into
 > "makefile-mode", "Text" into "text-mode", and hit some more keys, for
 > fear of overkill.

No, I propose that the user let Emacs translate `major-mode' into
`text-mode' or `makefile-mode' for him/her.  But my claim that the
difference between your request and this approach was only 1 mouse
failed to consider the 10 characters in "major-mode".  Like this:

(defun describe-major-mode-function ()
   "*Display the full documentation of the `major-mode' function."
   (interactive)
   (describe-function major-mode))

-- 
Kevin Rodgers

  parent reply	other threads:[~2004-08-31 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.559.1093742942.1998.bug-gnu-emacs@gnu.org>
2004-08-30 18:41 ` describe-mode should mention the .el file of the mode Kevin Rodgers
2004-08-31 17:37   ` Dan Jacobson
     [not found]   ` <mailman.887.1093976083.1998.bug-gnu-emacs@gnu.org>
2004-08-31 19:56     ` Kevin Rodgers [this message]
2004-08-28 18:53 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4134D7DF.7060209@yahoo.com \
    --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 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.