Jesse Duffield
Jesse Duffield
Hey @jwhitley are you still interested in continuing with this PR?
Nice work @jwhitley
Agreed that this should be a thing. I'm not sure that termbox (one of our dependencies) supports those keys, but I'm assuming there must be some way to read them....
I worry @duckbrain that if we only allow a subset of the config to be used that: 1) some users will be annoyed at the constraint 2) some configs could...
> I think the best option for the security concern is to filter out all those config options that could be abused (all that can be set to a command,...
Another thing that just came to mind on the topic of excluding keys vs requiring user confirmation: vscode's incessant trust checks can be annoying but the 99% typical case is...
I'm still uneasy about it. Putting everything on the table: Restricted config: * as maintainers, it's extra ongoing work to maintain a list of excluded config keys. We added one...
I also wasn't aware of that option. I stash staged changes all the time so that's going to be useful. 2.35.0 was in 2022 and I don't want to force...
@stefanhaller I meant to say much older than 2022. Some users seem to very slowly update their git versions (e.g. because they're on OS's with old git versions and because...
> So, In summary, for users with git version older than 2.35.9 the flow remains the same, and for users of this version an higher the git stash push --staged...