In demonstrating one of the gaps of man pages in modern times and likely having hindered the adoption of the Linux kernel’s new mount API, it took more than six years for those system calls to be properly documented within man pages. The Linux “new” mount API was introduced back in mid-2019 with Linux 5.2 and since supported by key file-systems after several years but not until weeks ago was this file descriptor based mount API scoped out within man pages.

The “new” mount API for Linux is a set of system calls like fsopen and fsconfig for offering more flexibility than the Linux kernel’s long-used mount system call that is a one-shot approach compared to this modern multi-step design for better flexibility. In the kernels since Linux 5.2, various file-systems have transitioned to supporting the modern mount API. It was only earlier this year that F2FS added support for it as one of the last major file-systems without it.

  • linuxPIPEpower@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    17 hours ago

    Someone can correct this but iirc some implementations of markdown have image options like this:

    ![alt text](/path/to/IMG.png|200px "description text")

    Others put the size in { } after the main image item.

    Rich text is contrary to the structural focus of markdown. Why should it be added?

    • MonkderVierte@lemmy.zip
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      5 hours ago

      Guess we have a semantics problem here. I understand under “rich text” text with formatting, not the long since dead file format. Markup is the language used to add richness to the plain text, no?

      • linuxPIPEpower@discuss.tchncs.de
        link
        fedilink
        arrow-up
        2
        ·
        5 hours ago

        Sorry I was trying to follow your meaning, because the example of absent rich text you gave was underlines. There is already basic text formatting support such as strong, emphasis, headings and links.

        You could style any, all or none of those to have underlining. Whatever chosen rendering, they all have meaning independent from the applied style. What you are asking for is to have something that is purely a display style without any structural value. This is not coming to markdown any time soon. Hardly anyone uses underline as its own thing in html anymore, for good reasons.

        Maybe this article will help to further explain.

        Native SVG handling would be completely out of scope. The point of markdown is that it is supposed to be understandable in its plain text format. SVG is incompatible with that. The closest thing would be like mermaid charts but I think it’s quite a stretch even then.

        I think you should just use HTML, it has a much larger array of tools that would suit your needs. Markdown is purposely constrained because it enables much more portability.