Hello All,
I am pretty new to Suse Linux, coming from Sun Solaris. I have an issue with the “more” command. It highlights all the lines beyond the first terminal appearance; anyway I can kill this highlighting?
Thanks!
Why not use the less command? it’s more modern.
On 2010-08-04 00:36, missingunix wrote:
>
> Hello All,
>
> I am pretty new to Suse Linux, coming from Sun Solaris. I have an
> issue with the “more” command. It highlights all the lines beyond the
> first terminal appearance; anyway I can kill this highlighting?
I don’t see that behaviour here. What command line do you use and on which terminal and desktop?
Perhaps a screenshot uploaded somewhere?
Although I prefer less to more, which is really more than more >:-)
Did you understood my meaning? Then there is also a dog :-p
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
Carlos E. R. wrote:
> Although I prefer less to more, which is really more than more >:-)
i also vote for less and have never seen the highlighting noted with
more (but don’t use it much)…
man more | grep -i high
returns zip…
you might try launching more with the -u switch (suppress
underlining)…or, once launched try a ^L to redraw the screen…
beyond that i have to guess some kind of graphic problem and guess
we might need to know the OS, version, state of update, DE used (if
any), graphics chip/driver in use and what?
bash or other?
GUI terminal, or boot to run level 3 command line, Ctrl+Alt+F1, or what?
oh, and if using bash have you ‘customized’ /etc/bash.bashrc or
/home/[you]/.bashrc, or added a /etc/bash.bashrc.local ?? if so can
you back level and try again?
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
I use more rather often (after typing* | more* for more then 20 years it is not easy to change to less lol! ), but I never experienced what I think you post.
Easy, just do
alias more=‘less’
and more is less, or should that be less is more? Or more or less? lol!
But I suspect some terminfo issues with the OP. Without knowing more about his environment, can’t really say.
Hello Gentleman/Ladies,
Thank you for the replies, I now use less as all of you have stated; much better than more.
But, I am still having the highlighting issue. On the man page for less it only states how to remove highlighting for search strings; but, I am getting highlighting on every line after my first forward move.
Here is the info on my system:
uname -a —> Linux hostname* 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 Time* x86_64 x86_64 x86_64 GNU/Linux
echo $TERM–> xterm (this I am assuming because I am remotely logging into the Linux box from a Solaris Box)
Currently using standard .vimrc and DIR_COLORS
Thanks in advance!!! 
Ken, I agree with yourself. It most likely is a term issues on Solaris box; but, not sure what it could be.
When I login from my windows machine into my Linux box using Cygwin, I have no such highlighting issues.
missingunix wrote:
> When I login from my windows machine into my Linux box using Cygwin, I
> have no such highlighting issues.
i bet you need to ask a Solaris Guru…
–
DenverD
CAVEAT: http://is.gd/bpoMD [posted via NNTP w/openSUSE 10.3]
Hi Denver,
I would assume it would be some kind of terminal issue that I am overlooking; as Ken stated? I have no such issue when I am logging from Solaris → Solaris. Hence, pointing to some kind of environment setting on my Linux box?
I use the bash shell, and from my understanding these are the only files that get sourced during login:
$HOME/.bashrc
/etc/bash.bashrc
Thanks!
On 2010-08-04 23:06, missingunix wrote:
>
> Hi Denver,
>
> I would assume it would be some kind of terminal issue that I am
> overlooking; as Ken stated? I have no such issue when I am logging from
> Solaris → Solaris. Hence, pointing to some kind of environment
> setting on my Linux box?
>
> I use the bash shell, and from my understanding these are the only
> files that get sourced during login:
> $HOME/.bashrc
> /etc/bash.bashrc
Linux does some kind of terminal detection and adapts to it. Time ago I had to use “vt100” instead
of the default “linux”. I’m unsure if it is the “TERM” variable, which now instead has value “xterm”.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
Hi Carlos,
Thanks for the hint, I set the $TERM to vt100 and the issue was solved.
I take it vt100 is close to xterm; since, xterm is supposed to emulate vt100?
Thanks!
More likely your terminal window on Solaris can only deal with the vt100 subset of xterm capabilities and falsely claiming to be xterm allowed Linux to send control sequences the terminal window wasn’t prepared for.
vt100 < xterm as far as control sequence capability goes.
On 2010-08-06 00:06, ken yap wrote:
>
> More likely your terminal window on Solaris can only deal with the vt100
> subset of xterm capabilities and falsely claiming to be xterm allowed
> Linux to send control sequences the terminal window wasn’t prepared for.
>
> vt100 < xterm as far as control sequence capability goes.
I’m not sure who is setting that xterm thing, it could be Linux. Years ago it was set to “linux”
when I connected from windows, because the linux terminal is not standard. And vt100 is standard,
that’s why it works. I also tried with vt102 that time.
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
It depends on what software was used to connect which determines whether the TERM variable is inherited or has to be set by heuristic at the server end. telnet probably doesn’t do the right thing. Recent versions of ssh probably do, but it could also be that Solaris’ idea of xterm capabilities is behind the times.
On 2010-08-06 02:36, ken yap wrote:
>
> Carlos E. R.;2202136 Wrote:
>> I’m not sure who is setting that xterm thing, it could be Linux.
>
> It depends on what software was used to connect which determines
> whether the TERM variable is inherited or has to be set by heuristic at
> the server end. telnet probably doesn’t do the right thing. Recent
> versions of ssh probably do, but it could also be that Solaris’ idea of
> xterm capabilities is behind the times.
Who defines “behind the times”? The “xterm” should be common to old unixes and linuxes. Perhaps it
is linux who has improved xterm to the point of not being compatible.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
Just to clarify a bit. It is on my Solaris box that the TERM is set to xterm; reason being is that our systems control legacy equipment and require the X system. Also, it relies on the CDE (Common Destop Environment) interface (required for our GUI). Nonetheless, it seems that setting the TERM to vt100 during remote session login fixes the issue.
Thanks!