unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Zachary Kanfer <zkanfer@gmail.com>
Cc: 2176@debbugs.gnu.org
Subject: bug#2176: 2176 proposal
Date: Tue, 26 Jul 2011 00:58:31 -0400	[thread overview]
Message-ID: <E1QlZix-0005Cj-Q3@fencepost.gnu.org> (raw)
In-Reply-To: <CAFXT+RN+VoEm4kRWUpyxP6WjYa=CF8eDMQg+KK3Sp6tF9v4TBw@mail.gmail.com> (message from Zachary Kanfer on Mon, 25 Jul 2011 23:13:00 -0400)

> From: Zachary Kanfer <zkanfer@gmail.com>
> Date: Mon, 25 Jul 2011 23:13:00 -0400
> 
> This patch makes the line include a link to run 'recover-session .
> It also rephrases the text. The text used to be "If an Emacs session crashed
> recently, type Meta-x recover-session RET \nto recover the files you were
> editing." The rephrased text is "If Emacs crashed recently, you may recover
> your previous session."
> The text no longer tells you how to run the command (i.e., with Meta-x
> recover-session RET). This is in line with the other commands on the page
> (e.g., Emacs Tutorial, Open a File).

Recovering a crashed session is much more important than visiting a
tutorial or opening a file.  I would understand and support a
suggestion to _add_ a clickable link, but why would you want to remove
the information about invoking recovery by hand?  A user whose session
crashed may be under pressure, and not immediately recognize the
significance of the blue underlined portion of the text.





  reply	other threads:[~2011-07-26  4:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <hgr62gupgg.fsf@fencepost.gnu.org>
2011-07-26  3:13 ` bug#2176: 2176 proposal Zachary Kanfer
2011-07-26  4:58   ` Eli Zaretskii [this message]
2011-07-28  5:59     ` Zachary Kanfer
2012-04-11 12:40       ` Lars Magne Ingebrigtsen
2012-12-01  2:12 ` bug#2176: Observations on the splash screen - and signal-process Chong Yidong

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=E1QlZix-0005Cj-Q3@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=2176@debbugs.gnu.org \
    --cc=zkanfer@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).