unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 4960@emacsbugs.donarmstrong.com
Subject: bug#4960: 23.1.50; Please provide access to the tour on the Help  menu; preferably ship it also
Date: Fri, 20 Nov 2009 11:32:07 +0200	[thread overview]
Message-ID: <87ws1lzksg.fsf@mail.jurta.org> (raw)
In-Reply-To: <e01d8a50911190427h6e2f8c1brca105a869e0b7a08@mail.gmail.com> (Lennart Borgman's message of "Thu, 19 Nov 2009 13:27:07 +0100")

>> Previous discussion:
>>
>> http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00120.html
>
> There seemed to be a consensus to change part of the Help menu the way
> Drew suggested:
>
>   http://lists.gnu.org/archive/html/emacs-devel/2008-11/msg00158.html
>
> Though Stefan and someone else thought that a menu item that opened
> something in a web browser felt a bit wrong. I never understood why.
> Is not that very common?
>
> I suggest we change the Help menu as discussed there.

The Web Guided Tour is an advertisement of Emacs features.
It doesn't provide any help.  So the "Help" menu is not appropriate.
We could create a new menu "Ads" ;-)

BTW, I noticed that the About screen doesn't say that the link
will start the browser (like it says on the startup screen).
Here is a fix:

Index: lisp/startup.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/startup.el,v
retrieving revision 1.550
diff -u -r1.550 startup.el
--- lisp/startup.el	6 Nov 2009 05:16:28 -0000	1.550
+++ lisp/startup.el	20 Nov 2009 09:31:21 -0000
@@ -1371,7 +1371,7 @@
      :link ("Emacs Guided Tour"
 	    (lambda (button) (browse-url "http://www.gnu.org/software/emacs/tour/"))
 	    "Browse http://www.gnu.org/software/emacs/tour/")
-     "\tSee an overview of the many facilities of GNU Emacs"
+     "\tSee an overview of Emacs facilities at gnu.org"
      ))
   "A list of texts to show in the middle part of the About screen.
 Each element in the list should be a list of strings or pairs

-- 
Juri Linkov
http://www.jurta.org/emacs/





  parent reply	other threads:[~2009-11-20  9:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  3:15 bug#4960: 23.1.50; Please provide access to the tour on the Help menu; preferably ship it also Jason A. Spiro
2009-11-19  8:03 ` Glenn Morris
2009-11-19 12:27   ` Lennart Borgman
2009-11-19 13:34     ` Joel J. Adamson
2009-11-19 14:06       ` Lennart Borgman
2009-11-20  9:32     ` Juri Linkov [this message]
2009-11-20 10:53       ` Kevin Rodgers
2009-11-20 11:14         ` Juri Linkov
2009-11-20 12:06       ` Lennart Borgman
2020-04-28 17:28       ` Stefan Kangas
2020-05-12 14:58         ` Stefan Kangas
2009-11-19 13:35 ` Joel J. Adamson
2009-11-19 14:08   ` Lennart Borgman

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=87ws1lzksg.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=4960@emacsbugs.donarmstrong.com \
    --cc=lennart.borgman@gmail.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 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).