From: Andreas Enge <andreas@enge.fr>
To: bug-guix@gnu.org
Cc: alirioeyng@gmail.com
Subject: Re: Comments on European Lisp Symposium paper
Date: Fri, 31 May 2013 20:29:01 +0200 [thread overview]
Message-ID: <201305312029.01227.andreas@enge.fr> (raw)
In-Reply-To: <877gifcwby.fsf@gnu.org>
Am Freitag, 31. Mai 2013 schrieb Ludovic Courtès:
> More importantly, I rarely type in /nix/store file names, let alone use
> tab completion in there (it’s crowded!).
Actually, I do it quite a lot, when I am using the tarballs to check manual
compilation of a new package that poses problems.
Andreas
next prev parent reply other threads:[~2013-05-31 18:29 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
2013-05-31 18:29 ` Andreas Enge [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201305312029.01227.andreas@enge.fr \
--to=andreas@enge.fr \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).