all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: guix: Set 'guix-dot-program' emacs variable.
Date: Sun, 18 Oct 2015 18:50:26 +0200	[thread overview]
Message-ID: <871tcsi0j1.fsf@gnu.org> (raw)
In-Reply-To: <87oafxsdkm.fsf@gmail.com> (Alex Kost's message of "Sat, 17 Oct 2015 18:46:17 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Ludovic Courtès (2015-10-17 16:34 +0300) wrote:

[...]

>> The docstring should mention that it can be the empty string.
>> Alternately, ‘configure’ could set DOT_USER_PROGRAM to “dot” when it’s
>> not found, which I think is ever preferable.  WDYT?
>
> IMO an empty string is preferable (explained below), so I would like to
> leave it like this (with an improved docstring as you pointed), if you
> don't mind.
>
>>> +(defcustom guix-dot-program
>>> +  (if (string= "" guix-config-dot-program)
>>> +      (executable-find "dot")
>>> +    guix-config-dot-program)
>>
>> Thus here we’d be checking whether ‘guix-config-dot-program’ is an
>> absolute file name.
>
> I think (executable-find "dot") is more reliable than just "dot" which
> may not exist.

Agreed!  I was just saying that an empty string is odd, and that setting
it to ‘dot’ would be aesthetically more pleasing.

So the only different is that the above would become:

  (defcustom guix-dot-program
    (if (absolute-file-name-p guix-config-dot-program)
         guix-config-dot-program
      (executable-find "dot")))

Does it make sense?

Ludo’.

  reply	other threads:[~2015-10-18 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 19:48 [PATCH] gnu: guix: Set 'guix-dot-program' emacs variable Alex Kost
2015-10-16  8:20 ` Ludovic Courtès
2015-10-16 18:21   ` Alex Kost
2015-10-17 13:34     ` Ludovic Courtès
2015-10-17 15:46       ` Alex Kost
2015-10-18 16:50         ` Ludovic Courtès [this message]
2015-10-19 14:49           ` Alex Kost
2015-10-19 15:41             ` Ludovic Courtès

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=871tcsi0j1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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/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.