all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Xah Lee <xah@xahlee.org>
Cc: emacs-devel@gnu.org
Subject: Re: Fiddling with the menus
Date: Sun, 09 Aug 2009 01:05:35 -0400	[thread overview]
Message-ID: <jwvskg1629o.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <jwv3a817kui.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 08 Aug 2009 23:36:04 -0400")

[ Sorry, hit C-c C-c before it was time.  Here's the rest of the list. ]

> Emacs 22's Tool menu.

> The menu items for rmail and gnus do not work out of the box, because
> these features need operating system's support and setup that requires
> some sys admin expertise.

Agreed.  The way to fix it is to make M-x rmail and/or M-x gnus run some
kind of "wizard" to configure them.

> Today, vast majority of people use web based email services, even
> among professional programers.  Also, unlike the situation of the
> 1980s and 1990s, where most programer's “workstation” machines running
> unix are setup to run sendmail services. Today, even linux users, most
> are probably not setup to run sendmail.  Microsoft Windows, today used
> by ~95% of personal computer users world wide, does not come with
> “sendmail”.  Mac OS X uses PostFix as its MTA and is not enabled
> by default.

By "sendmail", this menu entry means sendmail.el which uses
the "sendmail" command provided by most/all MTAs, including Postfix.
Sadly, this command is commonly non-functional, so here again,
sendmail.el should run some kind of wizard to make sure that sending
email is properly configured.

> It is questionable, that the gnus and rmail should have a menu item.

These are important packages that deserve to have a visible entry point.

> For those programers who might want to use these and have the
> expertise to set it up, they can most certainly find out about these
> features online or in the Emacs documentation.  For the Emacs
> die-hards accustomized to using rmail or gnus, they never actually
> pull these menus to invoke the commands.  They simply type “M-x rmail”
> or “M-x gnus”.

Not necessarily: they may temporarily be using Emacs without access to
a keyboard.

> The game items seem a bit silly.

Maybe, but it costs just one entry.

> For Emacs to showoff a game, it should at least show a outstanding
> implementation, or some game that has merits to stands itself.  (A
> typing game implemented in elisp would be suitable, or a Emacs
> interface to GNU Go, GNU Chess,

Agreed, these would be good.

> or music player.)

Not exactly a game.

> Emacs's help menu. Extremely confusing and chaotic.

> In the Emacs's help menu, there are about 30 items. With this many
> items, they are more confusing than helpful.  Many of these are
> outdated, redundant, never used, or FSF propaganda.  The following are
> some explanation.

The Emacs maintainers consider FSF propaganda to be important.

> The content of “Emacs FAQ”, “Emacs News”, “Emacs Known Problems”, are
> about 5 or 10 years out of date.

If Emacs News is out of date, it's a bug.

The "known problems" indeed tend to be very out of date, tho not all of
them are.  We should probably split this file into sections for problems
which have been reported for specific releases (with a note that
problems in older releases may still be relevant).

The FAQ's maintenance has always been a bit problematic, indeed.  I'd be
happy to drop it.

> Similarly, the “External Packages” is hopelessly outdated.  For this,
> the emacswiki (emacswiki.org) provides far more useful resource.

We could link to some web page on www.gnu.org.  But we need someone to
keep it up-to-date.  Maybe along with ELPA.

> The “Find Emacs Packages” item has rather confusing name. After using
> Emacs 8 hours a day for 10 years, i pulled it today for the first
> time, and realized it is a keyword based search on bundled elisp
> packages. Looking at the result, it does not seems very useful. For
> example, clicking on OOP shows a bunch of modes that really have
> little to do with Object Oriented Programing. Perhaps it should go
> into the “Search Documentation” sub-menu.

This command needs a lot of work to make it useful, I find.

> The “Emacs Psychotherapist” is the forefront of AI research in the
> 1960s. (It is a implementation of ELIZA) Having it in 1980s is way
> cool. Having it in 1990s in a text editor is a novelty. Today, as
> a demo of elisp power or as a fun program, it's rather stupid.

I'd call it silly, and silliness is a quality.

> The “Getting New Versions”, “Copying Condition”, “(Non)Warranty” are
> all redundant.

I don't see how they're redundant.  But yes, “Getting New Versions”
sounds old.  It should probably link to www.gnu.org/software/emacs.

> In today's web info world, it's silly that a Emacs
> users would pull a menu to know where to get new versions.  A modern
> replacement should be “Check Update” that tells user if his Emacs is
> up to date, or better, automatically upgrade Emacs as a option.
> Such a feature is common in all modern apps.

Under GNU/Linux this doesn't belong in the application but in the
distribution, and indeed it works just fine for Emacs just like it works
for all other applications.
For other platforms, we could imagine better support for installers and
semi-automatic update, but not until someone writes them.

> The “Copying Condition” and “(Non)Warranty” are part of the licensing
> and user agreement.  No app today has it as a menu item.  All 3 items,
> are linked in the “About Emacs” menu item's doc, and that is
> sufficient and appropriate.

Oh, that's what you meant by redundant, then I think I agree.

> The “About GNU” is Richard Stallman's FSF propaganda.  Its inclusion
> in Emacs's Help menu is more about politics than as a helpful resource
> for the Emacs software.  The Emacs manual has FSF propaganda littered
> throughout already.  This menu item burdens the Help menu with another
> non-helpful item.  Again, “About Emacs” has a link to it already.

Politics matter.

> The items in “More Manuals” sub-menu, can all be gone except the “All
> Other Manuals (Info)” and the the “Lookup Subject in all manuals...”
> (info-apropos).  The “All Other Manuals (Info)” should be moved to the
> top, and serve as the one entry point for all manuals, and the
> info-apropos menu item can move to the “Search Documentation”
> sub menu.

That sounds OK.


        Stefan




  parent reply	other threads:[~2009-08-09  5:05 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  3:22 bug#4043: 23.1; thanks for emacs 23! xah lee
2009-08-06  2:15 ` Richard Stallman
2009-08-08 16:11   ` Xah Lee
2009-08-09  3:36     ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Stefan Monnier
2009-08-09  3:53       ` Lennart Borgman
2009-08-09  5:13         ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs Stefan Monnier
2009-08-09 17:20         ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Eli Zaretskii
2009-08-09 17:56           ` Lennart Borgman
2009-08-09 18:02             ` Eli Zaretskii
2009-08-09 18:10               ` Lennart Borgman
2009-08-09 18:15                 ` Eli Zaretskii
2009-08-09 18:21                   ` Lennart Borgman
2009-08-09 18:51                     ` Eli Zaretskii
2009-08-09 18:54                       ` Lennart Borgman
2009-08-09 18:57                         ` Eli Zaretskii
2009-08-09 18:55                 ` Eli Zaretskii
2009-08-09 19:07                   ` Lennart Borgman
2009-08-09 20:36                     ` Lennart Borgman
2009-08-09 23:00                       ` Fiddling with the menus Jason Rumney
2009-08-09 23:14                         ` Lennart Borgman
2009-08-09 23:46                           ` Jason Rumney
2009-08-10  1:51                       ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Stephen J. Turnbull
2009-08-10  3:03                       ` Eli Zaretskii
2009-08-10  3:26                         ` Lennart Borgman
2009-08-10  2:27               ` Fiddling with the menus Stefan Monnier
2009-08-10  2:32                 ` Lennart Borgman
2009-08-09  5:05       ` Stefan Monnier [this message]
2009-08-09  9:51         ` CHENG Gao
2009-08-09 17:38           ` Eli Zaretskii
2009-08-09 18:06             ` CHENG Gao
2009-08-09 18:17               ` Eli Zaretskii
2009-08-09 18:24                 ` Lennart Borgman
2009-08-09 18:54                   ` Eli Zaretskii
2009-08-09 18:59                     ` Lennart Borgman
2009-08-09 22:54                     ` Jason Rumney
2009-08-10  1:12               ` Stefan Monnier
2009-08-09 17:50         ` Eli Zaretskii
2009-08-09 23:14           ` Juri Linkov
2009-08-10  2:32             ` Stefan Monnier
2009-08-10  3:07             ` Eli Zaretskii
2009-08-11  5:06         ` Dan Nicolaescu
2009-08-11 13:03           ` Lennart Borgman
2009-08-09 12:37       ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Florian Beck
2009-08-09 17:52         ` Eli Zaretskii
2009-08-09 17:26       ` Eli Zaretskii
2009-08-09 18:05         ` Fiddling with the menus Richard Riley
2009-08-09 18:14           ` Eli Zaretskii
2009-08-10  2:09         ` Stefan Monnier
2009-08-10  3:16           ` Eli Zaretskii
2009-08-09 23:09       ` Juri Linkov
2009-08-09 23:29         ` Lennart Borgman
2009-08-10  0:10           ` Drew Adams
2009-08-10  2:22           ` Stefan Monnier
2009-08-09 20:29     ` bug#4043: 23.1; thanks for emacs 23! Richard Stallman

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=jwvskg1629o.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=xah@xahlee.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.