From: Juri Linkov <juri@jurta.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, 17351@debbugs.gnu.org
Subject: bug#17351: Trunk emacs splats .emacs.desktop at startup
Date: Fri, 04 Jul 2014 02:35:00 +0300 [thread overview]
Message-ID: <871tu22ezf.fsf@mail.jurta.org> (raw)
In-Reply-To: <dt61jfqi2d.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 02 Jul 2014 22:42:18 -0400")
>> But another case is when the errors are in the init file, and the buffer
>> *Warnings* is displayed. The remaining problem is that the buffer
>> *Warnings* becomes hidden behind the restored window configuration,
>> so the user has no indication about the errors in the init file.
>
> That seems unrelated to this report?
Fortunately, it doesn't cause the desktop file corruption,
so I created a separate bug#17927.
It seems for this bug#17351 to be closed, what remains to do is
to generate a backup copy of the desktop file. I see two ways:
1. manually write a backup file once after reading the desktop
and locking it. This solution fits into the current design
of desktop.el.
2. Use normal mechanisms of making a backup and locking
by using save-buffer instead of write-region, but this
will cause more problems (including in the recentf list, etc.)
prev parent reply other threads:[~2014-07-03 23:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 18:04 bug#17351: Trunk emacs splats .emacs.desktop at startup Alan Mackenzie
2014-04-27 8:22 ` Juri Linkov
2014-04-27 9:15 ` Alan Mackenzie
2014-04-27 9:52 ` Juri Linkov
2014-04-27 14:31 ` Stefan Monnier
2014-04-27 22:13 ` Stefan Monnier
2014-06-22 7:05 ` Glenn Morris
2014-06-22 23:01 ` Juri Linkov
2014-06-23 0:05 ` Glenn Morris
2014-06-23 22:57 ` Juri Linkov
2014-06-24 18:30 ` Glenn Morris
2014-06-24 23:23 ` Juri Linkov
2014-06-26 19:31 ` Glenn Morris
2014-06-26 23:44 ` Juri Linkov
2014-08-11 1:18 ` Glenn Morris
2014-08-12 6:52 ` Juri Linkov
2014-07-02 23:52 ` Juri Linkov
2014-07-03 2:42 ` Glenn Morris
2014-07-03 23:35 ` Juri Linkov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tu22ezf.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=17351@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.