LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 01-09-2005, 01:06 PM   #1
zedmelon
Member
 
Registered: Jun 2004
Location: colorado, USA
Distribution: slack, oBSD
Posts: 119

Rep: Reputation: 22
[vi|man|less] covers/erases previous screen output


Either I would completely fail the [ Google | LinuxQuestions ] Search String Composition Test, or I am the only person who is annoyed enough by this to try and fix it.

When I use vi, man, less, et cetera, the screen is cleared (naturally) for the output of the program. When I'm done, the previous scrollback has been covered for the number of lines in the console, including the output or errors from what I was doing. I imagine whoever originally set this behavior enjoyed the extra scrollback it afforded, but more often than not, it erases information that I would have used for reference.

------------
Code:
make --with --a_buncha_options
(ten or thirty minutes pass)
Code:
*BARF*
naw, that didn't work. Hrmm, what does this error mean?
Code:
less INSTALL
Okay, now what was that error again...? Crap. No way to tell.
------------


I could just alias 'man' to 'echo;echo...echo;echo;man" and be done with it, but there's got to be a more intelligent way to do this.

I've man-ed setterm and term, but that's all I can think of. I've also manned less and skimmed man, but since the behavior is ubiquitous for all the fullscreen programs like this, the solution is likely elsewhere.

I'm using Slackware, but I've seen the same behavior--whether it's a tty or a remote pts--in oBSD and (I think) Fedora2, so I doubt it's relegated to one or two distros.
 
Old 01-09-2005, 10:52 PM   #2
zedmelon
Member
 
Registered: Jun 2004
Location: colorado, USA
Distribution: slack, oBSD
Posts: 119

Original Poster
Rep: Reputation: 22
*bump*

Anyone have any ideas on this?




Mods, I hate to double-post, but should I have posed this question in "Linux - General?"
 
Old 01-10-2005, 03:22 PM   #3
dr_zayus69
Member
 
Registered: Sep 2004
Location: western massachusetts
Distribution: fedora core 3, Suse 10
Posts: 877

Rep: Reputation: 35
The only idea i have is you could do make -bunch of options > tempfilename. This will put the output of make -bunch of options into the file named tempfilename. Then just remember a word or two of the error then do grep [options] words you remembered tempfilename. Or you could store the error in your PAA -personal analog assistant aka a notepad and number two stylus.
 
Old 01-10-2005, 03:31 PM   #4
bulliver
Senior Member
 
Registered: Nov 2002
Location: Edmonton AB, Canada
Distribution: Gentoo x86_64; Gentoo PPC; FreeBSD; OS X 10.9.4
Posts: 3,760
Blog Entries: 4

Rep: Reputation: 77
Sounds like it may be slack specific...

When I use less, vim etc...when I quit the buffer is redrawn (ie: what you want) so I would assume there has to be a config for this somewhere...

EDIT: ok, sorry. Just ignore me...it works in an xterm (konsole) but not on the CLI

Last edited by bulliver; 01-10-2005 at 03:33 PM.
 
Old 01-10-2005, 06:11 PM   #5
zedmelon
Member
 
Registered: Jun 2004
Location: colorado, USA
Distribution: slack, oBSD
Posts: 119

Original Poster
Rep: Reputation: 22
Quote:
Originally posted by dr_zayus69
The only idea i have is you could do make -bunch of options > tempfilename.
Yeah, but rather than circumventing the issue, I want to eliminate the "cover up." SecureCRT (Windows ssh client) has an option "scroll to clear screen;" I guess I'm wanting something similar to that.
Quote:
Or you could store the error in your PAA -personal analog assistant aka a notepad and number two stylus.
*chortle* I like that.

----------
Quote:
Originally posted by bulliver
Sounds like it may be slack specific...

When I use less, vim etc...when I quit the buffer is redrawn (ie: what you want) so I would assume there has to be a config for this somewhere...
Yeah, I thought so too, because my BSD box gives my undisturbed screen back, and you can't even tell I edited a file. Other than the command line "# vi jonketyfilecrap" that is.
Quote:
...it works in an xterm (konsole) but not on the CLI
I checked this out. No diff on the tty or pts (my machines are across the room in a rack). Just for kicks, I did "man vi" (then found the link below) then "man elvis." I didn't see anything that might help, but I haven't scrutinized the built in help yet either. However, I did notice this:
Code:
/usr/bin/vi --> elvis
I tried 'vim,' and it gave back my console (yippee!). When I first learned vi wasn't really vi (~2001), I was noob enough to not know any difference. Hopefully I'm still noob enough to not tell between vim and elvis, because I edited the link to point to vim.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
dual screen/ tv output - help please Enoon Suse/Novell 1 10-06-2005 02:17 PM
output to screen from a deamon csfalcon Programming 10 04-22-2005 02:14 AM
How to quit man (less) and keep man info on screen? peb Linux - Newbie 7 03-25-2004 10:02 PM
MBR erases when power is off Zero-0-Effect Linux - General 6 01-24-2004 09:05 PM
CD covers for Redhat booya72 Linux - General 5 05-29-2002 06:59 AM


All times are GMT -5. The time now is 11:47 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration