Most urgent features?

[cmaughan]

I'm keen to push Zep forward. I'd like to know what people need from it?

I'm still working on a live coding tool part-time, and some of what I do is directed towards that, but I'm happy to take suggestions for the most urgent fixes/features that people need?

[totalgee]

For me, there are some Vim mappings that would be very useful. One thing in particular, I was thinking about adding the % at some point, to jump to the matching parentheses/braces/brackets -- very helpful to orient yourself -- and ci) ("change in" parentheses and its friends ci", ci] etc.), as mentioned in #32. I've not had time to look at these, I imagine they should be relatively easy for you to add (you must already have "find matching paren" code in there, for the matching brace/bracket/paren colour highlighting).

Also, a way to map an external way to scroll the buffer, for example so I can map the "two-finger touchpad slide" (or mousewheel) behaviour to scroll the buffer up and down quickly. (Maybe this is already possible?)

[cmaughan]

% and ci are high on my list too. I forget how the scroll buffer works; I think there is line offset for each window, so it shouldn't be hard to modify that.

[cmaughan]

... the window.cpp has an m_textOffsetPx value which is the offset in pixels from the start of the document. If you have the VScroller visible, it modifies the scroll location like this:

           auto pScroller = dynamic_cast<Scroller*>(payload->pComponent);
           m_textOffsetPx = pScroller->vScrollPosition * m_textSizePx.y;
           UpdateVisibleLineRange();
           EnsureCursorVisible();
           DisableToolTipTillMove();

... because the scroller works in document lines. I think I made it a pixel offset originally so I could do a nice smooth scroll; I just never got around to it.

Adding a command that scrolls in the same way would be simple enough.

[cmaughan]

Here is support for %:
8a1e153

[cmaughan]

I have just pushed a first go at implementing ci. It is not straightforward, but the implementation covers what I usually use, and seems robust. Needs unit tests.

[totalgee]

I just tested it out, so far seems to work as expected. There is a difference from Vim, but not one that matters to me. In case you're curious, try this (| is the cursor):

f(x,|
y)

If you put the cursor somewhere after the opening paren on the first line and do ci) (or ci(), you get something that spans multiple lines.

f(
     |
 )

Vim doesn't do this, it brings up the previous closing paren to the first line.

f(|)

Anyhow, I'm not saying you should "fix" it; it doesn't really matter to me, the Zep behaviour is fine (just a bit different from Vim). It does work the same as Vim when the open and close are on the same line (and even when there are other nested parens).

Nice, thanks!

[cmaughan]

I'm not even sure what the rule is there; I played a bit and can't figure it out (the docs are lean on this topic too). I could look in the neovim sources, and I may do out of curiosity, but I agree it isn't a big deal. Much of Zep is pragmatic around the features I actually use day to day; though I do try to follow the same behaviour when I can.