geza-herman

### Observed behavior ccls reports invalid name for the operator in this code: ``` template struct Foo { operator Foo() { return 0; } }; ``` It produces this json...

Use flush-lines and keep-lines for g//d and v//d if possible

2

# Issue type - Enhancement request It would be awesome if evil handled some of the global commands specially. I use `g//d` and `v//d` a lot. But these are much...

When processing textDocument/documentSymbol, function scoped static variables may be better not to be reported

1

As I understand, the current textDocument/documentSymbol reports symbols, which can be useful in source code navigation, like imenu of emacs. So it doesn't report local variables, for example. But it...

I use `magit-blame-styles` setting which includes `margin-format`, and I noticed that blaming is very slow. I think that the issue is that when `magit-blame--make-overlays` calls `magit-blame--make-margin-overlays`, the point is not...

Completion should consider parts already in buffer

4

Consider this c++ snippet, with clangd server: ```c++ int main() { int uniqueVariableName = 0; uniqueVariable = 42; } ``` If I move the cursor to the "V" in "uniqueVariable",...

projectile-project-root's cache doesn't work as it supposed to work

1

## Expected behavior Cache should work properly ## Actual behavior Cache doesn't work properly, when the project root exists, but it is found by the non-first entry of `projectile-project-root-functions`. ##...

When doing worktree diff with a commit, apply/reverse doesn't work in the diff buffer

3

When doing a worktree diff with a commit (`d C-u w`), then neither `magit-apply` (`a`) nor `magit-reverse` (`v`) works in the resulting diff buffer on a hunk. Error messages are...

Idea: use (magit-get-upstream-ref) as ref commit

10

This is just an idea/suggestion. I see that magit-todos uses `(magit-main-branch)` to figure out (using `merge-base`) the revision to compare the HEAD against. How about using `(magit-get-upstream-ref)` instead? I'm suggesting...

If adding a new character at the filter prompt creates a string, which matches both the current and the next line in the dired buffer, the cursor will move down...

If live gutter is turned on (`git-gutter:update-interval` is non-nil), git-gutter will run `diff` after every keystroke, no matter whether it actually modified the buffer or not. Just moving the cursor...