From: Oleg Pykhalov <go.wigust@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 30797@debbugs.gnu.org
Subject: [bug#30797] [PATCH 1/2] gnu: Add emacs-exec-path-from-shell
Date: Fri, 16 Mar 2018 19:16:06 +0300 [thread overview]
Message-ID: <874llgro6x.fsf@gmail.com> (raw)
In-Reply-To: <m1in9wxetg.fsf@fastmail.net> (Konrad Hinsen's message of "Fri, 16 Mar 2018 15:42:03 +0100")
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
[…]
>> And in the description, we could use ‘@var’ instead of ‘@code’:
>>
>> -This library allows the user to set Emacs @code{exec-path} and
>> +This library allows the user to set Emacs @var{exec-path} and
>
> I actually hesitated in this case, after consulting the Texinfo manual:
>
> 7.1.7 @var{metasyntactic-variable}
>
> Use the @var command to indicate metasyntactic variables. A
> metasyntactic variable is something that stands for another piece of
> text. For example, you should use a metasyntactic variable in the
> documentation of a function to describe the arguments that are passed
> to that function.
>
> Do not use @var for the names of normal variables in computer
> programs. These are specific names, so @code is correct for them
> (@code). For example, the Emacs Lisp variable texinfo-tex-command is
> not a metasyntactic variable; it is properly formatted using @code.
>
> I must confess I don't understand the difference between a metasyntactic
> variable and a normal variable. The examples don't help: for me, a
> function argument is just a pre-initialized "normal" variable.
From Emacs source code in ‘doc/lispref/files.texi’:
Typical values for @var{path} are @code{exec-path}
(@pxref{Subprocess Creation}) when looking for executable programs,
or @code{load-path} (@pxref{Library Search}) when looking for Lisp
files. If @var{filename} is absolute, @var{path} has no effect, but
the suffixes in @var{suffixes} are still tried.
A proper piece of sentence according to a quote above I could think of:
This library allows the user to set Emacs @code{exec-path} and
@var{path} from the shell @env{PATH}
WDYT?
Thanks,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-03-16 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 15:47 [bug#30797] [PATCH 1/2] gnu: Add emacs-exec-path-from-shell Konrad Hinsen
2018-03-15 8:50 ` Oleg Pykhalov
2018-03-16 12:11 ` Konrad Hinsen
2018-03-16 14:13 ` bug#30797: " Oleg Pykhalov
2018-03-16 14:42 ` [bug#30797] " Konrad Hinsen
2018-03-16 15:05 ` Clément Lassieur
2018-03-16 15:28 ` Konrad Hinsen
2018-03-16 16:16 ` Oleg Pykhalov
2018-03-16 16:16 ` Oleg Pykhalov [this message]
2018-03-17 11:46 ` Andreas Enge
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=874llgro6x.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=30797@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.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 external index
https://git.savannah.gnu.org/cgit/guix.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.