{"componentChunkName":"component---src-templates-post-template-js","path":"/powershell-custom-prompt-en","result":{"data":{"markdownRemark":{"id":"e5e0a84a-6c4e-5c78-babf-80d0d147757a","html":"
\n

This page has been machine-translated from the original page.

\n
\n

Customize the PowerShell prompt display

\n

Let’s jump right in and start learning PowerShell.

\n

First, let’s simplify the prompt display.
\nBy default, it is probably shown as PS [current directory], like this.

\n
PS C:\\Users\\yuki>
\n

Here, you can remove the current-directory display by entering the following command.

\n
PS C:\\Users\\yuki> function Prompt { \"PS > \" }\nPS >
\n

To restore the original state, enter the following.

\n
PS > function prompt { \"PS \" + $(Get-Location) + \"> \" }
\n

This returns the prompt to its original form.

\n

Next, let’s customize the display using another command.

\n

If you enter the following command, the output of $(echo \"test\") will be shown in the prompt.

\n
PS C:\\Users\\yuki> function prompt { \"PS \" + $(echo \"test\") + \"> \" }\nPS test>
\n

Using this approach, you can freely change how the PowerShell prompt is displayed.

\n

By the way, Get-Location, which we used to display the current directory, has two other aliases for the same command.

\n

They are gl and pwd.

\n

So even if you enter the following, the current directory will still be displayed in the prompt just as when using Get-Location.

\n
PS C:\\Users\\yuki> function prompt {\n>> \"PS \" + $(pwd) + \"> \" }\n\nPS C:\\Users\\yuki> function prompt {\n>> \"PS \" + $(gl) + \"> \" }\n\nPS C:\\Users\\yuki>
\n

When it comes to these aliases, a natural question is whether you really need to know all of them.
\nIf you are the only one using them, honestly, knowing just one is probably enough.

\n

However, if you are going to use PowerShell in the security field, it seems you need to know all of the aliases.

\n

The idea is that even if you do not use a particular alias yourself, an attacker might use it, so understanding them is important if you want to recognize an attacker’s intent.

\n

For more details, I referred to the following article.

\n

Learning the basics of PowerShell at the Yamato Security Study Group · Akaki I/O

\n

Summary

\n

This time, I covered how to change the prompt display and touched on aliases.

\n

PowerShell has become open source, and because it is a powerful shell and scripting environment that works not only on Windows but also on Linux and macOS, I want to keep learning more and more about it in the future.

","fields":{"slug":"/powershell-custom-prompt-en","tagSlugs":["/tag/power-shell-en/","/tag/windows-en/","/tag/english/"]},"frontmatter":{"date":"2020-06-30","description":"This article summarizes how to customize the PowerShell prompt display.","tags":["PowerShell (en)","Windows (en)","English"],"title":"How to freely customize the PowerShell prompt display","socialImage":{"publicURL":"/static/dc4d8b7f8795f3c3d3489d9957d155f2/no-image.png"}}}},"pageContext":{"slug":"/powershell-custom-prompt-en"}},"staticQueryHashes":["251939775","401334301","825871152"]}