Perhaps the most useful command: EOF. No need to use "exit" / "logout" ever again, works in anything using deadline, any shell, and things like cat when using it to create files cat - > file.

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

• Category
  • fzf binary
  • Key bindings
• Shell
  • bash
  • zsh
  • fish

Eg, I would like to have the second item highlighted on startup.

It would be nice to call fzf as in:

echo -e 'abc\ndef' | fzf --bind 'start:down'

For reference, this is the tool I'm develop

• 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

I can't check shellcheck.net because it requires JavaScript.

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

#!/bin/sh
set +x

From https://github.com/kennethreitz/autoenv :

Note: you should probably use direnv instead. Simply put, it is higher quality software. But, autoenv is still great, too. Maybe try both? :)

When singular items are missing we say "does not exist" or doesn't exist".
When singular items are present we say "does exist" or "exists".
Yes, English can be difficult.
https://github.com/acmesh-official/acme.sh/search?q=%22doesn%27t+exists%22&unscoped_q=%22doesn%27t+exists%22
Text says "doesn't exists".

Ref also : https://github.com/acmesh-official/acme.sh/search?q=%22does+not+exists%22&

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

Description

Uncommenting info "Disk" disk results in a partially correct output: Disk (81%): 495G / Fles/Git (97G%). What is Fles/Git (97G%)? I'm guessing this might be my external SSD.

Also uncommenting info "Font" font info "Users" users info "Song" song [[ "$player" ]] && prin "Music Player" "$player" results in no display of this info.

• Does this issue still occ

Feature Request

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

I realized that starship has no documentation in Portuguese (Brazil), so I would like to contribute with project and add pt_BR translation.

Describe the solution you'd like

Documentation in Portuguese (Brazil).

Contributing

If you are interested in contributing, please take a look

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

# build default.nix
nix-build -E 'with import <nixpkgs> {} ; callPackage ./default.nix {}'

this line things of nixpkgs> as a variable, but it actually should stay `.

Describe the solution you'd like

Best we to escapt <nixpkgs> some how.

Describe alternatives you've considered

currentl

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".

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

On the default settings, each segment is padded on either end by a space " ". This adds visual appeal and clarity. On the other hand, it adds two characters per segment. It'd be nice to customize this option for users who want powerline to span fewer characters.

Would a left_pad and right_pad option be useful?

(PS. This project is awesome. Thanks!)

if I understood it corretly from README.MD, we can install like this:

$ git clone https://github.com/donnemartin/dev-setup.git && cd dev-setup
$ ./.dots bootstrap osxprep brew osx

and later when we need datastores, we run

$ cd ~/dev-setup
$ ./.dots datastores

I understand that bootstrap copies the dot files to the home directory, such as .bash_profile and .exports.
but

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.