From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] texdoc doesn't work / texlive documentation missing
Date: Tue, 20 Apr 2021 01:26:47 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30340@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
New issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/30340
Description:
This used to work (with `texlive-bin`):
```
$ texdoc enumitem
[... opens /opt/texlive/2020/texmf-dist/doc/latex/enumitem/enumitem.pdf ...]
```
With the new packaged `texlive`:
```
$ texdoc enumitem
texdoc error: No texlive.tlpdb nor shipped tlpdb data found.
$ xlocate enumitem.pdf
$
```
That is, `texdoc` seems to be broken, and the corresponding documentation can't be found anywhere.
next reply other threads:[~2021-04-19 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 23:26 tornaria [this message]
2021-04-20 3:50 ` ericonr
2021-04-20 9:15 ` fosslinux
2022-01-17 11:03 ` scheckley
2022-01-17 11:04 ` scheckley
2022-05-18 2:09 ` github-actions
2022-06-02 2:13 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30340@inbox.vuxu.org \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).