🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• xi18n
• run
• config
• help
• version
• doc

Description

According to the document of [CanActi

An alias for --decorations always so I can pipe the decorations when doing something like bat FILE | gview -. …but without the ^M's.

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

Topic

So sometimes when I am pushing to a branch and it has diverged from the remote, a little pop up shows up saying would you like to force push. Instinctively I press enter instead of escape which ends up force pushing

Your thoughts

I was hoping there would be an option to disable this specific behavior or just disable force pushing all throughout lazygit.

I feel like this m

I see a lot of fd users that seem to think that they need to add "{}" to all commands. Some users also seem to think that the closing semicolon (which needs to be escaped) \; is required:

fd … -x command "{}" \;

In reality, 90% of the --exec use cases can be written without the "{}" part (which fd adds, if it is ommitted) because the file entry often comes last. The semic

...this boilerplate is awesome, thank you for sharing it guys 👍

Currently, each argument to fx treated as an anonymous function. Here is an example:

fx 'groupBy("commit.author.name")' 'mapValues(size)' toPairs 'sortBy(1)' reverse 'take(10)' fromPairs

But this requires a lot of ' quotes. My idea is to split the argument by whitespaces . So next will be possible to write:

fx 'groupBy("commit.author.name") mapValues(size) toPairs so