From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23502@debbugs.gnu.org
Subject: bug#23502: 24.5; Document auto-save-* user options in Emacs manual
Date: Wed, 11 May 2016 07:35:41 -0700 (PDT) [thread overview]
Message-ID: <d12e67f8-7f7c-4b8d-a0d9-3e1f33e57fe8@default> (raw)
In-Reply-To: <<83inykbzbt.fsf@gnu.org>>
> > Why are these options described in detail only in the Elisp manual?
> > At the very least, there should be a cross-reference from the Emacs
> > manual, node `Auto Save Control' to (elisp) `Auto-Saving'.
>
> Which ones aren't in the user manual?
Did I say any of them are not "in" the user manual?
They are not described in more detail there. Or at least please
consider adding cross-references to the information in the Elisp
manual. These are _user_ options.
> I found all of the user options
> mentioned in the "Auto-Saving" node of the ELisp manual documented in
> the user manual as well, in the 3 subsections of the "Auto Save"
> section. If I missed some, can you point them out?
What you apparently missed is that the bug report does not say
that any are missing. What it requests is to provide more info
or point users to the existing info about them in the Elisp manual.
next parent reply other threads:[~2016-05-11 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<a23b5534-87b8-45ff-b007-7bed6a341157@default>
[not found] ` <<83inykbzbt.fsf@gnu.org>
2016-05-11 14:35 ` Drew Adams [this message]
2016-05-11 14:46 ` bug#23502: 24.5; Document auto-save-* user options in Emacs manual Eli Zaretskii
[not found] <<<a23b5534-87b8-45ff-b007-7bed6a341157@default>
[not found] ` <<<83inykbzbt.fsf@gnu.org>
[not found] ` <<d12e67f8-7f7c-4b8d-a0d9-3e1f33e57fe8@default>
[not found] ` <<83d1osbqkd.fsf@gnu.org>
2016-05-11 15:36 ` Drew Adams
2016-05-11 15:54 ` Eli Zaretskii
2016-05-10 5:13 Drew Adams
2016-05-11 11:37 ` 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=d12e67f8-7f7c-4b8d-a0d9-3e1f33e57fe8@default \
--to=drew.adams@oracle.com \
--cc=23502@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.