> For the complete documentation index, see [llms.txt](https://aptivi.gitbook.io/aptivi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aptivi.gitbook.io/aptivi/nitrocid-ks-v0.2.1-rolling-manual/advanced-and-power-users/inner-workings/inner-essentials/kernel-placeholders.md). # Kernel Placeholders Do you want to \?
Kernel placeholders are text variables for any piece of text that are replaced by different elements found within the kernel. They are parsed in several different areas of the kernel, the most famous example being the MOTD and the MAL messages. The probing takes place in the `PlaceParse.ProbePlaces()` function found within the `Nitrocid.Misc.Probers.Placeholder` namespace.
Types of text that support placeholders The following types of text use this function to parse the placeholders: * MOTD and MAL messages * Username prompt and their derivatives for each shell * Password prompt and their derivatives for each shell * Mail progress style * Mail progress style (single) * `echo` command * Manual page information style * GPG prompt style * Custom welcome banner * Remote debugger message format * RSS feed URL prompt style * Manual page contents * Download and upload progress for network transfers * Progress Clock screensaver's informational text variables
Types of placeholders and their values These are the placeholders and what possible values are going to replace them when being parsed: | Placeholder | Value | | --------------------------------- | ---------------------------------------------------------------------------------- | | `` | Current logged-in username | | `` | Current logged-in FTP username | | `` | Current logged-in FTP server address | | `` | Current FTP remote directory | | `` | Current FTP local directory | | `` | Current FTP local directory name | | `` | Current logged-in SFTP username | | `` | Current logged-in SFTP server address | | `` | Current SFTP remote directory | | `` | Current SFTP local directory | | `` | Current SFTP local directory name | | `` | Current logged-in mail address | | `` | Current logged-in mail server | | `` | Current mail directory | | `` | Host name of the kernel | | `` | Current directory | | `` | Current directory name | | `` | Short date | | `` | Long date | | `` | Short time | | `` | Long time | | `` | Today's date | | `
*** ## Custom placeholders You can make your own placeholders, too, with a simple one-line function that allows you to create your custom placeholders for commands and text that use the placeholders feature, with the dynamic content represented in text that you want. However, you need to register a placeholder before you can use it. Luckily, the registration is easy, unlike all the other components: {% code title="Somewhere in your mod code" lineNumbers="true" %} ```csharp PlaceParse.RegisterCustomPlaceholder("placeholder", (_) => "MyDynamicText"); ``` {% endcode %} {% hint style="info" %} Additionally, you can pass the first argument to the function that takes a string argument so that your placeholder behaves according to the argument provided. For example, colors are defined like this: ```csharp PlaceParse.RegisterCustomPlaceholder("colorfgtrue", (c) => new Color(c).VTSequenceForegroundTrueColor); ``` {% endhint %}
Verifying the placeholder registration You can verify that your placeholder is registered by calling the below function: {% code title="Verification" lineNumbers="true" %} ```csharp bool regged = PlaceParse.IsPlaceholderRegistered(""); // regged should be true ``` {% endcode %}
Unregistering a placeholder If you no longer want a custom placeholder, you can remove it using the `UnregisterCustomPlaceholder()` function using the same placeholder name. {% hint style="warning" %} Please note that you need to surround your placeholder name with the `<` and the `>` marks, except for `RegisterCustomPlaceholder()`, so that the prober can recognize your placeholder. It throws an exception if it's not surrounded. {% endhint %}