On Sat, 11 May 2024 10:14:15 +0200 pelzflorian (Florian Pelz) wrote ---
> Instead, there already is advice for .config/guix/current documented in
> the Guix manual’s Getting Started section. The advice should be a
> cross-reference that users should follow the steps from Getting Started,
>
Hello Matt, Vagrant and all. As I understand, we should not advice all
users to add these exports to .bashrc, because users with
guix-install.sh’s sys_create_init_profile or Debian’s
/etc/profile.d/guix.sh do not need it.
Instead, there already is advice for .config/guix/current documented in
On Tue, 07 May 2024 22:41:33 +0200 Vagrant Cascadian wrote ---
On 2024-05-07, m...@excalamus.com wrote:
#+begin_quote
6.7 L37 true for Guix System as well?
The result of running ‘guix pull’ is a “profile” available
under
‘~/.config/guix/current’ containing the latest Guix.
On 2024-05-07, m...@excalamus.com wrote:
> #+begin_quote
> 6.7 L37 true for Guix System as well?
> The result of running ‘guix pull’ is a “profile” available under
> ‘~/.config/guix/current’ containing the latest Guix. Thus, make sure to
> add it to the beginning of your search path so that you
We're working through a list of feedback one item at a time:
https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00117.html
We have completed the first five items. The sixth item was fixed already in
Pushed as b8ccbc942e0ec7baf695d383e575991289c6e033.
Thank you for trudging on through the list.
Regards,
Florian
We're working through a list of feedback one item at a time:
https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00117.html
We have completed the first four items.
The next item reported is:
#+begin_quote
3.8 Installing Guix in a Virtual Machine
L25 in an vm should be in a vm
#+end_quote
On Fri, 19 Apr 2024 22:56:13 +0200 pelzflorian (Florian Pelz) wrote ---
> Hello Matt, pushed as 86fb0e039bf30cf85e2066401f9a384427c47ea8.
>
> I was bold enough to retain the xref change in (Setting Up the Daemon)
> prompted by Ludo, because starting a sentence with @xref is
Hello Matt, pushed as 86fb0e039bf30cf85e2066401f9a384427c47ea8.
I was bold enough to retain the xref change in (Setting Up the Daemon)
prompted by Ludo, because starting a sentence with @xref is recommended
in the Texinfo manual and its examples, while @pxref at the start of a
phrase is not
On Tue, 16 Apr 2024 08:43:23 +0200 pelzflorian (Florian Pelz) wrote ---
> Hi Matt. When triple checking, I read in “info "(texinfo)@pxref"”:
>
>In past versions of Texinfo, it was not allowed to write punctuation
> after a '@pxref', so it could be used _only_ before a right
Hi Matt,
Matt writes:
> On Mon, 15 Apr 2024 14:58:50 +0200 pelzflorian (Florian Pelz) wrote
> ---
>
> > Do you agree that I should commit your docs correction with @pxref?
> > I believe it is an improvement over current “see @ref”, even though it
> > looks different in the info
Hi Matt. When triple checking, I read in “info "(texinfo)@pxref"”:
In past versions of Texinfo, it was not allowed to write punctuation
after a '@pxref', so it could be used _only_ before a right parenthesis.
This is no longer the case. The effect of '@pxref{NODE-NAME}' is
similar to that of
On Mon, 15 Apr 2024 14:58:50 +0200 pelzflorian (Florian Pelz) wrote ---
> Do you agree that I should commit your docs correction with @pxref?
> I believe it is an improvement over current “see @ref”, even though it
> looks different in the info reader.
Yes, I agree and thank you for
Matt writes:
> The problem is that the Emacs Info reader incorrectly renders
> cross-references by default. I was reading the Texinfo documentation
> in Emacs.
I believe the Emacs errors are historical; looking at Emacs 29.3 as
packaged in Guix, Emacs-Info displays xref properly as See.
On Sat, 13 Apr 2024 13:26:39 +0200 pelzflorian (Florian Pelz) wrote ---
> @xref produces a capital See instead of see. This should be @pxref.
> See the Texinfo manual “info texinfo” or the Web manual Ludo points to.
>
> In info, this will use the word *note instead of *see, but
Matt writes:
> The attached change updates "Libera Chat" to the "Libera.Chat" stylization.
Pushed as df7b569b464c05036871f23d37ba319be78e5f64.
Thanks!
Regards,
Florian
Hello,
I just want to mention that I am still in CC and my mail server is going
offline. Need to optimize my budget and don't have any time for GNU
anymore because of university.
--
Christian Miller
Am 10/04/2024 um 16:05 schrieb Matt:
We're working through a list of feedback one item at
Matt writes:
> #+begin_quote
> 3.7 After System Installation
> L27 Libera_Chat, why the underscore. It is colored as well for me so
> I guess this is a special char. Should be anways just Libera Chat
> #+end_quote
>
> "Libera_Chat" is not, or no longer, in the docs (d3fe763fe3).
> However, there
Hello Matt. Thank you for fixing the oversight. However:
Matt writes:
> From: Matthew Trzcinski
> Date: Sat, 13 Apr 2024 10:12:05 +0200
> Subject: [PATCH] doc: Fix cross-references
>
> * doc/guix.texi (Setting Up the Daemon): use @xref to start sentence.
> (Build Systems): capitalize "python"
On Fri, 12 Apr 2024 22:16:39 +0200 Ludovic Courtès wrote ---
> > See @ref{Substitutes} for how to allow the daemon to download pre-built
> > binaries.
>
> Nitpick: this works but I believe the recommended approach is
> “@xref{Substitutes} for how…”.
>
>
>
Hi,
Matt skribis:
> See @ref{Substitutes} for how to allow the daemon to download pre-built
> binaries.
Nitpick: this works but I believe the recommended approach is
“@xref{Substitutes} for how…”.
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Cross-Reference-Commands.html
We're working through a list of feedback one item at a time:
https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00117.html
We have completed the first three items.
The next item reported is:
#+begin_quote
3.7 After System Installation
L27 Libera_Chat, why the underscore. It is colored as
Pushed as cd557e2d1c83839dd587016279900d31f053efc8.
Matt writes:
> The next item reported is:
>
> #+begin_quote
> 2.4 Setting up the deamon
>
> Seems like an issue with info. Have seen this in the Emacs manual as well.
> There is also sometimes see see (doc)
>
> L15 See also see Substitutes.
We're working through a list of feedback one item at a time:
https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00117.html
We have completed the first two items.
The next item reported is:
#+begin_quote
2.4 Setting up the deamon
Seems like an issue with info. Have seen this in the Emacs
On 2024-03-06, pelzflorian (Florian Pelz) wrote:
> I don’t feel qualified to judge, but is this the preference? Arch wiki
> advises against the Arch AUR package: “Therefore, after updating Guix
> once, the AUR advantage really turns into a disadvantage, as there will
> be many unnecessary files
On Wed, 06 Mar 2024 18:15:05 +0100 pelzflorian (Florian Pelz) wrote ---
> Thank you Matt for the suggested diff.
Thank you for taking the time to review it!
> > - Places directions for 'guix-install.sh' after directions to use
> > distribution-specific package managers, giving
Thank you Matt for the suggested diff.
Yes, I agree some simplification as you suggested would be beneficial,
so that the description of Binary Installation looks as simple as it
really is. (In particular, I have witnessed people, to whom I had
suggested Guix, fail at trying Guix because they
We're working through a list of feedback one item at a time:
https://lists.gnu.org/archive/html/guix-devel/2024-01/msg00117.html
We have completed an item and are ready to work on the next one:
#+begin_quote
,** Binary Installation L88 and L95
~root is weird. Should be root or simply ~ for the
On Fri, 23 Feb 2024 03:46:29 +0100 Maxim Cournoyer wrote ---
> Great, sounds good. I've checked your v2 update, but opted to keep
> things as they are (following my own edition of your initial work, which
> was committed).
No problem, I think what you did looks good.
> Thank you
Hi Matt,
Matt writes:
> On Wed, 21 Feb 2024 18:20:19 +0100 Maxim Cournoyer wrote ---
>
> > Thanks for the follow-up.
>
> Thank you! Seems like we were looking at it at about the same time :)
>
> > Like Josselin, I prefer to keep the mention that the tarball archive
> > includes the
On Wed, 21 Feb 2024 18:20:19 +0100 Maxim Cournoyer wrote ---
> Thanks for the follow-up.
Thank you! Seems like we were looking at it at about the same time :)
> Like Josselin, I prefer to keep the mention that the tarball archive
> includes the transitive dependencies of Guix
On Sun, 18 Feb 2024 14:55:46 +0100 Josselin Poiret wrote ---
> Matt m...@excalamus.com> writes:
>
> > Specific mention of installing Guix's dependencies was removed. Guix
> > being installed implies that its dependencies are also installed.
>
> I don't agree here: it's often
Hi Matt,
Thanks for the follow-up.
Matt writes:
[...]
> #+begin_src diff
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 4af830aed7..16349d4ec1 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -732,14 +732,16 @@ ready to use it.
>
> @cindex installing Guix from binaries
>
Hi Matt,
Matt writes:
> The explanation of "a self-contained tarball providing binaries for Guix and
> for all its dependencies" was reduced to the simpler "archived binaries."
> Generally, "tarball" is imprecise, hence the need to explain what it contains
> in this context. Further, it's
Friendly bump. Awaiting feedback or guidance.
Friendly bump.
Attached is a suggested diff.
A previous suggestion was made to change "system" to the proper noun "System",
as in the "Guix System", within the Binary Installation section. The change
would occur in a warning that moving unpacked binary tarballs as directed on
existing Guix
On Thu, 18 Jan 2024 20:44:53 +0100 Maxim Cournoyer wrote ---
> That would be a good way to help, yes! It'll be easier to review if
> each distinct problem is fixed in its own commit (patch).
Now that I've looked more closely at it, I completely agree.
I suggest we take them
Hi Matt!
Matt writes:
> I care about this. How can I help?
>
> - Convert the notes into patches?
> - Proofread any patches that derive from Christian's efforts?
That would be a good way to help, yes! It'll be easier to review if
each distinct problem is fixed in its own commit (patch).
--
> I care about this. How can I help?
I don't know. I would also create patches but don't know if it should
be a huge patch or multiple ones, or maybe even it's own branch.
> What's TTY mode? M-x tty reveals nothing for me.
Mode is probably the wrong word. It basically is just running
I care about this. How can I help?
- Convert the notes into patches?
- Proofread any patches that derive from Christian's efforts?
On Sun, 14 Jan 2024 16:01:58 +0100 Christian Miller wrote ---
> I read through the GNU Guix manual on revision
>
Hello,
I read through the GNU Guix manual on revision
ee7c9d254117fa470686210ad2ef5e7f1ba4fefc with Emacs in TTY mode.
As a beginner, the manual was helpful and I learned lot's of stuff.
Though it felt heartless. No consistency and sometimes the structure
is confusing (especially the
41 matches
Mail list logo
