From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] pinfo bash: Tag table is corrupt
Date: Sun, 31 Oct 2021 17:01:43 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33849@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
New issue by tornaria on void-packages repository
https://github.com/void-linux/void-packages/issues/33849
Description:
Steps to reproduce:
- install `pinfo`
- run `pinfo bash`
- move down to some menu entry and hit `<enter>`
- The status bar reads "Tag table is corrupt, trying to fix... (press a key to continue)"
I've no idea of the format for info files, but looking at the tag table at the end of `/usr/share/info/bash.info` it seems the byte address for a given node is incorrect. Example:
```
Node: What is Bash?^?3029
```
which I take to mean this node starts at byte address 3029, but in fact it starts at byte address 3020 or 3021 (definitely not 3029).
All the tag table seems to be wrong in this sense, the offset from the "right" byte address seems to be more for later entries.
I compared the tag table for other info files (e.g. `gzip.info`) and they seem to match perfectly in contrast to `bash.info` so I guess my understanding is not incorrect and `bash.info` seems wrong for some reason.
next reply other threads:[~2021-10-31 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 16:01 tornaria [this message]
2021-10-31 22:33 ` tornaria
2021-11-08 16:35 ` tornaria
2022-06-10 2:14 ` github-actions
2022-06-24 2:15 ` [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-33849@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).