Some markdown bold syntax is incorrectly displayed.

• 예를 들면 **alt-.**같은 경우
• ctrl-v **[Tab]**키를 누르거나

It should be modified as follows.

• 예를 들면 alt-. 같은 경우
• ctrl-v [Tab] 키를 누르거나

It would be good if the docs and --help output could mention that nvm install installs and uses the given Node version. I've probably wasted hours typing nvm install __ && nvm use __, - just discovered the second part has been unnecessary since this was fixed in 2014 :)

The man page says that the default for the gutter is bg+ (https://github.com/junegunn/fzf/blob/ff951341c993ed84ad65344e496e122ee3dddf67/man/man1/fzf.1#L258), but that does not appear to be the case with --color=16,bg+:18.

Related code might be: https://github.com/junegunn/fzf/blob/ff951341c993ed84ad65344e496e122ee3dddf67/src/tui/tui.go#L414

Specifying it explicitly works.

I can see th

Of the three examples here only hash correctly reports if an executable is in the PATH. type -p and command -v both report success on aliases, builtins, etc.

type -P (capital P) does correctly report if an executable is in the PATH.

Perhaps this section could

For bugs

• Rule Id (if any, e.g. SC1000):
  SC2012
• My shellcheck version (shellcheck --version or "online"):
  Any
• [*] The rule's wiki page does not already cover this (e.g. https://shellcheck.net/wiki/SC2012)

Specifically, SC2012 wiki should cover the case where ls is being used just to get the number of files matching a certain literal or glob pattern, rather than propagating th

shamelessly copy-pasted from exercism/bash/issues/171

tldp.org's shell scripting pages have very high Google page rank. They're detailed, extensive, and easy to read, and much of the information in there is useful. But the examples they use are very often riddled with code that runs between smelly and bug-prone to outright dead wrong and dangerous. An advanced bash scripter could maybe read

SED on osx does not have the "-i" option. This means that acme.sh fails to run properly. Users of acme.sh on osx must install and use gnu-sed.

Neither here nor powerline/fonts has any documentation of what codepoints are supposed to be provided with which glyphs by fonts. This makes it virtually impossible for font authors to add support.

Also, I’ve seen you use the PUA. Please register your codepoints with http://www.evertype.com/standards/csur/ so they don’t overlap with any other CSUR PUA assignments. (It’s easy, I got a couple ass

Solaris and Illumos use Bash as the default shell. However, currently bash-it does not work as expected on them.

This can be fixed as described, tested, and confirmed here.

Here's what I suggest:

• In install.sh, check for `$0S

Node version (or tell us if you're using electron or some other framework):

12.1.0

ShellJS version (the most recent version/Github branch you see the bug on):

0.8.3

Operating system:

Windows

Description of the bug:

sed is applied only once by line:
original archive:
import [COMPONENTNAME]Base from './[COMPONENTNAME]Base';
`const [COMPONENTNAME] = styled( [COMPONENTNAME]

Thanks a ton for any helpful feedback

I need help with getting best quality GIFs.

I am not used to CSS syntax so it would be amazing if you add a lot of example config.yml files. Also, try adding config.yml files for the GIFs you are displaying in your README.md. They look fantastic. I have spent hours trying to get perfect GIF but no luck.

I don't know what value to give for shadow

If yum isn't installed, for example, all snippets that start with yum should be hidden

1. this shouldn't impact startup time
2. if --show-all is used, there should be no filtering

Feature Request

Is your feature request related to a problem? Please describe.

There is no documentation on how to update the prompt when a new release comes out

Describe the solution you'd like

Ive tried using path and exact variants to no avail.

# /home/pbaum/.config/direnv/direnv.toml

[whitelist]
prefix = [ "/mnt/data/filesystem/home/x/Development/hosts" ]
prefix = [ "/home/x/Development/hosts" ]
exact = [ "/mnt/data/filesystem/home/x/Development/hosts/hc1/.envrc" ]
exact = [ "/home/x/Development/hosts/hc1/.envrc" ]

$ cd /home/x/Development/hosts/hc1
$ direnv

• The first example can have few more chained prompts (It shows the power of enquirer in a few seconds)
• Todo can be moved to the bottom & can be a section (Below Contribution section)
• The 'Related prompts' section can be moved below 'Example Usage'. After the gif, the code should be shown (It is correct for Input prompt)
• The example should be complete. It should match exac

If /home is a link, powerline-shell doesn't show ~ when in home directory. Instead it shows "....ssh/home/username/%"

I looked at this briefly and I think the issue is in segments/cwd.py.

This stackoverflow post outlines a different method of using namedParameters than the readme and seems to be correct. Readme could be updated to match.

https://stackoverflow.com/questions/6212219/passing-parameters-to-a-bash-function

When the hook script is run, $alias contains the real name of the certificate directory in $CERTDIR. This is useful to know when the domain is a wildcard like "*.my.com", but as far as I can tell it's not documented anywhere.