all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: alirioeyng@gmail.com
Cc: bug-guix@gnu.org
Subject: Re: Comments on European Lisp Symposium paper
Date: Fri, 31 May 2013 11:50:09 +0200	[thread overview]
Message-ID: <877gifcwby.fsf@gnu.org> (raw)
In-Reply-To: <8761xzj09t.fsf@trisquel.local.lan> (alirioeyng@gmail.com's message of "Fri, 31 May 2013 03:28:30 +0000")

alirioeyng@gmail.com skribis:

> seems a typo
>
> 2305c2305
> < directly usable by packagers will little or no experience with Scheme. %
> ---
>> directly usable by packagers with little or no experience with Scheme. %

Indeed.

> I think '#!/usr/bin/env sh' would work with 'our unusual file system layout'

In the user environment yes, but not necessarily in the build
environment.

What NixOS does is that the system has /usr/bin/env and /bin/sh, but the
build environment only has /bin/sh.

> 2530c2530
> < required to allow scripts to work with our unusual file system layout;
> ---
>> required to allow scripts to work without that impurity;

Good idea.

I’ll commit these changes.

> why /nix/store/v9zic07iar8w90zcy398r745w78a7lqs-emacs-24.2 instead of /nix/store/emacs-24.2-v9zic07iar8w90zcy398r745w78a7lqs?
> you hate tab-completion?

That’s inherited from Nix.  My first reaction at the time was the same
as yours, but in practice, I found it convenient that only 3 or 4
characters are needed to disambiguate.

More importantly, I rarely type in /nix/store file names, let alone use
tab completion in there (it’s crowded!).

Thanks for your feedback!

Ludo’.

  reply	other threads:[~2013-05-31  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31  3:28 Comments on European Lisp Symposium paper alirioeyng
2013-05-31  9:50 ` Ludovic Courtès [this message]
2013-05-31 18:29   ` Andreas Enge
2013-05-31 21:43     ` 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=877gifcwby.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alirioeyng@gmail.com \
    --cc=bug-guix@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.