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 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 character would be visible.

What can be done:

- The cursor can be made to blink.  Then the character will at
  least be visible part of the time.  This can be done via X
  resources, the xterm command line, or the vtMenu.  ELinks could
  also send a control sequence to enable blinking, but we must
  not make that change, because if blinking has been enabled in
  some other way, then the control sequence would actually
  disable it.

- The colour of the cursor can be changed.  I have an X resource
  "UXTerm.VT100.cursorColor: #f66", which makes even white text
  partially readable.  ELinks could also change the colour with
  a control sequence, but there doesn't seem to be a way to ask
  xterm what the colour was originally, so people would then
  complain that ELinks does not restore it.

- Terminfo capabilities civis, cnorm, cvvis control the
  visibility of the cursor.  The civis string makes the cursor
  invisible so ELinks should not use that in input fields.  The
  only difference between cnorm (normal) and cvvis (very visible)
  seems to be that cvvis disables blinking.  ELinks does not send
  any of these strings.

All in all, I don't see how we could change ELinks to make the
character behind the cursor more visible, without hurting the
visibility for some other xterm settings.

Attachment: pgpnhWDXxHqQx.pgp
Description: PGP signature

Reply via email to