RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-27 03:57:44 +00:00
Code Issues Activity Actions

Help+Base: Add help://man URLs for links between man pages

Browse source 
The URLs of the form `help://man/<section>/<page>` link to another help
page inside the help application. All previous relative page links are
replaced by this new form. This doesn't change any behavior but it looks
much nicer :^)

Note that man doesn't handle these new links, but the previous relative
links didn't work either.
This commit is contained in:
kleines Filmröllchen 2022-01-07 14:15:44 +01:00 • committed by Linus Groh
parent becf74097e
commit 98c0c5e9e6
73 changed files with 177 additions and 165 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Base/usr/share/man/man4/audio.md
View file

@ -11,7 +11,7 @@ The `/dev/audio` character device file exposes the audio output device of the sy
| Format | 16-bit signed | 16-bit signed |
| Data | Left sample | Right sample |
The sample rate of the samples is determined by the audio device's current sample rate, which may be accessed by an [ioctl](../man2/ioctl.md).
The sample rate of the samples is determined by the audio device's current sample rate, which may be accessed by an [ioctl](help://man/2/ioctl).
Note that for convenience, the audio device may not block the call to `write` and return before all the samples were actually transferred to the hardware and/or played by the hardware. For this reason, users need to be aware that the audio device driver's internal buffer may become full and calls to `write` may return `ENOSPC`.

4
Base/usr/share/man/man4/full.md
View file

@ -30,6 +30,6 @@ $ head -c 8 /dev/full | hexdump
## See also
* [`null`(4)](../man4/null.md)
* [`zero`(4)](../man4/zero.md)
* [`null`(4)](help://man/4/null)
* [`zero`(4)](help://man/4/zero)

8
Base/usr/share/man/man4/mem.md
View file

@ -7,8 +7,8 @@ mem - physical system memory
`/dev/mem` is a character device file that is used by other programs to examine
the physical memory.
Trying to [`mmap`(2)](../man2/mmap.md) a physical range results either with success,
or with an error. When invoking [`mmap`(2)](../man2/mmap.md) on bad memory range,
Trying to [`mmap`(2)](help://man/2/mmap) a physical range results either with success,
or with an error. When invoking [`mmap`(2)](help://man/2/mmap) on bad memory range,
the kernel will write a message about it to the kernel log.
By default, the kernel limits the areas which can be accessed. The allowed areas
@ -21,11 +21,11 @@ mknod /dev/mem c 1 1
chmod 660 /dev/mem
```
## Returned error values after [`mmap`(2)](../man2/mmap.md)
## Returned error values after [`mmap`(2)](help://man/2/mmap)
* `EINVAL`: An access violation was detected.
* `ENOMEM`: The requested range would wrap around, creating an access violation.
## See also
* [`mmap`(2)](../man2/mmap.md)
* [`mmap`(2)](help://man/2/mmap)

4
Base/usr/share/man/man4/null.md
View file

@ -14,6 +14,6 @@ Reading from `/dev/null` returns end of file and exits with status 0.
## See also
* [`full`(4)](../man4/full.md)
* [`zero`(4)](../man4/zero.md)
* [`full`(4)](help://man/4/full)
* [`zero`(4)](help://man/4/zero)

4
Base/usr/share/man/man4/zero.md
View file

@ -21,6 +21,6 @@ $ head -c 8 /dev/zero | hexdump
## See also
* [`null`(4)](../man4/null.md)
* [`full`(4)](../man4/full.md)
* [`null`(4)](help://man/4/null)
* [`full`(4)](help://man/4/full)