I'm using elinks as a frontend to an embedded app.
I've added a whole bunch of code to viewer/text/form.c to handle our
special fields and to calculate the values in the form.
All of that is working fine, except that there are several fields that
need to be recalculated when the form loads.
I
Here is the patch.
Kalle, Jonas, could apply them (key motion patches) to the mainstream ELinks?
move-link-down-line, move-link-prev-line, etc.:
Change mode to NAVIGATE_LINKWISE to preserve the link position when
going back.
---
commit 14b37d0362f9963cb2803d08d2c3e6e84574cdbe
tree
This bug has to be fixed properly, otherwise, this is really interfering with
the default elinks behaviour. If we can fix this cursor geometry issue, I will
surely ask them to include it in the mainstream.
Thanks a lot.
On Tue, Aug 14, 2007 at 07:59:14PM +0200, Witold Filipczyk wrote:
Here
Woohoo. it works properly now. You can post this into the elinks list and I
will ask them to include it.
Thanks again.
On Tue, Aug 14, 2007 at 11:48:42PM +0530, Ligesh wrote:
This bug has to be fixed properly, otherwise, this is really interfering
with the default elinks behaviour. If
Sorry, I didn't realize that we were in the elinks mailing list. Anyway, it
seems, the patch now works fine, and it doesn't modify elinks' earlier
behaviour either, making the new key motion a really non-intrusive feature.
I would like to know if the maintainers can comment on this. Also, it
