From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: paaguti@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH]: package-user-dir is a defcustom
Date: Sat, 15 Jun 2024 20:30:00 +0300 [thread overview]
Message-ID: <864j9ut8pz.fsf@gnu.org> (raw)
In-Reply-To: <87h6duku2h.fsf@posteo.net> (message from Philip Kaludercic on Sat, 15 Jun 2024 17:13:42 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: emacs-devel <emacs-devel@gnu.org>
> Date: Sat, 15 Jun 2024 17:13:42 +0000
>
> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
> > Hi,
> > I would have saved some time, because I understood changing=>setq. I think
> > customising
> > is a bit more precise.
> >
> > Best, /PA
> >
> > diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi
> > index fd445805068..a98af7abdc1 100644
> > --- a/doc/emacs/package.texi
> > +++ b/doc/emacs/package.texi
> > @@ -566,7 +566,7 @@ Package Files
> > @vindex package-user-dir
> > Once installed, the contents of a package are placed in a
> > subdirectory of @file{~/.emacs.d/elpa/} (you can change the name of
> > -that directory by changing the variable @code{package-user-dir}). The
> > +that directory by customising the variable @code{package-user-dir}). The
> > package subdirectory is named @file{@var{name}-@var{version}}, where
> > @var{name} is the package name and @var{version} is its version
> > string.
>
> I think the clearer change would have been to replace the noun
> "variable" with "user option", instead of relying on the implicit
> information in the verb.
We use "customize the variable" all over the place in the user manual,
so it is quite common.
next prev parent reply other threads:[~2024-06-15 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 16:27 [PATCH]: package-user-dir is a defcustom Pedro Andres Aranda Gutierrez
2024-06-15 16:48 ` Eli Zaretskii
2024-06-15 17:13 ` Philip Kaludercic
2024-06-15 17:30 ` Eli Zaretskii [this message]
2024-06-15 20:21 ` [External] : " Drew Adams
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=864j9ut8pz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=paaguti@gmail.com \
--cc=philipk@posteo.net \
/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).