Skip to content

Have man papis page contain something in it, hopefully to lead into config options #1096

Open

Description

@tuurep

Hi I have a suggestion to make after noticing myself expect certain things:

  1. I needed to check a certain papis setting
  2. Instinct: run man papis and start searching
  3. Friction: No manual entry for papis
    • What I wanted was instead man papis-config-settings but this is very hard to figure out

I understand that the manpages are auto-generated from our docs, and that generally works pretty well.

Would it make sense to make man papis lead directly to papis-config-settings manpage (or be a copy of it)?

Activity

  1. tuurep commented on Nov 11, 2025

    @tuurep
    ContributorAuthor

    I've also seen this convention of placing man pages about configs in section 5, like:

    dunst(5) which is accessed by man 5 dunst

    Some discussion about that: https://unix.stackexchange.com/a/736087

    What do you think of papis(5) as a copy of papis-config-settings?

  2. tuurep commented on Nov 11, 2025

    @tuurep
    ContributorAuthor

    Oh yeah,

    papis-default is the one for the main command, papis, in a sense.

    Suggestion (if we have control over these things):

    • man papis => man papis-default
    • man 5 papis => man papis-config-settings
  3. alexfikl commented on Nov 11, 2025

    @alexfikl
    Collaborator

    You should be able to get some good results there with a bit of work. You can add text only to the man pages in the rst docs using

    .. only:: man
    
       This text will appear **only** in the Sphinx man page output.

    so that they link better to each other. You can also add them to more appropriate sections using https://www.sphinx-doc.org/en/master/usage/configuration.html#confval-man_pages. They're currently all added to section 1 in here:

    papis/doc/source/conf.py

    Lines 280 to 289 in cecfc53

    man_pages = [
    ("configuration", "papis-config-settings", "Papis configuration",
    [papis.__author__], 1),
    ("library_structure", "papis-library-structure", "Papis library structure",
    [papis.__author__], 1),
    ("info_file", "papis-info-file", "Papis info.yaml file",
    [papis.__author__], 1),
    ("database_structure", "papis-database-structure", "Papis database structure",
    [papis.__author__], 1),
    ]

    Section 7 should also be more appropriate for the library structure description and whatnot.

  4. tuurep commented on Nov 11, 2025

    @tuurep
    ContributorAuthor

    That sounds promising, thanks

    I'll get to it at some point :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions