Terminal is a serial computer interface for text entry and display. Instruction given to perform a task are called commands. Current computers (GUI based) uses terminal emulators such as Unix shell, BASH shell, command prompt.
Describe the bug you encountered:
If you use bat on C# source files (.cs, .xaml and others), a space appears in the first line. This is due to byte order mark (BOM)
Maybe reproduced for others files on Windows systems
https://en.wikipedia.org/wiki/Byte_order_mark#Byte_order_marks_by_encoding
Sample file with BOM:
[Program.cs.txt](https://github.com/sharkdp/bat/files/7420061/Program
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 ;)
Is your feature request related to a problem? Please describe.
In our company we have way too many branches remotely. Basically everybody creates new ones for every PR, and most of the time the branches don't get deleted afterwards.
That makes it very hard to check out a remote branch with lazygit, as I have to search for it. Need to know the exact PR number, ...
**Describe the solution
fd 8.2.1 on Windows 10
fd --changed-within "2021-10-09" | rg -i xxx
won't return an result.
fd --changed-within "2021-10-09" --exec rg -i xxx
returns the lines macthing xxx but the output is missing the filename where xxx is found.
Any idea how to get the filename where xxx is found?
rg -i xxx
alone returns machting lines including filename
Users installing Spaceship via homebrew don't know they have to add following lines to their .zshrc:
autoload -U promptinit; promptinit
prompt spaceship
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
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://