Re: Alternative window managers for Apple X11?
Re: Alternative window managers for Apple X11?
- Subject: Re: Alternative window managers for Apple X11?
- From: Randy Ford <email@hidden>
- Date: Sat, 29 Mar 2003 02:46:13 -0600
On Friday, March 28, 2003, at 10:29 PM, Brian Kurotsuchi wrote:
I'd like Cmd-V to paste actually. Yes, I've read the FAQ so let's not
comment
on that. Perhaps I should upgrade to a 3 button mouse.
You can configure xterm to paste using Cmd-V. Just add the top and
bottom line below to your ~/.Xresources or ~/.Xdefaults. (.Xresources,
if used, will override .Xdefaults) I've included all of my xterm
translations since they somewhat mimic what Terminal.app does.
XTerm*VT100.translations: #override\
<Key>Prior: scroll-back(1,pages) \n\
<Key>Next: scroll-forw(1,pages)\n\
Meta <Key> K: send-signal(int) clear-saved-lines()
\n\
Meta <KeyPress> P: print() \n\
Meta <KeyPress> minus: smaller-vt-font() \n\
Meta <KeyPress> KP_Subtract: smaller-vt-font() \n\
Meta <KeyPress> plus: larger-vt-font() \n\
Meta <KeyPress> KP_Add: larger-vt-font() \n\
Meta <KeyPress> M: iconify() \n\
Meta <KeyPress> V: insert-selection(PRIMARY,
CUT_BUFFER0) \n\
If I had a three-button mouse, could I remap middle button to be
paste? I
spend all my (other) time in X11, so that's what I'm used to and I
like it.
By default, middle button is paste on a three button mouse.
The curses bug... It's inappropriate to fix it with the termcap
database,
that data is correct. Why would I alter a termcap on a working system
(say
Linux or Solaris)? I could see copying and modifying it to workaround
a bug.
It usually makes more sense to add an entry to the existing terminfo
database than to copy and modify it. If nobody sets their TERM to
xterm-fixed, then they won't be affected. That's why it's built like
it is.
I haven't used HP much since 1996, but as of then HP's terminfo entry
for xterm did not support arrow keys. On each machine I used much, I
copied the entry for xterm to xterm-keys and deleted the extra
definition in HP's terminfo that caused the problem. Then I could set
TERM=xterm-keys and the arrow keys would work. I had to do this from
HP-UX 9 through 11. The bug report for it had been open several
versions before 9. If I didn't have root access, I built my own limited
terminfo database with just entries I needed, but it's better to add an
entry to the system one to make it available to all users.
There are a lot of other reasons to add to the terminfo library. If
you start the xterm with the -hf parameter, it will use different
escape codes for the function keys. To work correctly with curses
apps, it would need a modified terminfo entry. (I haven't
checked--there may be one shipped.) The different escape codes may be
needed to work with some non-curses programs. HP used to have several
that caused problems. They had been hard-coded to work on HP
terminals. Adding an "xterm-hp" entry to the system database was the
appropriate thing to do.
Anyway, I don't think that will fix it.
The problem is that when I'm in a ssh session, running BitchX (which
is curses
intensive) and the ssh connection close unexpectedly, the xterm gets
stuck
scrolling the last line only. So no scrolling occurs after that
point. I can
issue commands and see results printed sequentially, but it's all done
on the
last line of the terminal.
I don't see this as a bug in either curses or xterm. Curses sets up
the terminal how it needs it, and resets it when it is done. If curses
loses the connection in the middle of running, there isn't any way for
it to reset the terminal. Xterm doesn't have any way of knowing that
curses is no longer the program writing to the screen, so it can't
properly reset itself.
I've had this problem in the past and found a solution, but I forget
what it was. Have you tried the xterm's soft and hard resets to see it
they fix the problem. The are on the control-middle button menu. I
believe that you can get to it on a one-button mouse by pressing
control-option-mouse_button. I may have written a script or program to
reset the terminal. I don't remember right now and I don't have BitchX
installed.
If one of the resets is appropriate, you could assign it to a key, like
the cmd-V above. Otherwise, it may take some investigation to see
which commands need to be given to the xterm to reset it properly.
Then you can assign it to a key or make a script that will reset it
appropriately when ssh finishes.
randy.
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.