Merge branch 'main' into quantumFlo/systemd-resolve
This commit is contained in:
Shashank Hebbar
GitHub
commit
6a4e99fb77
|
|
@ -1,12 +1,11 @@
|
|||
# tldr-pages client specification
|
||||
|
||||
**Current Specification Version:** 2.0
|
||||
**Current Specification Version:** 2.1
|
||||
|
||||
This document contains the official specification for tldr-pages clients. It is _not_ a specification of the format of the pages themselves - only a specification of how a user should be able to interface with an official client. For a list of previous versions of the specification, see the [changelog section](#Changelog) below.
|
||||
This document contains the official specification for tldr-pages clients. It is _not_ a specification of the format of the pages themselves - only a specification of how a user should be able to interface with an official client. For a list of previous versions of the specification, see the [changelog section](#changelog) below.
|
||||
|
||||
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
|
||||
|
||||
|
||||
## Terminology
|
||||
|
||||
This section defines key terms that are relevant for understanding this specification document.
|
||||
|
|
@ -24,7 +23,6 @@ If a page is common across multiple platforms, but slightly different on a given
|
|||
|
||||
For example, if the command `foo` is common to `mac`, `windows`, and `linux` but functions differently on `windows`, then the main page will be stored in `common`, and a copy will be placed in `windows` that's altered to match the different functionality.
|
||||
|
||||
|
||||
## Command-line interface
|
||||
|
||||
This section describes the standardised command-line interface (CLI) for clients implementing one. Clients that do not provide a CLI can ignore this section.
|
||||
|
|
@ -78,12 +76,12 @@ This section documents the directory structure that contains the pages themselve
|
|||
|
||||
The main version of every page is stored inside (but not directly) the `pages` directory. Inside this directory, there is a folder for each platform - for example `windows`, `linux`, and the special `common` platform:
|
||||
|
||||
- `pages/`
|
||||
- `common/`
|
||||
- `linux/`
|
||||
- `windows/`
|
||||
- `osx/`
|
||||
- ...etc.
|
||||
- `pages/`
|
||||
- `common/`
|
||||
- `linux/`
|
||||
- `windows/`
|
||||
- `osx/`
|
||||
- ...etc.
|
||||
|
||||
It is RECOMMENDED that clients support `macos` as an alias for `osx`.
|
||||
|
||||
|
|
@ -97,23 +95,21 @@ Command name | Mapped name | Filename
|
|||
`git checkout` | `git-checkout` | `git-checkout.md`
|
||||
`tar` | `tar` | `tar.md`
|
||||
|
||||
|
||||
### Translations
|
||||
|
||||
Other directories sit alongside the main `pages` directory, and contain translations of the main versions of every page - though pages MAY NOT have a translation available for a given language yet. Furthermore, a given language MAY NOT have a folder yet either. The format of these directories is `pages.<locale>`, where `<locale>` is a [POSIX Locale Name](https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html#Locale-Names) in the form of `<language>_<country>`, where:
|
||||
|
||||
- `<language>` is the shortest [ISO 639](https://en.wikipedia.org/wiki/ISO_639) language code for the chosen language (see [here](https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes) for a complete list).
|
||||
- `<country>` is the two-letter [ISO 3166-1](https://en.wikipedia.org/wiki/ISO_3166-1) country code for the chosen region (see [here](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements) for a complete list).
|
||||
- `<language>` is the shortest [ISO 639](https://en.wikipedia.org/wiki/ISO_639) language code for the chosen language (see [here](https://en.wikipedia.org/wiki/List_of_ISO_639-2_codes) for a complete list).
|
||||
- `<country>` is the two-letter [ISO 3166-1](https://en.wikipedia.org/wiki/ISO_3166-1) country code for the chosen region (see [here](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements) for a complete list).
|
||||
|
||||
Some examples:
|
||||
|
||||
- Chinese (Taiwan): `pages.zh_TW`.
|
||||
- Portuguese (Brazil): `pages.pt_BR`.
|
||||
- Italian: `pages.it`.
|
||||
- Chinese (Taiwan): `pages.zh_TW`.
|
||||
- Portuguese (Brazil): `pages.pt_BR`.
|
||||
- Italian: `pages.it`.
|
||||
|
||||
The structure inside these translation folders is identical to that of the main `pages` folder.
|
||||
|
||||
|
||||
## Page structure
|
||||
|
||||
Although this specification is about the interface that clients must provide, it is also worth noting that pages are written in standard [CommonMark](https://commonmark.org/), with the exception of the non-standard `{{` and `}}` placeholder syntax, which surrounds values in an example that users may edit. Clients MAY highlight the placeholders and MUST remove the surrounding curly braces. Clients MUST NOT treat them as the placeholder syntax if they are escaped using `\` (i.e. `\{\{` and `\}\}`) and MUST instead display literal braces, without backslashes. Placeholder escaping applies only when both braces are escaped (e.g. in `\{` or `\{{`, backslashes MUST be displayed). Clients MUST NOT break if the page format is changed within the _CommonMark_ specification.
|
||||
|
|
@ -122,8 +118,7 @@ Although this specification is about the interface that clients must provide, it
|
|||
|
||||
- `ping {{example.com}}` MUST be rendered as "ping example.com"
|
||||
- `docker inspect --format '\{\{range.NetworkSettings.Networks\}\}\{\{.IPAddress\}\}\{\{end\}\}' {{container}}` MUST be rendered as "docker inspect --format '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container"
|
||||
- `mount \\{{computer_name}}\{{share_name}} Z:` MUST be rendered as "mount \\computer_name\share_name Z:"
|
||||
|
||||
- `mount \\{{computer_name}}\{{share_name}} Z:` MUST be rendered as "mount \\\\computer_name\share_name Z:"
|
||||
|
||||
## Page resolution
|
||||
|
||||
|
|
@ -131,12 +126,13 @@ This section defines the algorithm by which a client can decide which page a use
|
|||
|
||||
After transparently replacing spaces (` `) with dashes (`-`) and lowercasing the name, clients have several decisions to make:
|
||||
|
||||
- The language of a page to display to a client
|
||||
- The platform to display a page from
|
||||
- The language of a page to display to a client
|
||||
- The platform to display a page from
|
||||
|
||||
### Platform
|
||||
|
||||
Clients MUST default to displaying the page associated with the platform on which the client is running.
|
||||
|
||||
For example, a client running on _Windows 11_ will default to displaying pages from the `windows` platform.
|
||||
Clients MAY provide a user-configurable option to override this behaviour, however.
|
||||
|
||||
|
|
@ -155,6 +151,8 @@ Steps #3 and #4 may be done in either order.
|
|||
|
||||
It is possible that due to this page resolution logic, the client may show a page which does not belong to the host platform because a page can reside in `common`, and not be present on the host platform. Clients must not assume that a given command is always executable on the host platform.
|
||||
|
||||
It is RECOMMENDED that clients detect new platforms added to the relevant `pages` directory automatically.
|
||||
|
||||
#### If a page is not found
|
||||
|
||||
If a page cannot be found in _any_ platform, then it is RECOMMENDED that clients display an error message with a link to create a new issue against the `tldr-pages/tldr` GitHub repository. Said link might take the following form:
|
||||
|
|
@ -169,7 +167,6 @@ where `{command_name}` is the name of the command that was not found. Clients th
|
|||
|
||||
If multiple versions of a page were found for different platforms, then a client MAY choose to display a notice to the user notifying them of this.
|
||||
|
||||
|
||||
## Language
|
||||
|
||||
Pages can be written in multiple languages. If a client has access to environment variables, it MUST use them to derive the preferred user language as described in the next paragraphs. If not, then clients MUST make reasonable assumptions based on the information provided by the environment in which they operate (e.g. consulting `navigator.languages` in a browser, etc.).
|
||||
|
|
@ -205,12 +202,14 @@ The [`LC_MESSAGES` environment variable](https://www.gnu.org/software/gettext/ma
|
|||
|
||||
Here's an example of how the lookup should be done on `linux` having set `LANG=it` and `LANGUAGE="it:fr:en"`:
|
||||
|
||||
1. pages.it/linux/some-page.md -> does not exist
|
||||
2. pages.fr/linux/some-page.md -> does not exist
|
||||
3. pages/linux/some-page.md -> does not exist
|
||||
4. pages.it/common/some-page.md -> does not exist
|
||||
5. pages.fr/common/some-page.md -> does not exist
|
||||
6. pages/common/some-page.md -> FOUND!
|
||||
Step | Path checked | Outcome
|
||||
------|--------------------------------|-----------------------
|
||||
1 | pages.it/linux/some-page.md | does not exist
|
||||
2 | pages.fr/linux/some-page.md | does not exist
|
||||
3 | pages/linux/some-page.md | does not exist
|
||||
4 | pages.it/common/some-page.md | does not exist
|
||||
5 | pages.fr/common/some-page.md | does not exist
|
||||
6 | pages/common/some-page.md | FOUND!
|
||||
|
||||
## Caching
|
||||
|
||||
|
|
@ -218,7 +217,6 @@ If appropriate, it is RECOMMENDED that clients implement a cache of pages. If im
|
|||
|
||||
Caching SHOULD be done according to the user's language configuration (if any), to not waste unneeded space for unused languages. Additionally, clients MAY automatically update the cache regularly.
|
||||
|
||||
|
||||
## Changelog
|
||||
|
||||
<!--
|
||||
|
|
@ -232,35 +230,40 @@ including the changes. NOTE: tagging of the commit with a new version tag (in
|
|||
the form `vX.Y`) should be done immediately AFTER merging the version bump, as
|
||||
the commit hash changes when merging with squash or rebase.
|
||||
-->
|
||||
- Unreleased
|
||||
|
||||
- [v2.0, September 10th 2023](https://github.com/tldr-pages/tldr/blob/v2.0/CLIENT-SPECIFICATION.md) ([#10148](https://github.com/tldr-pages/tldr/pull/10148))
|
||||
- Add recommendation to support `macos` alias for `osx` ([#7514](https://github.com/tldr-pages/tldr/pull/7514))
|
||||
- Drop the special "all" platform from the `--list` flag ([#7561](https://github.com/tldr-pages/tldr/pull/7561))
|
||||
- Drop the `master` branch from the assets link. ([#9668](https://github.com/tldr-pages/tldr/pull/9668))
|
||||
- Require support for long options ([#9651](https://github.com/tldr-pages/tldr/pull/9651))
|
||||
- Add recommendation to support caching individual translation archives ([#10148](https://github.com/tldr-pages/tldr/pull/10148))
|
||||
- Unreleased
|
||||
|
||||
- [v1.5, March 17th 2021](https://github.com/tldr-pages/tldr/blob/v1.5/CLIENT-SPECIFICATION.md) ([#5428](https://github.com/tldr-pages/tldr/pull/5428))
|
||||
- Add requirement for converting command names to lowercase before running the page resolution algorithm.
|
||||
- Use HTTPS for archive links.
|
||||
- [v2.1, November 30th 2023](https://github.com/tldr-pages/tldr/blob/v2.1/CLIENT-SPECIFICATION.md) ([#11523](https://github.com/tldr-pages/tldr/pull/11523))
|
||||
- Add requirement to support escaping the placeholder syntax in certain pages ([#10730](https://github.com/tldr-pages/tldr/pull/10730))
|
||||
- Add suggestion to detect new platforms added to the relevant `pages` directory automatically ([#11523](https://github.com/tldr-pages/tldr/pull/11523))
|
||||
|
||||
- [v1.4, August 13th 2020](https://github.com/tldr-pages/tldr/blob/v1.4/CLIENT-SPECIFICATION.md) ([#4246](https://github.com/tldr-pages/tldr/pull/4246))
|
||||
- Add requirement for CLI clients to use non-zero exit code on failing to find a page.
|
||||
- [v2.0, September 10th 2023](https://github.com/tldr-pages/tldr/blob/v2.0/CLIENT-SPECIFICATION.md) ([#10148](https://github.com/tldr-pages/tldr/pull/10148))
|
||||
- Add recommendation to support `macos` alias for `osx` ([#7514](https://github.com/tldr-pages/tldr/pull/7514))
|
||||
- Drop the special "all" platform from the `--list` flag ([#7561](https://github.com/tldr-pages/tldr/pull/7561))
|
||||
- Drop the `master` branch from the assets link. ([#9668](https://github.com/tldr-pages/tldr/pull/9668))
|
||||
- Require support for long options ([#9651](https://github.com/tldr-pages/tldr/pull/9651))
|
||||
- Add recommendation to support caching individual translation archives ([#10148](https://github.com/tldr-pages/tldr/pull/10148))
|
||||
|
||||
- [v1.3, June 11th 2020](https://github.com/tldr-pages/tldr/blob/v1.3/CLIENT-SPECIFICATION.md) ([#4101](https://github.com/tldr-pages/tldr/pull/4101))
|
||||
- Clarified fallback to English in the language resolution algorithm.
|
||||
- Update the `LANG` and `LANGUAGE` environment variables to conform to the GNU spec.
|
||||
- [v1.5, March 17th 2021](https://github.com/tldr-pages/tldr/blob/v1.5/CLIENT-SPECIFICATION.md) ([#5428](https://github.com/tldr-pages/tldr/pull/5428))
|
||||
- Add requirement for converting command names to lowercase before running the page resolution algorithm.
|
||||
- Use HTTPS for archive links.
|
||||
|
||||
- [v1.2, July 3rd 2019](https://github.com/tldr-pages/tldr/blob/v1.2/CLIENT-SPECIFICATION.md) ([#3168](https://github.com/tldr-pages/tldr/pull/3168))
|
||||
- Addition of a new `-L, --language` recommended command-line option.
|
||||
- Rewording of the language section, also encouraging the use of configuration files for language.
|
||||
- Shift from BCP-47 to POSIX style locale tags, with consequent **deprecation of previous versions of the spec**.
|
||||
- Clearer clarification about the recommended caching functionality.
|
||||
- Correction of the usage of the term "arguments" in the homonym section.
|
||||
- [v1.4, August 13th 2020](https://github.com/tldr-pages/tldr/blob/v1.4/CLIENT-SPECIFICATION.md) ([#4246](https://github.com/tldr-pages/tldr/pull/4246))
|
||||
- Add requirement for CLI clients to use non-zero exit code on failing to find a page.
|
||||
|
||||
- [v1.1, April 1st 2019](https://github.com/tldr-pages/tldr/blob/v1.1/CLIENT-SPECIFICATION.md) (deprecated) ([#2859](https://github.com/tldr-pages/tldr/pull/2859))
|
||||
- Clarified platform section.
|
||||
- [v1.3, June 11th 2020](https://github.com/tldr-pages/tldr/blob/v1.3/CLIENT-SPECIFICATION.md) ([#4101](https://github.com/tldr-pages/tldr/pull/4101))
|
||||
- Clarified fallback to English in the language resolution algorithm.
|
||||
- Update the `LANG` and `LANGUAGE` environment variables to conform to the GNU spec.
|
||||
|
||||
- [v1.0, January 23rd 2019](https://github.com/tldr-pages/tldr/blob/v1.0/CLIENT-SPECIFICATION.md) (deprecated) ([#2706](https://github.com/tldr-pages/tldr/pull/2706))
|
||||
- Initial release.
|
||||
- [v1.2, July 3rd 2019](https://github.com/tldr-pages/tldr/blob/v1.2/CLIENT-SPECIFICATION.md) ([#3168](https://github.com/tldr-pages/tldr/pull/3168))
|
||||
- Addition of a new `-L, --language` recommended command-line option.
|
||||
- Rewording of the language section, also encouraging the use of configuration files for language.
|
||||
- Shift from BCP-47 to POSIX style locale tags, with consequent **deprecation of previous versions of the spec**.
|
||||
- Clearer clarification about the recommended caching functionality.
|
||||
- Correction of the usage of the term "arguments" in the homonym section.
|
||||
|
||||
- [v1.1, April 1st 2019](https://github.com/tldr-pages/tldr/blob/v1.1/CLIENT-SPECIFICATION.md) (deprecated) ([#2859](https://github.com/tldr-pages/tldr/pull/2859))
|
||||
- Clarified platform section.
|
||||
|
||||
- [v1.0, January 23rd 2019](https://github.com/tldr-pages/tldr/blob/v1.0/CLIENT-SPECIFICATION.md) (deprecated) ([#2706](https://github.com/tldr-pages/tldr/pull/2706))
|
||||
- Initial release.
|
||||
|
|
|
|||
|
|
@ -7,15 +7,15 @@
|
|||
|
||||
`7z a {{archivo_comprimido.7z}} {{ruta/al/archivo_o_directorio_a_comprimir}}`
|
||||
|
||||
- Encriptar un archivo comprimido existente (incluyendo cabeceras):
|
||||
- Encripta un archivo comprimido existente (incluyendo cabeceras):
|
||||
|
||||
`7z a {{archivo_encriptado.7z}} -p{{contraseña}} -mhe=on {{archivo_comprimido.7z}}`
|
||||
|
||||
- Extraer un archivo comprimido en formato `.7z` con la estructura original que tenía antes de comprimir:
|
||||
- Extrae un archivo comprimido en formato `.7z` con la estructura original que tenía antes de comprimir:
|
||||
|
||||
`7z x {{archivo_comprimido.7z}}`
|
||||
|
||||
- Extraer un archivo comprimido en una ruta definida por el usuario:
|
||||
- Extrae un archivo comprimido en una ruta definida por el usuario:
|
||||
|
||||
`7z x {{archivo_comprimido.7z}} -o {{ruta/donde/extraer}}`
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@
|
|||
|
||||
- E[x]trae un archivo a un directorio específico:
|
||||
|
||||
`7zr x {{ruta/al/larchivo.7z}} -o{ruta/de/salida}}`
|
||||
`7zr x {{ruta/al/archivo.7z}} -o{ruta/de/salida}}`
|
||||
|
||||
- E[x]trae un archivo a `stdout`:
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@
|
|||
|
||||
`assimp export {{archivo_entrada.stl}} {{archivo_salida.obj}}`
|
||||
|
||||
- Convertir un archivo utilizando parámetros personalizados (el archivo dox_cmd.h en el código fuente de assimp enumera los parámetros disponibles):
|
||||
- Convierte un archivo utilizando parámetros personalizados (el archivo dox_cmd.h en el código fuente de assimp enumera los parámetros disponibles):
|
||||
|
||||
`assimp export {{archivo_entrada.stl}} {{archivo_salida.obj}} {{parametros}}`
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
|
||||
`dotnet publish --self-contained true --runtime {{identificador_del_entorno_en_tiempo_de_ejecución}} {{ruta/al/archivo_del_proyecto}}`
|
||||
|
||||
- Empaqueta la aplicación en un archivo ejecutable unico de una plataforma específica:
|
||||
- Empaqueta la aplicación en un archivo ejecutable único de una plataforma específica:
|
||||
|
||||
`dotnet publish --runtime {{identificador_del_entorno_en_tiempo_de_ejecucución}} -p:PublishSingleFile=true {{ruta/al/archivo_del_proyecto}}`
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# dotnet restore
|
||||
|
||||
> Restarua las dependencias y herramientas de un proyecto .NET.
|
||||
> Restaura las dependencias y herramientas de un proyecto .NET.
|
||||
> Más información: <https://learn.microsoft.com/dotnet/core/tools/dotnet-restore>.
|
||||
|
||||
- Restaura dependencias para un proyecto o solución .NET en el directorio actual:
|
||||
|
|
@ -11,7 +11,7 @@
|
|||
|
||||
`dotnet restore {{ruta/al/proyecto_o_solución}}`
|
||||
|
||||
- Restaura depedencias sin almacenar las solicitudes HTTP en caché:
|
||||
- Restaura dependencias sin almacenar las solicitudes HTTP en caché:
|
||||
|
||||
`dotnet restore --no-cache`
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,28 @@
|
|||
# chatgpt
|
||||
|
||||
> Shell script para usar ChatGPT de OpenAI y DALL-E desde la terminal.
|
||||
> Más información: <https://github.com/0xacx/chatGPT-shell-cli>.
|
||||
|
||||
- Comienza en modo chat:
|
||||
|
||||
`chatgpt`
|
||||
|
||||
- Dar un [p]rompt para responder:
|
||||
|
||||
`chatgpt --prompt "{{¿Cuál es la expresión regular para emparejar una dirección de correo electrónico?}}"`
|
||||
|
||||
- Inicia en modo chat utilizando un [m]odelo específico (por defecto es `gpt-3.5-turbo`):
|
||||
|
||||
`chatgpt --model {{gpt-4}}`
|
||||
|
||||
- Inicia en modo chat con un prompt [i]nicial:
|
||||
|
||||
`chatgpt --init-prompt "{{Tú eres Rick, de Rick y Morty. Responde a las preguntas usando su amaneramiento e incluye chistes insultantes.}}"`
|
||||
|
||||
- Envía el resultado de un comando a ChatGPT como un prompt:
|
||||
|
||||
`echo "{{¿Cómo ver los procesos en ejecución en Ubuntu?}}" | chatgpt`
|
||||
|
||||
- Genera una imagen utilizando DALL-E:
|
||||
|
||||
`chatgpt --prompt "{{image: Un gato blanco}}"`
|
||||
|
|
@ -29,4 +29,8 @@
|
|||
|
||||
- Geef een [l]ijst met de inhoud van het archiefbestand:
|
||||
|
||||
`7z l {{archief.7z}}`
|
||||
`7z l {{pad/naar/archief.7z}}`
|
||||
|
||||
- Zet het niveau van compressie (hoger betekent meer compressie, maar langzamer):
|
||||
|
||||
`7z a {{pad/naar/archief.7z}} -mx={{0|1|3|5|7|9}} {{pad/naar/bestand_of_map}}`
|
||||
|
|
|
|||
|
|
@ -28,6 +28,10 @@
|
|||
|
||||
`7za a -t{{7z|bzip2|gzip|lzip|tar|...}} {{pad/naar/archief.7z}} {{pad/naar/bestand_of_map}}`
|
||||
|
||||
- Lijst de inhoud van een archief op:
|
||||
- Geef een [l]ijst met de inhoud van het archiefbestand:
|
||||
|
||||
`7za l {{pad/naar/archief.7z}}`
|
||||
|
||||
- Zet het niveau van compressie (hoger betekent meer compressie, maar langzamer):
|
||||
|
||||
`7za a {{pad/naar/archief.7z}} -mx={{0|1|3|5|7|9}} {{pad/naar/bestand_of_map}}`
|
||||
|
|
|
|||
|
|
@ -24,6 +24,10 @@
|
|||
|
||||
`7zr x {{pad/naar/archief.7z}} -so`
|
||||
|
||||
- Lijst de inhoud van een archief op:
|
||||
- Geef een [l]ijst met de inhoud van het archiefbestand:
|
||||
|
||||
`7zr l {{pad/naar/archief.7z}}`
|
||||
|
||||
- Zet het niveau van compressie (hoger betekent meer compressie, maar langzamer):
|
||||
|
||||
`7zr a {{pad/naar/archief.7z}} -mx={{0|1|3|5|7|9}} {{pad/naar/bestand_of_map}}`
|
||||
|
|
|
|||
|
|
@ -0,0 +1,36 @@
|
|||
# clamdscan
|
||||
|
||||
> Een command-line virus scanner die gebruik maakt van de ClamAV Daemon.
|
||||
> Meer informatie: <https://docs.clamav.net/manual/Usage/Scanning.html#clamdscan>.
|
||||
|
||||
- Scan een bestand of map op kwetsbaarheden:
|
||||
|
||||
`clamdscan {{pad/naar/bestand_of_map}}`
|
||||
|
||||
- Scan data van `stdin`:
|
||||
|
||||
`{{commando}} | clamdscan -`
|
||||
|
||||
- Scan de huidige map en toon alleen geïnfecteerde bestanden:
|
||||
|
||||
`clamdscan --infected`
|
||||
|
||||
- Sla het scan rapport op in een log bestand:
|
||||
|
||||
`clamdscan --log {{pad/naar/log_bestand}}`
|
||||
|
||||
- Verplaats geïnfecteerde bestanden naar een specifieke map:
|
||||
|
||||
`clamdscan --move {{pad/naar/quarantaine_map}}`
|
||||
|
||||
- Verwijder geïnfecteerde bestanden:
|
||||
|
||||
`clamdscan --remove`
|
||||
|
||||
- Gebruik meerdere threads voor het scannen van een map:
|
||||
|
||||
`clamdscan --multiscan`
|
||||
|
||||
- Geef de bestandsdescriptor door in plaats van het bestand naar de daemon:
|
||||
|
||||
`clamdscan --fdpass`
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
# clamscan
|
||||
|
||||
> Een command-line virus scanner.
|
||||
> Meer informatie: <https://docs.clamav.net/manual/Usage/Scanning.html#clamscan>.
|
||||
|
||||
- Scan een bestand op kwetsbaarheden:
|
||||
|
||||
`clamscan {{pad/naar/bestand}}`
|
||||
|
||||
- Scan alle bestanden recursief in een specifieke map:
|
||||
|
||||
`clamscan -r {{pad/naar/map}}`
|
||||
|
||||
- Scan data van `stdin`:
|
||||
|
||||
`{{commando}} | clamscan -`
|
||||
|
||||
- Specificeer een virus database bestand of map van bestanden:
|
||||
|
||||
`clamscan --database {{pad/naar/database_bestand_of_map}}`
|
||||
|
||||
- Scan de huidige map en toon alleen geïnfecteerde bestanden:
|
||||
|
||||
`clamscan --infected`
|
||||
|
||||
- Sla het scan rapport op in een log bestand:
|
||||
|
||||
`clamscan --log {{pad/naar/log_bestand}}`
|
||||
|
||||
- Verplaats geïnfecteerde bestanden naar een specifieke map:
|
||||
|
||||
`clamscan --move {{pad/naar/quarantine_map}}`
|
||||
|
||||
- Verwijder geïnfecteerde bestanden:
|
||||
|
||||
`clamscan --remove yes`
|
||||
|
|
@ -0,0 +1,8 @@
|
|||
# freshclam
|
||||
|
||||
> Update virus definities voor ClamAV antivirus programma.
|
||||
> Meer informatie: <https://www.clamav.net>.
|
||||
|
||||
- Update virus definities:
|
||||
|
||||
`freshclam`
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
# todo
|
||||
|
||||
> Een eenvoudige, op standaarden gebaseerde, opdrachtregel todo manager.
|
||||
> Meer informatie: <https://todoman.readthedocs.io>.
|
||||
|
||||
- Toon startbare taken:
|
||||
|
||||
`todo list --startable`
|
||||
|
||||
- Voeg een nieuwe taak toe aan de werklijst:
|
||||
|
||||
`todo new {{ding_om_te_doen}} --list {{werk}}`
|
||||
|
||||
- Voeg een locatie toe aan een taak met een gegeven ID:
|
||||
|
||||
`todo edit --location {{locatie_naam}} {{taak_id}}`
|
||||
|
||||
- Toon details over een taak:
|
||||
|
||||
`todo show {{taak_id}}`
|
||||
|
||||
- Markeer taken met de opgegeven IDs als voltooid:
|
||||
|
||||
`todo done {{taak_id1 taak_id2 ...}}`
|
||||
|
||||
- Verwijder een taak:
|
||||
|
||||
`todo delete {{taak_id}}`
|
||||
|
||||
- Verwijder voltooide taken en reset de IDs van de overgebleven taken:
|
||||
|
||||
`todo flush`
|
||||
|
|
@ -1,7 +1,6 @@
|
|||
# distrobox-export
|
||||
|
||||
> Exporteer app/service/binary van container naar host-besturingssysteem.
|
||||
> Subcommando van `distrobox`. Bekijk ook: `tldr distrobox`.
|
||||
> Exporteer app/service/binary van container naar host-besturingssysteem. Bekijk ook: `tldr distrobox`.
|
||||
> Meer informatie: <https://distrobox.it/usage/distrobox-export>.
|
||||
|
||||
- Exporteer een app van de container naar de host (het desktop pictogram verschijnt in de applicatielijst van uw hostsysteem):
|
||||
|
|
|
|||
|
|
@ -0,0 +1,16 @@
|
|||
# pulumi up
|
||||
|
||||
> Create or update the resources in a stack.
|
||||
> More information: <https://www.pulumi.com/docs/cli/commands/pulumi_up/>.
|
||||
|
||||
- Preview and deploy changes to a program and/or infrastructure:
|
||||
|
||||
`pulumi up`
|
||||
|
||||
- Automatically approve and perform the update after previewing it:
|
||||
|
||||
`pulumi up --yes`
|
||||
|
||||
- Preview and deploy changes in a specific stack:
|
||||
|
||||
`pulumi up --stack {{stack}}`
|
||||
|
|
@ -1,6 +1,7 @@
|
|||
# pulumi
|
||||
|
||||
> Define infrastructure on any cloud using familiar programming languages.
|
||||
> Some subcommands such as `pulumi up` have their own usage documentation.
|
||||
> More information: <https://www.pulumi.com/docs/reference/cli>.
|
||||
|
||||
- Create a new project using a template:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,20 @@
|
|||
# vboxmanage-clonevm
|
||||
|
||||
> Create a clone of an existing virtual machine (VM).
|
||||
> More information: <https://www.virtualbox.org/manual/ch08.html#vboxmanage-clonevm>.
|
||||
|
||||
- Clone the specified VM:
|
||||
|
||||
`VBoxManage clonevm {{vm_name}}`
|
||||
|
||||
- Specify a new name for the new VM:
|
||||
|
||||
`VBoxManage clonevm {{vm_name}} --name {{new_vm_name}}`
|
||||
|
||||
- Indicate the folder where the new VM configuration is saved:
|
||||
|
||||
`VBoxManage clonevm {{vm_name}} --basefolder {{path/to/directory}}`
|
||||
|
||||
- Register the cloned VM in VirtualBox:
|
||||
|
||||
`VBoxManage clonevm {{vm_name}} --register`
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
# vboxmanage-createvm
|
||||
|
||||
> Create a new virtual machine.
|
||||
> More information: <https://www.virtualbox.org/manual/ch08.html#vboxmanage-createvm>.
|
||||
|
||||
- Create a new VM with default settings:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}}`
|
||||
|
||||
- Set the base folder where the VM configuration will be stored:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}} --basefolder {{path/to/directory}}`
|
||||
|
||||
- Set the guest OS type (one of `VBoxManage list ostypes`) for the imported VM:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}} --ostype {{ostype}}`
|
||||
|
||||
- Register the created VM in VirtualBox:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}} --register`
|
||||
|
||||
- Set the VM to the specified groups:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}} --group {{group1,group2,...}}`
|
||||
|
||||
- Set the Universally Unique Identifier (UUID) of the VM:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}} --uuid {{uuid}}`
|
||||
|
||||
- Set the cipher to use for encryption:
|
||||
|
||||
`VBoxManage createvm --name {{vm_name}} --cipher {{AES-128|AES-256}}`
|
||||
|
|
@ -0,0 +1,24 @@
|
|||
# vboxmanage-export
|
||||
|
||||
> Export virtual machines to a virtual appliance (ISO) or a cloud service.
|
||||
> More information: <https://www.virtualbox.org/manual/ch08.html#vboxmanage-export>.
|
||||
|
||||
- Specify the target OVA file:
|
||||
|
||||
`VBoxManage export --output {{path/to/filename.ova}}`
|
||||
|
||||
- Export in OVF 0.9 legacy mode:
|
||||
|
||||
`VBoxManage export --legacy09`
|
||||
|
||||
- Export in OVF (0.9|1.0|2.0) format:
|
||||
|
||||
`VBoxManage export --{{ovf09|ovf10|ovf20}}`
|
||||
|
||||
- Create manifest of the exported files:
|
||||
|
||||
`VBoxManage export --manifest`
|
||||
|
||||
- Specify a description of the VM:
|
||||
|
||||
`VBoxManage export --description "{{vm_description}}"`
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
# vboxmanage-import
|
||||
|
||||
> Import a previously exported virtual machine (VM).
|
||||
> More information: <https://www.virtualbox.org/manual/ch08.html#vboxmanage-import>.
|
||||
|
||||
- Import a VM from an OVF or OVA file:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}}`
|
||||
|
||||
- Set the name of the imported VM:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --name {{vm_name}}`
|
||||
|
||||
- Indicate the folder where the configuration of the imported VM will be stored:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --basefolder {{path/to/directory}}`
|
||||
|
||||
- Register the imported VM in VirtualBox:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --register`
|
||||
|
||||
- Perform a dry run to check the import without actually importing:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --dry-run`
|
||||
|
||||
- Set the guest OS type (one of `VBoxManage list ostypes`) for the imported VM:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --ostype={{ostype}}`
|
||||
|
||||
- Set the memory (in megabytes) for the imported VM:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --memory={{1}}`
|
||||
|
||||
- Set the number of CPUs for the imported VM:
|
||||
|
||||
`VBoxManage import {{path/to/file.ovf}} --cpus={{1}}`
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
# vboxmanage-registervm
|
||||
|
||||
> Register a virtual machine (VM).
|
||||
> More information: <https://www.virtualbox.org/manual/ch08.html#vboxmanage-registervm>.
|
||||
|
||||
- Register an existing VM:
|
||||
|
||||
`VBoxManage registervm {{path/to/filename.vbox}}`
|
||||
|
||||
- Supply the encryption password file of the VM:
|
||||
|
||||
`VBoxManage registervm {{path/to/filename.vbox}} --password {{path/to/password_file}}`
|
||||
|
||||
- Prompt for the encryption password on the command line:
|
||||
|
||||
`VBoxManage registervm {{path/to/filename.vbox}} --password -`
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
# vboxmanage-unregistervm
|
||||
|
||||
> Unregister a virtual machine (VM).
|
||||
> More information: <https://www.virtualbox.org/manual/ch08.html#vboxmanage-unregistervm>.
|
||||
|
||||
- Unregister an existing VM:
|
||||
|
||||
`VBoxManage unregistervm {{uuid|vm_name}}`
|
||||
|
||||
- Delete hard disk image files, all saved state files, VM logs, and XML VM machine files:
|
||||
|
||||
`VBoxManage unregistervm {{uuid|vm_name}} --delete`
|
||||
|
||||
- Delete all files from the VM:
|
||||
|
||||
`VBoxManage unregistervm {{uuid|vm_name}} --delete-all`
|
||||
|
|
@ -1,13 +1,13 @@
|
|||
# exiqgrep
|
||||
|
||||
> The `exiqgrep` utility is a Perl script offering possibilities to `grep` in the Exim queue output.
|
||||
> Perl script offering possibilities to `grep` in the Exim queue output.
|
||||
> More information: <https://www.exim.org/exim-html-current/doc/html/spec_html/ch-exim_utilities.html>.
|
||||
|
||||
- Match the sender address using a case-insensitive search:
|
||||
|
||||
`exiqgrep -f '<{{email@somedomain.com}}>'`
|
||||
|
||||
- Match the sender address, and display message IDs only:
|
||||
- Match the sender address and display message IDs only:
|
||||
|
||||
`exiqgrep -i -f '<{{email@somedomain.com}}>'`
|
||||
|
||||
|
|
|
|||
|
|
@ -1,17 +1,17 @@
|
|||
# playerctl
|
||||
|
||||
> Utility to control different media players.
|
||||
> Control media players via MPRIS.
|
||||
> More information: <https://github.com/altdesktop/playerctl>.
|
||||
|
||||
- Toggle play:
|
||||
|
||||
`playerctl play-pause`
|
||||
|
||||
- Next media:
|
||||
- Skip to the next track:
|
||||
|
||||
`playerctl next`
|
||||
|
||||
- Previous media:
|
||||
- Go back to the previous track:
|
||||
|
||||
`playerctl previous`
|
||||
|
||||
|
|
@ -21,12 +21,12 @@
|
|||
|
||||
- Send a command to a specific player:
|
||||
|
||||
`playerctl --player={{player_name}} {{command}}`
|
||||
`playerctl --player {{player_name}} {{play-pause|next|previous|...}}`
|
||||
|
||||
- Send a command to all players:
|
||||
|
||||
`playerctl --all-players {{command}}`
|
||||
`playerctl --all-players {{play-pause|next|previous|...}}`
|
||||
|
||||
- Show now playing:
|
||||
- Display metadata about the current track:
|
||||
|
||||
`playerctl metadata --format "Now playing: {{artist}} - {{album}} - {{title}}"`
|
||||
`playerctl metadata --format "{{Now playing: \{\{artist\}\} - \{\{album\}\} - \{\{title\}\}}}"`
|
||||
|
|
|
|||
|
|
@ -0,0 +1,25 @@
|
|||
# rargs
|
||||
|
||||
> Execute a command for each line of standard input.
|
||||
> Like `xargs`, but with pattern matching support.
|
||||
> More information: <https://github.com/lotabout/rargs>.
|
||||
|
||||
- Execute a command for every line of input, just like `xargs` (`{0}` indicates where to substitute in the text):
|
||||
|
||||
`{{command}} | rargs {{command}} {0}`
|
||||
|
||||
- Do a dry run, which prints the commands that would be run instead of executing them:
|
||||
|
||||
`{{command}} | rargs -e {{command}} {0}`
|
||||
|
||||
- Remove the `.bak` extension from every file in a list:
|
||||
|
||||
`{{command}} | rargs -p '(.*).bak mv {0} {1}`
|
||||
|
||||
- Execute commands in parallel:
|
||||
|
||||
`{{command}} | rargs -w {{max-procs}}`
|
||||
|
||||
- Consider each line of input to be separated by a NUL character (`\0`) instead of a newline (`\n`):
|
||||
|
||||
`{{command}} | rargs -0 {{command}} {0}`
|
||||
|
|
@ -0,0 +1,29 @@
|
|||
# Get-Command
|
||||
|
||||
> List and get available commands in the current PowerShell session.
|
||||
> This command can only be run through PowerShell.
|
||||
> More information: <https://learn.microsoft.com/powershell/module/microsoft.powershell.core/get-command>.
|
||||
|
||||
- List all available PowerShell commands (aliases, cmdlets, functions) in the current computer:
|
||||
|
||||
`Get-Command`
|
||||
|
||||
- List all available PowerShell commands in the current session:
|
||||
|
||||
`Get-Command -ListImported`
|
||||
|
||||
- List only PowerShell aliases/cmdlets/functions available in the computer:
|
||||
|
||||
`Get-Command -Type {{Alias|Cmdlet|Function}}`
|
||||
|
||||
- List only programs or commands available on PATH in the current session:
|
||||
|
||||
`Get-Command -Type Application`
|
||||
|
||||
- List only PowerShell commands by the module name, e.g. `Microsoft.PowerShell.Utility` for utility-related commands:
|
||||
|
||||
`Get-Command -Module {{module}}`
|
||||
|
||||
- Get the command information (e.g. version number or module name) by its name:
|
||||
|
||||
`Get-Command {{command}}`
|
||||
|
|
@ -1,28 +1,28 @@
|
|||
# Get-Help
|
||||
|
||||
> Display help information and documentation for PowerShell commands, aka. cmdlets.
|
||||
> Display help information and documentation for PowerShell commands (aliases, cmdlets, and functions).
|
||||
> This command can only be run through PowerShell.
|
||||
> More information: <https://learn.microsoft.com/powershell/module/microsoft.powershell.core/get-help>.
|
||||
|
||||
- Display general help information for a specific cmdlet:
|
||||
- Display general help information for a specific PowerShell command:
|
||||
|
||||
`Get-Help {{cmdlet}}`
|
||||
`Get-Help {{command}}`
|
||||
|
||||
- Display a more detailed documentation for a specific cmdlet:
|
||||
- Display a more detailed documentation for a specific PowerShell command:
|
||||
|
||||
`Get-Help {{cmdlet}} -Detailed`
|
||||
`Get-Help {{command}} -Detailed`
|
||||
|
||||
- Display the full technical documentation for a specific cmdlet:
|
||||
- Display the full technical documentation for a specific PowerShell command:
|
||||
|
||||
`Get-Help {{cmdlet}} -Full`
|
||||
`Get-Help {{command}} -Full`
|
||||
|
||||
- Print only the documentation for a specific parameter of the cmdlet (use `*` to show all parameters), if available:
|
||||
- Print only the documentation for a specific parameter of the PowerShell command (use `*` to show all parameters), if available:
|
||||
|
||||
`Get-Help {{cmdlet}} -Parameter {{parameter}}`
|
||||
`Get-Help {{command}} -Parameter {{parameter}}`
|
||||
|
||||
- Print only the examples of the cmdlet, if available:
|
||||
|
||||
`Get-Help {{cmdlet}} -Examples`
|
||||
`Get-Help {{command}} -Examples`
|
||||
|
||||
- List all available cmdlet help pages:
|
||||
|
||||
|
|
@ -32,6 +32,6 @@
|
|||
|
||||
`Update-Help`
|
||||
|
||||
- View an online version of cmdlet documentation in the default web browser:
|
||||
- View an online version of PowerShell command documentation in the default web browser:
|
||||
|
||||
`Get-Help {{cmdlet}} -Online`
|
||||
`Get-Help {{command}} -Online`
|
||||
|
|
|
|||
|
|
@ -0,0 +1,13 @@
|
|||
# Get-WUApiVersion
|
||||
|
||||
> Get the Windows Update Agent version. Part of external `PSWindowsUpdate` module.
|
||||
> This command can only be run under PowerShell.
|
||||
> More information: <https://github.com/mgajda83/PSWindowsUpdate>.
|
||||
|
||||
- Get the currently-installed Windows Update Agent version:
|
||||
|
||||
`Get-WUApiVersion`
|
||||
|
||||
- Send the current configuration data via email (SMTP):
|
||||
|
||||
`Get-WUApiVersion -SendReport -PSWUSettings @{SmtpServer="{{smtp_server}}"; Port={{smtp_port}} From="{{sender_email}}" To="{{receiver_email}}"}`
|
||||
|
|
@ -0,0 +1,25 @@
|
|||
# Get-WUHistory
|
||||
|
||||
> Get the history of installed updates from Windows Update. Part of external `PSWindowsUpdate` module.
|
||||
> This command can only be run under PowerShell.
|
||||
> More information: <https://github.com/mgajda83/PSWindowsUpdate>.
|
||||
|
||||
- Get list of update history:
|
||||
|
||||
`Get-WUHistory`
|
||||
|
||||
- List the last 10 installed updates:
|
||||
|
||||
`Get-WUHistory -Last {{10}}`
|
||||
|
||||
- List all updates installed from a specific date to today:
|
||||
|
||||
`Get-WUHistory -MaxDate {{date}}`
|
||||
|
||||
- List all updates installed in the past 24 hours:
|
||||
|
||||
`Get-WUHistory -MaxDate (Get-Date).AddDays(-1)`
|
||||
|
||||
- Send the results via email (SMTP):
|
||||
|
||||
`Get-WUHistory -SendReport -PSWUSettings @{SmtpServer="{{smtp_server}}"; Port={{smtp_port}} From="{{sender_email}}" To="{{receiver_email}}"}`
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
# Get-WUSettings
|
||||
|
||||
> Get the current Windows Update Agent configuration. Part of external `PSWindowsUpdate` module.
|
||||
> This command can only be run under PowerShell.
|
||||
> More information: <https://github.com/mgajda83/PSWindowsUpdate>.
|
||||
|
||||
- Get the current Windows Update Agent configuration:
|
||||
|
||||
`Get-WUSettings`
|
||||
|
||||
- Send the current configuration data via email (SMTP):
|
||||
|
||||
`Get-WUSettings -SendReport -PSWUSettings @{SmtpServer="{{smtp_server}}"; Port={{smtp_port}} From="{{sender_email}}" To="{{receiver_email}}"}`
|
||||
|
|
@ -0,0 +1,36 @@
|
|||
# Install-Module
|
||||
|
||||
> Install PowerShell modules from PowerShell Gallery, NuGet, and other repositories.
|
||||
> More information: <https://learn.microsoft.com/powershell/module/powershellget/install-module>.
|
||||
|
||||
- Install a module, or update it to the latest available version:
|
||||
|
||||
`Install-Module {{module}}`
|
||||
|
||||
- Install a module with a specific version:
|
||||
|
||||
`Install-Module {{module}} -RequiredVersion {{version}}`
|
||||
|
||||
- Install a module no earlier than a specific version:
|
||||
|
||||
`Install-Module {{module}} -MinimumVersion {{version}}`
|
||||
|
||||
- Specify a range of supported versions (inclusive) of the required module:
|
||||
|
||||
`Install-Module {{module}} -MinimumVersion {{minimum_version}} -MaximumVersion {{maximum_version}}`
|
||||
|
||||
- Install module from a specific repository:
|
||||
|
||||
`Install-Module {{module}} -Repository {{repository}}`
|
||||
|
||||
- Install module from specific repositories:
|
||||
|
||||
`Install-Module {{module}} -Repository {{repository1 , repository2 , ...}}`
|
||||
|
||||
- Install the module for all/current user:
|
||||
|
||||
`Install-Module {{module}} -Scope {{AllUsers|CurrentUser}}`
|
||||
|
||||
- Perform a dry run to determine which modules will be installed, upgraded, or removed through `Install-Module`:
|
||||
|
||||
`Install-Module {{module}} -WhatIf`
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
# PSWindowsUpdate
|
||||
|
||||
> A PowerShell external module to manage Windows Update.
|
||||
> This tool provides multiple commands that all can only be run through PowerShell.
|
||||
> More information: <https://github.com/mgajda83/PSWindowsUpdate>.
|
||||
|
||||
- Install the module using `Install-Module`:
|
||||
|
||||
`Install-Module PSWindowsUpdate`
|
||||
|
||||
- List all commands available under the module:
|
||||
|
||||
`Get-Command -Module PSWindowsUpdate`
|
||||
Loading…
Reference in New Issue