Terminal

Many systems don't link python to python3. Debian even maintains it's wrong for their packages to expect python to work:

NOTE: Debian testing (bullseye) has removed the "python" package and the '/usr/bin/python' symlink due to the deprecation of Python 2. No packaged scripts should depend on the existence of '/usr/bin/python': if they do, that is a bu

We are currently adding Hyper CLI path to user PATH in Windows registry: https://github.com/zeit/hyper/blob/262eb8ad9b7b9b15351f331765151538d67a09e2/app/utils/cli-install.js#L49-L91

A caveat is that environment variables are cached and users should open and validate "Edit environment variables for your account" dialog to force a cache refresh (or simply reboot their workstation).
![](https://

Describe the bug you encountered:

The options --map-syntax and --ignored-suffix cannot work together.

How to reproduce it:

1. Prepare a file foo.demo in YAML syntax:

   # file: foo.demo
   foo: "bar"

2. Use bat --map-syntax "*.demo:YAML" foo.demo can print it with YAML syntax highlighting:

   bat foo.demo \
       --map-syntax "

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

Currently, $LAZYGIT_NEW_DIR_FILE's path only gets updated on exit. It'd be a lot more useful if it was updated on the spot whenever directories are changed while running lazygit.

This would enable a new realm of functionality outside of lazygit, namely being able to quickly span a parallel session that points to lazygit's current directory for running miscellaneous commands.

The only other

(As discussed in #885,) the current benchmark suite has a few shortcomings.

The most obvious one is that there is no standardized dataset. Past ideas involved using large Git repositories (Linux, Chromium, Rust compiler), but these repositories change over time. We can not simply check out a certain state because the .git folder will still grow. It'

The problem

Users installing Spaceship via homebrew don't know they have to add following lines to their .zshrc:

autoload -U promptinit; promptinit
prompt spaceship

Describe the solution you'd like

Homebrew has to report a caveat with this information. Here's an example how they do that with nvm formula: https://github.com/Homebrew/homebrew-core/blob/23f6654873c