Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wish: refman.info improvement #8247

Closed
vicuna opened this issue Aug 23, 2003 · 3 comments
Closed

Wish: refman.info improvement #8247

vicuna opened this issue Aug 23, 2003 · 3 comments

Comments

@vicuna
Copy link

vicuna commented Aug 23, 2003

Original bug ID: 1795
Reporter: administrator
Status: acknowledged
Resolution: open
Priority: normal
Severity: feature
Category: documentation

Bug description

Full_Name: Yamagata Yoriyuki
Version: 3.06
OS: Linux
Submission from: p2114-adsau14honb7-acca.tokyo.ocn.ne.jp (220.106.58.114)

The current refman.info doesn't seem to follow GNU convention of info. In
particular, I'd like to suggest the following improvement.

  1. It is better if chapters and sections are referred by their name, not
    numbers. This change enables a user to use "m" command to jump desired sections
    and chapters.

  2. Make all chapters listed in the top index, while move licence conditions or
    like to their own sections.

  3. Remove decorative ****** and ===

In general, I think it is preferable to create info from texi, not directly from
latex files by havea.

@vicuna
Copy link
Author

vicuna commented Aug 26, 2003

Comment author: administrator

Looks like an Hevea issue...

@dbuenzli
Copy link
Contributor

Not an info user myself but a test with the last published info files seems to indicate that 1+3 are still present.

@maranget do you think the "administrator" is right in pointing fingers at HeVeA ?

@github-actions
Copy link

github-actions bot commented May 6, 2020

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 6, 2020
@github-actions github-actions bot closed this as completed Jun 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants