if (BashIsBashingYou) {
return "Sorry to hear that. Here's a tool to make you feel better!"
}
else if (2020IsBashingYou) {
return "Take a look at this tool anyway, at least for the doodles!"
}
else {
return "Hmmm. I sense an alien among us ..."
}
Jokes aside, this tool is designed to make it a bit
easier for you to test out values of prompts in bash,
without having to set them as your prompt.
Why can this be a problem? If you screw up your prompt
enough, the terminal can become unusable, so you'll have
to open up a new session and try again. This stopping and
starting can get really frustrating when you're testing
different prompts out.
Enter in
any values you want in the "Optional parameters" section
and the value of the prompt you'd like to test out,
and you should get your result!
Here are a few different sample inputs and outputs
to try!
\[\e[1;32m\]KR$ \[\e[m\]
\u@\w
, with username and working directory in placeholder
sam@~/toad
\[\e[1;34m\]\H \T$ \[\e[m\]
, with hostname in placeholder
.bashrc
\[
and \]
. Why?
When you test the
prompt, the issue will not be immediately
apparent, either with this tool or in the shell.
Here's a more detailed explanation on
my website.
Take a look at the the official manual!
The bell character is not a printed character;
it is often interpreted as
a sound instead. In this app, you can choose
how you want it to be represented, as either a string
(BEL
), or as a sound.
\D
key is currently not supported
with strftime
. Sorry =(
$HOME
,
mainly because pretty much anything can be a variable.
Therefore, certain errors surrounding the $
aren't interpreted as the shell would interpret them.
For example, $egg
wouldn't be interpreted as
anything if egg
isn't a variable. In this tool,
this is rendered as just $egg
.
Eat some apple/pumpkin pie =) Happy October (which is basically Halloween, right?)!