all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emmanuel Beffara <manu@beffara.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: help-guix@gnu.org, guix-devel <guix-devel@gnu.org>
Subject: Re: documentation in TeX Live collections
Date: Tue, 29 Aug 2023 09:56:10 +0200	[thread overview]
Message-ID: <20230829095610.GC935@beffara.org> (raw)
In-Reply-To: <874jkjoxln.fsf@nicolasgoaziou.fr>

Hi,
 
De Nicolas Goaziou le 28/08/2023 à 20:01:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> >>> In any case, I suggest to write a proper bug report for this. Hopefully,
> >>> someone with better understanding about the implications of GUIX_TEXMF
> >>> will be able to solve this.
> >>
> >> I can do that for the texdoc behaviour.
> 
> By the way, I think I fixed `texdoc' utility. Would you care testing it
> after a fresh `guix pull'?

It seems to work fine: now texdoc does find all documentation in the various
items in GUIX_TEXMF. So there seems to be no need for a texdoc bug report
anymore, thanks! 

The only subtlety is that any call to guix shell with extra texlive packages
should also include texlive-bin (directly or not) so that the proper hooks are
called, otherwise GUIX_TEXMF is not updated. This goes beyond the point of
documentation, of course.

-- 
Emmanuel


  reply	other threads:[~2023-08-29  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 10:17 documentation in TeX Live collections Emmanuel Beffara
2023-08-27 10:13 ` Nicolas Goaziou
2023-08-28  7:49   ` Emmanuel Beffara
2023-08-28 11:01     ` Nicolas Goaziou
2023-08-28 14:52       ` Emmanuel Beffara
2023-08-28 16:54         ` Nicolas Goaziou
2023-08-28 18:01           ` Nicolas Goaziou
2023-08-29  7:56             ` Emmanuel Beffara [this message]
2023-08-28 18:05           ` Andreas Enge
2023-08-29  8:58             ` Emmanuel Beffara

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230829095610.GC935@beffara.org \
    --to=manu@beffara.org \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.