There's nothing built in, exactly, but there are two ways to get at the scrollback text.
You can configure the XTerm.vt100.on4Clicks
and XTerm.vt100.on5Clicks
resources (or from on1Clicks
onwards, for that matter) to choose to copy the whole scrollback to the X11 PRIMARY selection. For example, to copy the whole scrollback on a quadruple click, put this line in your .Xresources
:
XTerm.vt100.on4Clicks: all
You'll then have to arrange your own method for bringing up some way to search the content of the X selection, such as opening an editor or a pager with a window manager binding.
You can call the print-everything
action to send the whole scrollback to a program determined by the XTerm.vt100.printerCommand
resource. For example, to open the scrollback in less (running in a new xterm) when you press Ctrl+/, put these lines in your .Xresources
:
XTerm.vt100.printerCommand: xterm -e sh -c 'less <&3' 3<&0
XTerm.vt100.translations: #override Ctrl ~Meta ~Shift <Key>slash: print-everything()
At the time the sshd process on the remote computer forks to run /usr/bin/xterm there are very few environment variable set. In fact the LANG variable is not set. Hence the xterm process does not know that it should display characters in UTF-8. It falls back to xterms defaults. Whatever that might be.
However, the subshell running inside the xterm runs all setup scripts and alike.
Including setting the LANG environment variable.
One needs to understand the difference between the remote xterm process and the shell process running inside of xterm.
The solution is to run the remote xterm process like this:
/usr/bin/env LANG=en_US.UTF-8 /usr/bin/xterm
env(1) is a utility to run a program in a modified environment.
Setting LANG will make the remote xterm display UTF-8 characters properly.
Eskil...
:-)
P.s: Reading the xterm manual page I also found an easier way to achieve this:
xterm -en en_US.UTF-8
P.P.s: I do not think setting resources in ~/.Xresources will take effect unless you merge them in with xrdb. The xterm process on the Linux computer will query the X server running on your windows computer. At the time where xterm starts it is very unlikely that your X-Win32 server has the xterm* resources set. But you might be able to set resources in X-Win32 if it supports that.
Best Answer
Use editres
You cannot save what you configured through XTerm's own menu. BUT, XTerm is a well behaved X application and as such it supports the editres protocol. So what you should do is:
The save file can now appended to your .Xdefaults.
Example of what I got by this procedure:
Beware, some options take effects only when some other option changes. For instance: rightScrollBar is looked up by Xterm only when scrollBar changed from false to true.
But all in all you should have the possibility to do the configuration you want.
Links: