all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 30797-done@debbugs.gnu.org, 30797@debbugs.gnu.org
Subject: [bug#30797] [PATCH 1/2] gnu: Add emacs-exec-path-from-shell
Date: Fri, 16 Mar 2018 15:42:03 +0100	[thread overview]
Message-ID: <m1in9wxetg.fsf@fastmail.net> (raw)
In-Reply-To: <87k1ucrtuu.fsf@gmail.com>

Hi Oleg,

>> +     "This library allows the user to set Emacs' @code{exec-path} and
>
> I still think this apostrophe is unnecessary.  I removed it if you don't
> mind.  ;-)

Well, I don't mind, but according to rules of English grammar, it's
either "Emacs'" or "Emacs's'" but not simply "Emacs". See for example:

   http://www.grammar.cl/rules/genitive-case.htm

   4. Singular noun ending in –s:

   It depends…
   a. Most names: add 's (apostrophe S)

   * They had a really good time at James’s barbecue last Friday. 
   * We spent the day admiring Frances’s new car. 

   b. Classical or religious names: add ' (only the apostrophe)

   * Jesus’ disciples carried out the teachings of Jesus. 
   * Sophocles’ plays are still performed today. 


> 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.

> Pushed with changes above as 22d628148ce857b620f5b8e48dc7cabe004313c5
>
> I'll close the bug report.

Great, thanks!

Konrad.

  reply	other threads:[~2018-03-16 14:43 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       ` Konrad Hinsen [this message]
2018-03-16 15:05         ` [bug#30797] " Clément Lassieur
2018-03-16 15:28           ` Konrad Hinsen
2018-03-16 16:16             ` Oleg Pykhalov
2018-03-16 16:16         ` Oleg Pykhalov
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=m1in9wxetg.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=30797-done@debbugs.gnu.org \
    --cc=30797@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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.