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

Everywhere: Remove unnecessary whitespace at the end of some lines.

Browse source
This commit is contained in:
Emanuele Torre 2021-03-08 00:19:37 +01:00 • committed by Andreas Kling
parent 6749ba3477
commit 1f81bc6879
32 changed files with 76 additions and 76 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Base/usr/share/man/man3/posix_spawn_file_actions_init.md
View file

@ -29,7 +29,7 @@ A `posix_spawn_file_actions_t` object is allocated on the stack but starts in an
`posix_spawn_file_actions_destroy()` frees up resources used by a valid `posix_spawn_file_actions_t` object and puts it into an undefined state. It has to be called after a `posix_spawn_file_actions_t` object is no longer needed.
It is valid to alternatingly call `posix_spawn_file_actions_init()` and `posix_spawn_file_actions_destroy()` on the same object,
It is valid to alternatingly call `posix_spawn_file_actions_init()` and `posix_spawn_file_actions_destroy()` on the same object,
`posix_spawn_file_actions_addchdir()` and `posix_spawn_file_actions_addfchdir()` make `posix_spawn()` change the current working directory before spawning a process, like `chdir` and `fchdir` would.. The current working directory affects the spawned child process, but also relative paths passed to later `posix_spawn_file_actions_add(f)chdir()` and `posix_spawn_file_actions_addopen()`, and relative paths passed to `posix_spawn()` for the executable path.

2
Base/usr/share/man/man3/posix_spawnattr_init.md
View file

@ -44,7 +44,7 @@ A `posix_spawnattr_t` object is allocated on the stack but starts in an undefine
`posix_spawnattr_destroy()` frees up resources used by a valid `posix_spawn_file_actions_t` object and puts it into an undefined state. It has to be called after a `posix_spawnattr_t` object is no longer needed.
It is valid to alternatingly call `posix_spawnattr_init()` and `posix_spawnattr_destroy()` on the same object,
It is valid to alternatingly call `posix_spawnattr_init()` and `posix_spawnattr_destroy()` on the same object,
`posix_spawnattr_setflags()` configures which attributes of the new child process `posix_spawn()` will set. It receives a bitmask that can contain: