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 :)

• I have read through the manual page (man fzf)
• I have the latest version of fzf
• I have searched through the existing issues

Info

• OS
  • Linux
  • Mac OS X
  • Windows
  • Etc.
• Shell
  • bash
  • zsh
  • fi

• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

I'm trying to include highlighting of the conda virtualenv in the .bash_prompt file, but I'm not very familiar with bash and haven't had much success in targeting it. Say this is the desired result for some virtualenv named temp;

username at host in ~/dotfiles on master [+] < temp >

Currently, the conda virtualenv name is prepended to the command prompt. I believe that i

For new checks and feature suggestions

• shellcheck.net (i.e. the latest commit) currently gives no useful warnings about this
• I searched through https://github.com/koalaman/shellcheck/issues and didn't find anything related

Here's a snippet or screenshot that shows the problem:

#!/bin/bash
if [ "$(find "$i" -type l | wc -l)" -eq 0 ]; then

Her

I followed the guide on this page to install a certificate, and the entire process works until the last step, basically:

[Fri Nov 22 13:06:40 EST 2019] Installing cert to:/usr/syno/etc/certificate/_archive/xxxxxx/cert.pem
./acme.sh: line 5218: /usr/syno/etc/certificate/_archive/xxxxxx/cert.pem: Permission denied

What's confu

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

Small omission in the guide: it is implied in step 9 that a {} literal should be parsed as a hash-map in the reader, but this is never explicitly stated earlier on. The sentence in question is: "This is basically the functional form of the {} reader literal syntax".

Contributing

If you are interested in contributing, please take a look at our Crowdin page.

📝 Visit translate.starship.rs to contribute!

Any localization contributions and reviews would be greatly appreciated! 🙏

If you are interested in leading the Spanish translation initiative, taking responsibility of reviewing and ma

In #303, @zimbatm says he wants improved code coverage before accepting some patches. I'm opening this issue so that code coverage can be tracked independently.

• 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

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

I cannot see any docs on how the OCSP feature is suppose to work. Please document it. Thanks.

I am wondering if autoenv could not be used in complex CI environments where we have multiple steps and where we need to save/restore status between different steps.

We are currently doing appending variables inside some env_jenkins.properties files and on some some steps (builders) and on others we do source env_jenkins.properties in order to load them.

If autoenv would work also for