Dear diary, on Fri, Mar 04, 2005 at 06:28:57PM CET, I got a letter,
where Ryan Underwood <[EMAIL PROTECTED]> told me, that...
>
> On Fri, Mar 04, 2005 at 08:22:21AM +0100, Petr Baudis wrote:
> > Dear diary, on Fri, Mar 04, 2005 at 07:08:45AM CET, I got a letter,
> > where Ryan Underwood <[EMAIL PROTECTED]> told me, that...
> > > It appears that the default Terminal Options->Frame Handling setting of
> > > Linux or OS/2 Frames causes wrong output under an xterm (the lines are
> > > replaced with alphabet characters). Changing this to VT100 provides
> > > proper output in both an xterm and Linux console. It would seem
> > > sensible to make this the default, but I may be overlooking something
> > > obvious.
> >
> > At least in the upstream version, the default is to use the ASCII frames
> > if the $TERM is unknown, Linux frames if the $TERM is linux and VT100
> > frames if the $TERM is vt100 or xterm. So it looks you could get into
> > problems with the default configuration only if your $TERM in your xterm
> > was set to linux, and you should better know what are you doing in that
> > case... ;-)
>
> Is it possible that the following happens:
> 1) User uses elinks at Linux console once
> 2) Preference is set to Linux console frames
> 3) User installs X environment
> 4) User from then on uses elinks at xterm, but preference has been
> automatically set to linux console already
This is not really how it works. The terminal settings are specific to
the given $TERM. You can have multiple terminal settings for different
$TERMs and the one matching your $TERM is selected automatically.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
98% of the time I am right. Why worry about the other 3%.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
