From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: 16749@debbugs.gnu.org
Subject: bug#16749: More informative error when restoring frameset with killed buffer
Date: Fri, 14 Feb 2014 08:42:02 +0100 [thread overview]
Message-ID: <52FDC8CA.1060301@easy-emacs.de> (raw)
In-Reply-To: <a561oiw52x.fsf@fencepost.gnu.org>
Am 14.02.2014 08:01, schrieb Glenn Morris:
>
> PS Perhaps it should not stop with an error on encountering a dead
> buffer, but should continue restoring as much as it can,
Suggest an ask before: maybe the killing was deliberately but the jump-key a mistake.
then give a
> summary message/error about dead buffer(s) at the end.
>
>
>
>
next prev parent reply other threads:[~2014-02-14 7:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 6:52 bug#16749: More informative error when restoring frameset with killed buffer Glenn Morris
2014-02-14 7:01 ` Glenn Morris
2014-02-14 7:42 ` Andreas Röhler [this message]
2014-02-15 4:38 ` Juanma Barranquero
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=52FDC8CA.1060301@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=16749@debbugs.gnu.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).