Hi,
I am looking for advice about the best way to create a
documentation workflow for my projects. Maybe using Guix is the
best way to solve this, maybe not.
I have a set of projects with a common theme, say each project is
a circuit board that I have designed. Each project has its own git
Hello,
"Dr. Arne Babenhauserheide" writes:
> "Artyom V. Poptsov" writes:
>
>> -\usepackage{amssymb}
>> -\usepackage{marvosym}
>> I think that it is not worth the effort to use the "marvosym" package as
>> I can easily draw the single symbol I want from the package myself. But
>> maybe there's
Am Fri, Sep 01, 2023 at 07:24:19AM +0200 schrieb Dr. Arne Babenhauserheide:
> Since the switch to split texlive packages, many of my documents don’t
> compile yet (but I did not yet find out why, so I sadly can’t really
> help you) and I also use marvosym. So maybe something more general.
Did you
> My question is: How can I download the source of that package using
> the same URL that is shown in the package definition (I want to make
> sure that I'm downloading the same file that is used by the Guix
> package definition).
Not sure about wget but you can do that with
guix download 'mi
Hi,
Rodrigo Morales writes:
> #+begin_example
> mirror://gnome/sources/tracker/3.4.2/tracker-3.4.2.tar.xz: Unsupported scheme.
> 1
> #+end_example
`mirror://` is not a real URL schema; it's used by Guix as a substitute
for writing out the various mirror URLs of large projects like GNOME.
Here's
