Quoting Ludovic Courtès (2016-08-31 16:21:49)
> (That said, more and more software is distributed via Git rather than as
> tarballs, and most repos are unsigned; even if they were, there are
> basically no tools to meaningfully authenticate a Git checkout…)
In that case, not all hope is lost---I'v
I understand why this happens:
% khal --help
Usage: .khal-real [OPTIONS] COMMAND [ARGS]...
[...]
but I think it sorta sucks for user experience. Just thought I'd point this
out, and I was wondering if there were any ideas to address this.
Specifically, argv[0] references the name of the "
Quoting Ludovic Courtès (2016-09-01 04:59:02)
> ‘exec -a’ works as advertised:
>
> --8<---cut here---start->8---
> $ sh -c 'exec -a FOO guile -c "(pk (command-line))"'
>
> ;;; (("FOO"))
> --8<---cut here---end--->8---
So, he
I suspect the scope of this UX "bug" is larger than python. I think this
probably affects every executable written in an interpreted
language and using a shebang. Here's another example with a bash
script:
$ cat > t.sh
#!/bin/bash
sed 's/\x0/\\0/g' # replaces null bytes with a visible '\
I use Guix on an old thinkpad, and I've noticed that every time I run
`guix pull` followed by `guix package -u`, I need to compile many of the
packages. That whole process could take about an hour on my laptop
(compiling the package definitions, and many of the package upgrades in
my profile). I
