Re: Semantics of text virtual console vs. xterm

On 2008-02-24, phil-news-nospam@xxxxxxxx <phil-news-nospam@xxxxxxxx> wrote:

The second issue is mouse mechanics. This one looks to be more troubling.
In text mode, the mouse position at any moment is clear and unambiguous.
This is because it uses a full block inversion over the character cell to
show the mouse position. In X with xterm (and other applications), that
position is uncertain. The mouse symbol over text is the "I bar". There
are multiple pixel level positions the mouse can be moved to. But not all
of them behave as the mouse being over the character that the "I bar" will
appear to be over. For example, when highlighting text, unless you move
the mouse sufficiently far enough to the LEFT SIDE of the first character
to be highlighted, it will miss that character and start highlighting on
the character to the right. The same issue in reverse exists at the ending
character. I need to get this fixed. If the cause of this is in the code
of the application, or in a library it uses, maybe it is fixable in the
application. I have seen some applications that change mouse behaviour
around, so there is hope. But I'm not about to go trying to figure out the
parts of those applications that change mouse behaviour apart from all the
other stuff those applications do (writing code is easy ... reading other
people's code is hard).

In most GUI software, when you drag the cursor, the starting and ending
positions are considered to be between characters. Imagine that you are
physically cutting paper with the cursor as the blade. If you don't like
that you can use a text-mode editor such as nano or vim, and ignore the
mouse cursor unless you want to paste from one window to another.

Another aspect of the mouse issue is when doing things like double clicking
and triple clicking, just what gets highlighted is different. Highlighting
a word by double clicking highlights a full file path in text mode, but not
in xterm. That appears to be an issue of what characters are allowed to
stop the span of the highlight. Changing that, once it is found where they
are, should, I would think, be simple. But I haven't found where (I have
only looked in the xterm source code).

Double clicking selects a "word", defined as a series of characters of
the same class. See "Character Classes" in the xterm man page.

The third issue is to find a way to rapidly switch between different screens
of text. In text mode, the traditional virtual console involves Alt+FX,
where FX is one of the "F" function keys on the top row of the keyboard.
I have, through keyboard mapping, expanded that to so that Alt+X, where X
is either one of the function keys or one of just about any other key on
the main part of the keyboard (including space and ESC). I have 63 such
mappings to virtual consoles, and use them all. Alt+F10, Alt+F11, and
Alt+F12 are each going to X Windows (I run three instances of X at the
same time). The rest go to one of 60 different virtual consoles, all of
which are logged in and used. When I press Alt+X the switch is very rapid.
Some people have suggested using screen, but it is awkward to use for this
kind of rapid switching (I sometimes switch back and forth a few times a
second). I would thus want to have some kind of means to do such rapid
keyboard based switching while in X. That would not be switching between
the different instances of X (that's way too slow, anyway). It could be
switching between different windows of xterm, or subwindows within xterm,
or different virtual desktops within the same instance of X. Whichever is
the fastest is the way to go. But how to set that up? Maybe it needs a
new window manager? Or is one already available that can do that.

You can use screen, which also works in console mode, or you can use
the alt-tab key or a terminal with multiple tabs.

Non-specific advice won't be helpful. Does anyone have any specific advice?

.

Relevant Pages

  • Semantics of text virtual console vs. xterm
    ... I use both X Windows as well as the text virtual console. ... In xterm, the scrolling is still not as fast as in text mode, but at least ... This is because it uses a full block inversion over the character cell to ... keyboard based switching while in X. ...
    (comp.os.linux.x)
  • Re: xterm double-click to select words like "cups-bsd", "/var/log"
    ... > If you want to understand what's going on, read the CHARACTER CLASSES ... > section of the xterm man page. ... The above -cc adds each character to the character class 48 ... mentioned that now one can never decide what infinite color scheme is best. ...
    (Debian-User)
  • Re: Backspaces converted to ^? -- want to get rid of ^? -_-...
    ... su'ed in as root using vim, or the SuSe box at work when I VNC into ... behavior so pressing backspace erases a character, ... The attached XTerm file put in $HOME/XTerm will get xterms to send ctrl-h ... Shift: MoveThumbNotifyThumb() \n\ ...
    (freebsd-questions)
  • Re: how to display character from 128-159 range
    ... I went through net and found that -k8 option is added in xterm for ... value of a character getting displayed to 130 and see the output and i ... Next thing to consider for me was ncurses, ... xterm won't try to display that character if you remove the -k8 option. ...
    (comp.unix.programmer)
  • Re: Backspaces converted to ^? -- want to get rid of ^? -_-...
    ... su'ed in as root using vim, or the SuSe box at work when I VNC into ... behavior so pressing backspace erases a character, ... The attached XTerm file put in $HOME/XTerm will get xterms to send ctrl-h ... keyboard configuration that permits setting the backspace key to send ...
    (freebsd-questions)