From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60600@debbugs.gnu.org
Subject: bug#60600: 30.0.50; [PATCH] Document manual desktop restore
Date: Fri, 06 Jan 2023 14:30:39 +0100 [thread overview]
Message-ID: <878rifsscg.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83lemfvm65.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Jan 2023 15:15:46 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
[...]
> I find the organization of the text in that section not very logical
> in general. It begins by describing not-very-important optional
> features. It should instead start by describing desktop-save-mode,
> since this is the recommended use of this facility, and leave the
> manual saving/restoring for later (explaining why one would want to do
> it manually). When it describes desktop-save-mode, it should mention
> that saving happens also from time to time, not just upon exit,
> something that for some reason is described much later in the section.
> And the order of describing the various optional features seems to
> lack any logic, which at least should be to describe the more
> significant/important options (such as desktop-load-locked-desktop,
> for example) first.
Yes. I had the same feeling when reading this section. It starts
talking about desktop-restore-frames before I had grasp what is the
purpose of desktop.
I'll see if I can come up with something and report here.
>> And BTW, shouldn't desktop-revert be the user facing interface here?
>
> What do you mean? desktop-revert is described in that section (again,
> without any hint about when it could be useful).
I think I was mistaken desktop-read seems to be the correct interface as
documented in desktop-save-mode function.
--
Manuel Giraud
next prev parent reply other threads:[~2023-01-06 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 10:33 bug#60600: 30.0.50; [PATCH] Document manual desktop restore Manuel Giraud
2023-01-06 11:54 ` Eli Zaretskii
2023-01-06 12:26 ` Manuel Giraud
2023-01-06 13:15 ` Eli Zaretskii
2023-01-06 13:30 ` Manuel Giraud [this message]
2023-01-06 14:06 ` Eli Zaretskii
2023-01-06 15:15 ` Manuel Giraud
2023-01-07 8:49 ` Eli Zaretskii
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=878rifsscg.fsf@ledu-giraud.fr \
--to=manuel@ledu-giraud.fr \
--cc=60600@debbugs.gnu.org \
--cc=eliz@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.