From: ken <gebser@mousecar.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: desktop-save problems
Date: Wed, 13 Jul 2016 18:24:28 -0400 [thread overview]
Message-ID: <5786BF9C.3070701@mousecar.com> (raw)
In-Reply-To: <83poqh8fxc.fsf@gnu.org>
On 07/13/2016 04:02 PM, Eli Zaretskii wrote:
>> From: ken <gebser@mousecar.com>
>> Date: Wed, 13 Jul 2016 15:49:24 -0400
>>
>>> The way I do it is turn on desktop-save-mode, then Emacs will save the
>>> desktop when I exit automatically.
>> This means that the desktop isn't saved when the system crashes, e.g.,
>> the power suddenly goes out, yes?
> If this is frequent enough, you can save manually at strategic times.
Years ago desktop-save and desktop-read both worked properly out of the
box... didn'tl even have to invoke anything. It just kept track of what
files/buffers were open and opened them again in the next session,
whether the previous session was graceful or a crash... files opened via
tramp too. How/Why did things get messed up?
>> Also, in my emacs (24.3.1) I'm always prompted for the directory to save
>> the desktop in. Is there a way to specify one directory where the
>> desktop is saved so I don't have this prompt come up?
> It doesn't prompt me, it uses the ~/.emacs.d/ directory by default;
> the directory from which the desktop was read overrides that. I'm
> never asked any such questions. Something is wrong with your setup.
This is how it works when I start emacs with "emacs -Q".
>>>> Second, is there a way for "desktop-save" to be run programmatically
>>>> whenever I open a new file/buffer or kill a buffer?
>>> In a new enough version of Emacs, the desktop is periodically saved
>>> even when no buffer is killed.
>> Which version is "new enough"?
> 24.4 and later.
>
>> Also, wouldn't it make more sense for desktop-save to work when file or
>> buffer is opened or closed?
> Since we now save periodically, we don't need to resolve this dilemma.
Just curious... how often is the desktop saved in your version?
> ....
Thanks for your help.
next prev parent reply other threads:[~2016-07-13 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 22:40 desktop-save problems ken
2016-06-15 15:08 ` Eli Zaretskii
2016-07-13 19:49 ` ken
2016-07-13 20:02 ` Eli Zaretskii
2016-07-13 22:24 ` ken [this message]
2016-07-14 2:38 ` Eli Zaretskii
2016-07-14 11:30 ` ken
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=5786BF9C.3070701@mousecar.com \
--to=gebser@mousecar.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).