On 2014-08-29 08:16:42 +0200, Moritz Mühlenhoff wrote:
On Sun, Jan 20, 2008 at 06:57:09PM +0200, Kalle Olavi Niemitalo wrote:
We should eventually make ELinks use terminfo, but that has not
yet been done:
ELinks bug 96 - Use terminfo to determine various escape sequences
We should eventually make ELinks use terminfo, but that has not
yet been done:
ELinks bug 96 - Use terminfo to determine various escape sequences
http://bugzilla.elinks.cz/show_bug.cgi?id=96
However, I don't think terminfo would actually help prevent the
cursor from obscuring the character
On 2008-01-20 18:57:09 +0200, Kalle Olavi Niemitalo wrote:
However, I don't think terminfo would actually help prevent the
cursor from obscuring the character behind it. In general, xterm
does not appear to allow programs such as ELinks to adjust the
cursor so that both the cursor and the
# Bcc: control
tags 403206 + upstream wontfix
thanks
On 06/12/20 10:56 +0100, Jonas Fonseca said ...
Vincent Lefevre [EMAIL PROTECTED] wrote Sat, Dec 16, 2006:
OK, I now understand. It would be a good idea to support it.
Another solution is to write a wrapper script that would build
a
severity 403206 minor
thanks
If some character is hidden, this is really a bug; I didn't thought
about it earlier, but making the cursor invisible would be a very
bad solution in text forms anyway. So, forget about this solution
concerning this bug.
This may be an xterm bug after all. When I run
retitle 403206 elinks: character below the cursor is hidden
thanks
Bug titles should contain the bug, not a particular way to fix it...
Using termcap/terminfo wouldn't solve the problem in forms since the
cursor needs to be visible. I've improved the title to include the
problem with forms (which
Vincent Lefevre [EMAIL PROTECTED] wrote Sat, Dec 16, 2006:
On 2006-12-16 11:19:51 +0100, Jonas Fonseca wrote:
ELinks only has a handful[1] of built-in terminal configurations.
Perhaps common ones should be added, like xterm-xfree86 and
xterm-vt220 (both used by the xterm provided by Debian,
Vincent Lefevre [EMAIL PROTECTED] wrote Sat, Dec 16, 2006:
BTW, I wonder why color is disabled by default in xterm-xfree86!
The other applications have no problem with it.
ELinks only has a handful[1] of built-in terminal configurations.
I have no such problem in the shell, for instance.
On 2006-12-16 11:19:51 +0100, Jonas Fonseca wrote:
Vincent Lefevre [EMAIL PROTECTED] wrote Sat, Dec 16, 2006:
BTW, I wonder why color is disabled by default in xterm-xfree86!
The other applications have no problem with it.
ELinks only has a handful[1] of built-in terminal configurations.
Package: elinks
Version: 0.11.1-1.2
Severity: normal
I tested elinks in an xterm with a black background (and white text).
When the xterm has the focus, the first character of the currently
selected link is not visible: I can just see the white cursor instead
of this character (in reversed
Vincent Lefevre [EMAIL PROTECTED] wrote Fri, Dec 15, 2006:
Package: elinks
Version: 0.11.1-1.2
Severity: normal
I tested elinks in an xterm with a black background (and white text).
When the xterm has the focus, the first character of the currently
selected link is not visible: I can just
On 2006-12-15 17:13:32 +0100, Jonas Fonseca wrote:
Vincent Lefevre [EMAIL PROTECTED] wrote Fri, Dec 15, 2006:
I tested elinks in an xterm with a black background (and white text).
When the xterm has the focus, the first character of the currently
selected link is not visible: I can just see
12 matches
Mail list logo
