On 2022-07-06 11:20, Tissevert wrote:
> Hi Guix,
>
> I'm finally having some time to try and put guix on the older machines at home
> and thought I'd start by generating a live CD to show the rest of the family
> what that would look like without having to make any irreversible changes yet.
>
> Me
Hi,
On mer., 06 juil. 2022 at 14:13, b...@bokr.com wrote:
> [13:23 ~/bs]$ guile --no-auto-compile -c '(display (getenv "PS1"))(newline)'
> [\A \w]\$
On my machine, all is as usual and I run Bash:
--8<---cut here---start->8---
$ echo $PS1
\n\w/\n\u@\h$
$ guil
Hi Maxim!
Em [2022-07-06 qua 09:35:28-0400], Maxim Cournoyer escreveu:
> I guess it's simply an oversight. Could you try to removing it from the
> affected packages and see if they still byte compile and run happily?
> If they do, a patch would be welcome.
I have just sent the patch to guix-pat
Hi,
On mer., 06 juil. 2022 at 16:16, Ludovic Courtès wrote:
> Nope! ‘all-modules’ *is* deterministic because it builds upon
> ‘scheme-files’, which is deterministic and documented as such.
Oh indeed! My bad, I have overlooked that ’scheme-files’ uses
’scandir*’ instead of Guile scandir; and t
I installed Bigloo version 4.3g using Guix, but there is always an error
when trying to compile a Scheme program:
$ bigloo myfile.scm
/usr/bin/ld: cannot find -lunistring
collect2: error: ld returned 1 exit status
Contents of myfile.scm:
(module mymodule
(main start))
Hi,
On jeu., 07 juil. 2022 at 15:56, Sam Lee wrote:
> $ bigloo myfile.scm
> /usr/bin/ld: cannot find -lunistring
> collect2: error: ld returned 1 exit status
Indeed, bigloo requires some packages. This works for me:
--8<---cut here---start->8---
On 2022-07-08 16:25 +0200, zimoun wrote:
> On jeu., 07 juil. 2022 at 15:56, Sam Lee wrote:
>
> > $ bigloo myfile.scm
> > /usr/bin/ld: cannot find -lunistring
> > collect2: error: ld returned 1 exit status
>
> Indeed, bigloo requires some packages. This works for me:
>
> --8<---
Am Freitag, dem 08.07.2022 um 15:42 + schrieb Sam Lee:
> On 2022-07-08 16:25 +0200, zimoun wrote:
> > On jeu., 07 juil. 2022 at 15:56, Sam Lee
> > wrote:
> >
> > > $ bigloo myfile.scm
> > > /usr/bin/ld: cannot find -lunistring
> > > collect2: error: ld returned 1 exit status
> >
Hello Guix developers!
I am messing around again with updating a package and according to my own guide
from previous adventures, I have to run the following command to generate the
`pre-inst-env` script, in the root directory of the guix sources:
guix environment guix -- ./bootstrap
On 7/8/22 23:57, Zelphir Kaltstahl wrote:
Hello Guix developers!
I am messing around again with updating a package and according to my own
guide from previous adventures, I have to run the following command to
generate the `pre-inst-env` script, in the root directory of the guix sources:
~~
That's because you're not using guix shell properly.
guix shell guix
Creates a shell where guix *itself* is available
guix shell -D guix
Creates a shell where guix *dependencies* are available. That's what you need
to use.
The manual provides more information on how to build Guix from the sou
Hi,
Isn't `guix environment guix` equivalent to `guix shell -D guix`?
I think you are missing a -D there so it's adding a shell with guix and not
with its development dependencies.
Hope that helps,
Ekaitz
[ElenQ Technology](https://elenq.tech)
Ethical Innovation
--- Original Message ---
Zelphir Kaltstahl writes:
> I am messing around again with updating a package and according to my
> own guide from previous adventures, I have to run the following
> command to generate the `pre-inst-env` script, in the root directory
> of the guix sources:
>
>
> guix environment guix -- ./
Hello : )
Thank you both! I did not know that. I previously mistakenly thought
"environment = shell", but did not know, that I would have to add `-D` or
`--development` to actually make an equivalent call. So `guix shell`, I guess,
is more nuanced then, than `guix environment`.
Anyway, that
Hi,
As some extra info:
`guix shell` by default does what `guix environment --ad-hoc` did.
And `guix shell --development` is what `guix environment` was.
They are equivalent, but the flags might be confusing at the beginning!
Happy hacking!
Ekaitz
[ElenQ Technology](https://elenq.tech)
Ethical I
Hi,
If you too have been wondering why hitting M-q on package descriptions
doesn't produce the intended effect anymore (the first line of text
protrudes beyond the fill-column value), this may be of interest.
The problem was introduced in commit 9bf367e1848, which aimed to improve
the handling of
Hi Guixers,
I'm working on this package and I could use some guidance:
```
(define-public emacs-importmagic
(let ((commit "701dfcca5f3ab42be0f26a8d381d7116c79be850")
(revision "0"))
(package
(name "emacs-importmagic")
(version (git-version "1.0" revision commit))
(
Hi Maxim,
> The problem was introduced in commit 9bf367e1848, which aimed to improve
> the handling of Elisp docstrings. To revert to the old version (the one
> that shipped with Emacs 27), you can put this in your .emacs:
>
> (require 'lisp-mode)
> (defun lisp-fill-paragraph (&optional justify
18 matches
Mail list logo
