unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Joel J. Adamson" <adamsonj@email.unc.edu>
To: Lennart Borgman <lennart.borgman@gmail.com>,
	4960@emacsbugs.donarmstrong.com,
	bug-submit-list@donarmstrong.com
Cc: Emacs Bugs <bug-gnu-emacs@gnu.org>
Subject: bug#4960: 23.1.50; Please provide access to the tour on the Help menu; preferably ship it also
Date: Thu, 19 Nov 2009 08:34:11 -0500	[thread overview]
Message-ID: <16272.1258637651@chondestes.bio.unc.edu> (raw)
In-Reply-To: <e01d8a50911190427h6e2f8c1brca105a869e0b7a08@mail.gmail.com>

>>>>> "Lennart" == Lennart Borgman <lennart.borgman@gmail.com> writes:

    > On Thu, Nov 19, 2009 at 9:03 AM, Glenn Morris <rgm@gnu.org> wrote:
    >> 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?

It may be common, but that doesn't mean it's good.  I find myself rather
unnerved when I go to a help Menu expecting to find some *help
documentation* and instead get sent to a website that acts mainly as
advertisement.

Of course in the case of Emacs it would be a link to something useful.
However, users should be made fully aware that they will be opening a
web browser.  And what would you do to make sure the browser is properly
configured?

Joel
-- 
Joel J. Adamson	-- http://www.unc.edu/~adamsonj
University of North Carolina at Chapel Hill
CB #3280, Coker Hall
Chapel Hill, NC 27599-3280





  reply	other threads:[~2009-11-19 13:34 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 [this message]
2009-11-19 14:06       ` Lennart Borgman
2009-11-20  9:32     ` Juri Linkov
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=16272.1258637651@chondestes.bio.unc.edu \
    --to=adamsonj@email.unc.edu \
    --cc=4960@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=bug-submit-list@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).