Lydgate [EMAIL PROTECTED] writes:
One question: is it possible to map the higher mouse buttons 4, 5, etc.,
to back and forward to elinks running in xterm? I ask because elinks
seems very capable of interpreting 1 2 and 3. Would the solution be at
an elinks, xterm, or X (e.g. xbindkeys)
On Sun, Jan 28, 2007 at 12:18:52PM +0200, Kalle Olavi Niemitalo wrote:
This appears to be limitation in libxt-1.0.0/src/TMparse.c,
which supports only five mouse buttons. I don't know how difficult
that would be to fix.
After a little more searching, it appears not so difficult in terms of
Lydgate [EMAIL PROTECTED] writes:
But if I understand you correctly, even adding 6 and 7 in X would not be
enough, and buttons 6 and 7 would need to be defined in elinks?
Although I would think that something like: Btn6Up:U\n\ would bypass
that limitation (assuming default keybindings)
bzip2 Should be merged before 0.12. Needs review.
This ostensibly helps with bug 517.
epoll I don't think this should be merged.
If ELinks has to keep supporting select() too, I think the
maintenance burden outweighs any advantages epoll may have.
It may be
Here's a patch to use pwmd for form history. pwmd is a daemon that
listens on a local socket and waits for commands from clients to
manipulate data. The data is an encrypted XML file. The password to
open/save the file is gotten with gpg-agent. Read
src/formhist/README.pwmd for more info.
--
