* James Richardson ([EMAIL PROTECTED]) wrote:
> >
> I don't know why it is the default, and I don't really know a lot of
> people who prefer the behavior, although presumable the guy who made it
> the default liked it. ;)
I can live with it even being default, though I really cannot imagine
it be
cothrige wrote:
> * James Richardson ([EMAIL PROTECTED]) wrote:
> > >
> > I am not sure about rxvt, but with xterm you can set the titeInhibit
> > resource to true (e.g. add a line like XTerm*titeInhibit: True to your
> > .Xresources file), not sure it it works with rxvt. You may have to mess
> >
* James Richardson ([EMAIL PROTECTED]) wrote:
> >
> I am not sure about rxvt, but with xterm you can set the titeInhibit
> resource to true (e.g. add a line like XTerm*titeInhibit: True to your
> .Xresources file), not sure it it works with rxvt. You may have to mess
> with the terminfo database a
cothrige wrote:
> In another thread in which I was seeking a better way to handle
> unicode in my terminals (my current preference mrxvt does not support
> it) rxvt-unicode was suggested as a possible alternative. However,
> now I am dealing with an even more aggravating situation, and that is
> t
On 10/31/06, cothrige <[EMAIL PROTECTED]> wrote:
In another thread in which I was seeking a better way to handle
unicode in my terminals (my current preference mrxvt does not support
it) rxvt-unicode was suggested as a possible alternative.
xterm from Sarge (xterm-4.3.0.dfsg.1-14sarge1) with $T
In another thread in which I was seeking a better way to handle
unicode in my terminals (my current preference mrxvt does not support
it) rxvt-unicode was suggested as a possible alternative. However,
now I am dealing with an even more aggravating situation, and that is
the alternate screen where
6 matches
Mail list logo