unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: C-h K and C-h F in the Help menu
Date: Sat, 20 May 2006 23:19:02 +0200	[thread overview]
Message-ID: <446F87C6.4090109@student.lu.se> (raw)
In-Reply-To: <uk68gxwsf.fsf@gnu.org>

Eli Zaretskii wrote:
> "Find Key in Manual" and "Find Command in Manual" are in the "More
> Manuals" submenu of the "Help" menu.  I think they should either in
> "Search Documentation" or in "Describe", because these two submenus
> are about Emacs, while "More Manuals" is about manuals of other
> packages.
>
> Does anyone object to moving these two items?
>
>   
Sounds ok to me.

I recently got some comments about the help menu in CVS Emacs from a 
long term Emacs user and fan (+15 y usage). One of the comments were 
that there are too many things in the help menu. I wonder if it could 
help if it was restructured a bit more again? Some suggestions for quick 
fixes:

- Just one tutorial entry with two subentries:

    Tutorial
        Tutorial in English
        Tutorial in other languages

- Just one bug entry with two subentries:

    Emacs Problems and Bugs
        Emacs Known Problems
        Send Bug Report

- Just one about entry:

    About Emacs
        Welcome Screen
        Copying Conditions
        (Non)Warranty
        Getting New Versions

- Move "Find Emacs Packages" to under "Search Documentation"

Another complaint was that the manual is not easily available in HTML 
which is the "standard" today. Could perhaps the Emacs Info node start 
with a link to a description of how to get the manual in HTML format?

  reply	other threads:[~2006-05-20 21:19 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20 20:32 C-h K and C-h F in the Help menu Eli Zaretskii
2006-05-20 21:19 ` Lennart Borgman [this message]
2006-05-20 21:38   ` David Kastrup
2006-05-20 21:54     ` Lennart Borgman
2006-05-20 22:10       ` David Kastrup
2006-05-20 22:28         ` Lennart Borgman
2006-05-20 22:48           ` David Kastrup
2006-05-20 23:00             ` Lennart Borgman
2006-05-20 23:08               ` David Kastrup
2006-05-20 23:16                 ` Lennart Borgman
2006-05-20 23:20                   ` David Kastrup
2006-05-21  3:35                     ` Eli Zaretskii
2006-05-21  3:36                   ` Eli Zaretskii
2006-05-21  9:31             ` Slawomir Nowaczyk
2006-05-21  3:38           ` Eli Zaretskii
2006-05-20 22:44         ` Mathias Dahl
2006-05-20 22:56           ` David Kastrup
2006-05-20 23:02             ` Lennart Borgman
2006-05-20 23:09               ` David Kastrup
2006-05-20 23:13                 ` Lennart Borgman
2006-05-20 23:22                   ` David Kastrup
2006-05-21  9:57             ` Mathias Dahl
2006-05-21 10:11               ` David Kastrup
2006-05-21 10:13               ` Andreas Schwab
2006-05-21 18:48               ` Eli Zaretskii
2006-05-21  3:43       ` Eli Zaretskii
2006-05-22  2:38         ` Richard Stallman
2006-05-22  2:56           ` Luc Teirlinck
2006-05-22  3:36             ` Eli Zaretskii
2006-05-22 20:36             ` Richard Stallman
2006-05-22  8:57           ` Lennart Borgman
2006-05-21  4:27     ` Juri Linkov
2006-05-21  3:42   ` Eli Zaretskii
2006-05-21  7:38     ` Lennart Borgman
2006-05-21 18:46       ` Eli Zaretskii
2006-05-21 21:04       ` Alan Mackenzie
2006-05-21 23:13         ` Lennart Borgman
2006-05-22 15:12           ` Richard Stallman
2006-05-22 16:53             ` Drew Adams
2006-05-22 21:49               ` Lennart Borgman
2006-05-22 18:39             ` Eli Zaretskii
2006-05-23  0:42               ` Richard Stallman
2006-05-23  3:21                 ` Eli Zaretskii
2006-05-22  3:23         ` Eli Zaretskii
2006-05-21 17:08   ` Richard Stallman
2006-05-21 17:08   ` Richard Stallman
2006-05-21  4:27 ` Juri Linkov
2006-05-21 17:08 ` Richard Stallman
2006-05-26 20:02   ` Eli Zaretskii

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=446F87C6.4090109@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --cc=emacs-devel@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 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).