Nelo-T. Wallus

Well, that could be mentioned in the docs - if a user would like to use the functionality they'll have to add it. Complexity is a fair point, especially the...

That should be fairly easy: ``` viml function s:CurrentFirst(target) let curfile = expand('%') let errorsOnCurrent = filter(copy(target), 'bufname(v:val.bufnr) =~ ^' . curfile) let errorsOnOther = filter(copy(target), 'bufname(v:val.bufnr) !~ ^' ....

The result looks a bit different, but it works quite well in both non-qf as well as qf-context. For now I've named the commands `:Qf{C,L}sort`, like the other global commands...

Mhm. Two ways we could go about this: 1. Additional logic in `qf#GetEntryPath` to waltz up the entries until it found a path. That would work but then we'll need...

Afterthought - the best thing would be a wrapper `qf#GetEntryPathRecursive`(o.s.) around `qf#GetEntryPath`, which does go until the first available and returns nil if none was found.

Imho the easiest way would be to use a simple annotation script that allows to add text/arrows/... to an image and then save it as a new version of the...

@devilx Personally I'd step back from that idea. In the view from an API dev this would need three additional steps: Create a new version of the note through updating,...

@devilx > 1) The way annotations are being saved: > > I my opinion, we should never ever modify a user-uploaded document/image/whatever. Therefor I pledge for modifying not the source...

@devilx I see the problem you mean now - but that could be solved by directly linking a `noteversion` to an `attachmentversion`. But still that would use up a lot...

Seconded, I've just hit this limitation as well.