From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45681) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ews2U-00026Z-DH for guix-patches@gnu.org; Fri, 16 Mar 2018 12:17:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ews2Q-0002Va-D5 for guix-patches@gnu.org; Fri, 16 Mar 2018 12:17:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:57531) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ews2Q-0002VQ-7v for guix-patches@gnu.org; Fri, 16 Mar 2018 12:17:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ews2Q-0001lR-3B for guix-patches@gnu.org; Fri, 16 Mar 2018 12:17:02 -0400 Subject: [bug#30797] [PATCH 1/2] gnu: Add emacs-exec-path-from-shell Resent-Message-ID: From: Oleg Pykhalov References: <87lgetu3gy.fsf@gmail.com> <87k1ucrtuu.fsf@gmail.com> Date: Fri, 16 Mar 2018 19:16:06 +0300 In-Reply-To: (Konrad Hinsen's message of "Fri, 16 Mar 2018 15:42:03 +0100") Message-ID: <874llgro6x.fsf@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Konrad Hinsen Cc: 30797@debbugs.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Konrad Hinsen writes: [=E2=80=A6] >> And in the description, we could use =E2=80=98@var=E2=80=99 instead of = =E2=80=98@code=E2=80=99: >> >> -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=20Emacs source code in =E2=80=98doc/lispref/files.texi=E2=80=99: 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. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEc+OyAXw1EaDPCmAPckbhHGm3lWkFAlqr7cYACgkQckbhHGm3 lWlbAg/+KbYBZns0QM9mHrWYuXgIF8OZNKO0MUQiYjdBQmaWUdyY1pJBQp94Rgs4 UoAh1Q1tMp5aERW9sgYwzagc/awQdFHj1kzxUncdaKvhR+wEstebZoVHh2ByCRHh alzV8QMa1uH+Pb+a9G+jYCodT/FkzpKizkDr5USx3eJ/AtR8B3KsXF1jKjLmmlac 0Mf8eUcL3+Z4ajUqyfLzkt+Kok6oWUje8LlGjOrRwCNQQGt0hW4mPcNMqYjtkHhZ z7YVN7+U8k7kOteXffKBAjQ/CJn49FnL3mwW/SG4rfA7PUF2mAb2HFGrPDWLtyUX LT2yLmD102Vz0YoD+ChlYRQ9CtCaOTi005dF0RNPMXuyLTG2SfUFj2g+VPrJ3eS1 DB1ARC3PdRzC4qSKDQX0L7UMvglhg4XnvEAu1cpwSiDon/7nkLg0JUovvZuyrMDX mdwqKHAgpm3n6vBNTysnA+/ElGVzBxNr1y0N92CSdo12PX77O8Oyjd8XiHsTzDqu rM+7/UxdCchxwz0g/DdIuajzbTFGJDmuB9fIkz6Gy4X10ygL+feiNHPLCgv7seW7 So0JmzH3lrzxIiwAkd35knvDxqlByZkQYP5/dYsaRW7sPPt9zkM8a/+Md6u6j64v jQDXrCCK4xrNvZVnefGbIVejv13w+AVew9i4DVFFVBRP0eysdbI= =CTds -----END PGP SIGNATURE----- --=-=-=--