[zathura] Confusing keybinding: search forward instead of search next

[Dan Rosén]

Dear developers of Zathura,

It took me some digging into the source code to understand that I should
bind `search forward' instead of `search next' in zathurarc, to, well,
search to the next match.

I do think that this is a problem: In the man page for zathurarc, there is
just a long list of possible arguments to all shortcut functions, but only
a few of them actually work to each specific function. It would be very
helpful to know which arguments can be passed to which function.

This would help in situations like this, when it is not obvious if `search'
should take `forward' and `backward' as arguments, rather than `previous'
and `next'.

Best,
Dan Ros?n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pwmt.org/archive/zathura/attachments/20140218/c0b57deb/attachment.html>

[Sebastian Ramacher]

Post by Dan Rosén
Dear developers of Zathura,
It took me some digging into the source code to understand that I should
bind `search forward' instead of `search next' in zathurarc, to, well,
search to the next match.
I do think that this is a problem: In the man page for zathurarc, there is
just a long list of possible arguments to all shortcut functions, but only
a few of them actually work to each specific function. It would be very
helpful to know which arguments can be passed to which function.
This would help in situations like this, when it is not obvious if `search'
should take `forward' and `backward' as arguments, rather than `previous'
and `next'.

Yes, indeed. We should document arguments to shortcut functions better.
I will start working on this.

Regards

[Sebastian Ramacher]

Post by Sebastian Ramacher

Post by Dan Rosén
Dear developers of Zathura,
It took me some digging into the source code to understand that I should
bind `search forward' instead of `search next' in zathurarc, to, well,
search to the next match.
I do think that this is a problem: In the man page for zathurarc, there is
just a long list of possible arguments to all shortcut functions, but only
a few of them actually work to each specific function. It would be very
helpful to know which arguments can be passed to which function.
This would help in situations like this, when it is not obvious if `search'
should take `forward' and `backward' as arguments, rather than `previous'
and `next'.

Yes, indeed. We should document arguments to shortcut functions better.
I will start working on this.

Done in ab9f551 for some shortcut functions. There are many more taking
arguments, but I don't feel like documenting them right now.

Regards