From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20697@debbugs.gnu.org
Subject: bug#20697: 25.0.50; Mention `M-x report-emacs-bug' on splash screen
Date: Wed, 21 Aug 2019 23:02:50 +0200 [thread overview]
Message-ID: <CADwFkmnmUHN6o6sVkVzfBHKP5KcOcs57TmgcOhgbKz9nJMh8wQ@mail.gmail.com> (raw)
In-Reply-To: <874l2az3r3.fsf@mouse.gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Stefan Kangas <stefan@marxist.se> writes:
>
> > "\tHow to contribute improvements to Emacs\n"
> > + :link ("Report Bugs" ,(lambda (_button) (view-emacs-howto-report-bugs)))
> > + "\tHow to report bugs in Emacs\n"
> > "\n"
>
> So this basically adds another line and links directly to the Bugs info
> page. Hm. Would it be possible to instead just change the line
>
> Contributing How to contribute improvements to Emacs
>
> to something like the following? That link already links to the bug
> reporting page...
>
> Contributing How to report bugs and contribute improvements
I had missed that, but you're absolutely correct and I agree that its
a better solution.
There was also a suggestion by Drew in the original post to mention
the Help menu as well. Is that something we want to do? But then,
wouldn't we also want to suggest C-h C-h, C-h C-i, etc.? Maybe a
better alternative would be to add the Emacs Manual at the bottom,
after the link to the guided tour? (And, but maybe that's just me, to
move all the help topics ("Emacs Tutorial", "Emacs Guided Tour") to
the top?)
Thanks,
Stefan Kangas
next prev parent reply other threads:[~2019-08-21 21:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 14:42 bug#20697: 25.0.50; Mention `M-x report-emacs-bug' on splash screen Drew Adams
2016-04-30 19:33 ` Lars Ingebrigtsen
2019-08-21 0:41 ` Stefan Kangas
2019-08-21 1:59 ` Drew Adams
2019-08-21 20:02 ` Lars Ingebrigtsen
2019-08-21 21:02 ` Stefan Kangas [this message]
2019-08-21 21:27 ` Drew Adams
2019-09-13 19:39 ` Stefan Kangas
2019-09-13 20:13 ` Drew Adams
2019-09-14 12:01 ` Stefan Kangas
2019-09-14 15:54 ` Drew Adams
2019-09-28 13:44 ` Stefan Kangas
2019-09-28 13:49 ` Stefan Kangas
2019-09-29 0:42 ` Drew Adams
2020-01-16 2:06 ` Stefan Kangas
2020-01-16 14:49 ` Eli Zaretskii
2020-01-16 14:55 ` Stefan Kangas
2020-01-16 15:16 ` Eli Zaretskii
2020-01-16 20:36 ` Stefan Kangas
2019-08-21 21:38 ` Lars Ingebrigtsen
2019-09-13 19:29 ` Stefan Kangas
2019-09-14 6:41 ` Eli Zaretskii
2019-09-14 12:06 ` Stefan Kangas
2019-09-14 12:11 ` Lars Ingebrigtsen
2019-09-28 13:39 ` Stefan Kangas
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=CADwFkmnmUHN6o6sVkVzfBHKP5KcOcs57TmgcOhgbKz9nJMh8wQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=20697@debbugs.gnu.org \
--cc=larsi@gnus.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).