<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: How to get a screen session to work the way I want to?</title>
	<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to/</link>
	<description>Comments on Ask MetaFilter post How to get a screen session to work the way I want to?</description>
	<pubDate>Sun, 05 Nov 2006 09:25:51 -0800</pubDate>
	<lastBuildDate>Sun, 05 Nov 2006 09:25:51 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: How to get a screen session to work the way I want to?</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to</link>	
		<description>How do I get my Linux shell to behave the same when I am using screen, as when I am not using it? &lt;br /&gt;&lt;br /&gt; I connect to my linux servers with Putty, from Windows. These are two different servers, but I have the same annoyance. When I work in the shell (bash) without using screen, and I use &quot;less&quot; or &quot;man&quot; or &quot;vim&quot; or something like that to read a file, and I close that file, the open file remains visible in the window. I just start typing new stuff below it. If I do not use screen, when I close the file, I get returned to the shell window I was using before, and I can see my previous commands.&lt;br&gt;
&lt;br&gt;
Also, when I am not in a screen session, I can use the scrollbars in Putty to scroll up in history. When I am in a screen session, this does not work. I can imagine this is a limitation of screen sessions, but if there is a solution for this, I would like to know as well.&lt;br&gt;
&lt;br&gt;
The latter annoyance is not as important, but the former has been irritating me for a long while now, and I hope there is an easy solution.</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2006:site.50208</guid>
		<pubDate>Sun, 05 Nov 2006 09:17:07 -0800</pubDate>
		<dc:creator>davar</dc:creator>
		
			<category>linux</category>
		
			<category>screen</category>
		
			<category>shell</category>
		
			<category>bash</category>
		
			<category>annoyance</category>
		
	</item> <item>
		<title>By: chrismear</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761728</link>	
		<description>&lt;i&gt;Also, when I am not in a screen session, I can use the scrollbars in Putty to scroll up in history. When I am in a screen session, this does not work. I can imagine this is a limitation of screen sessions, but if there is a solution for this, I would like to know as well.&lt;/i&gt;&lt;br&gt;
&lt;br&gt;
screen has a built-in scrollback buffer, which you can use by hitting C-a ESC, and then using C-b and C-f to go backwards and forwards.&lt;br&gt;
&lt;br&gt;
It&apos;s not as convenient as your terminal&apos;s scroll bar, but since screen is sort of simulating a terminal inside a terminal, your terminal isn&apos;t aware of the rest of the output, and you have to use screen&apos;s scrolling (AFAIK).</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761728</guid>
		<pubDate>Sun, 05 Nov 2006 09:25:51 -0800</pubDate>
		<dc:creator>chrismear</dc:creator>
	</item><item>
		<title>By: kcm</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761735</link>	
		<description>Change $TERM to whatever it is when you&apos;re not running screen.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761735</guid>
		<pubDate>Sun, 05 Nov 2006 09:29:48 -0800</pubDate>
		<dc:creator>kcm</dc:creator>
	</item><item>
		<title>By: davar</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761807</link>	
		<description>Thanks chrismear, that works! It is a bit more cumbersome than using scrollbars, but now at least I can see the info I want again.&lt;br&gt;
&lt;br&gt;
kcm, when I am not in screen, my $TERM is xterm. When I set TERM=xterm inside screen, the behaviour does not change.&lt;br&gt;
&lt;br&gt;
Any more ideas?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761807</guid>
		<pubDate>Sun, 05 Nov 2006 10:54:08 -0800</pubDate>
		<dc:creator>davar</dc:creator>
	</item><item>
		<title>By: mnology</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761820</link>	
		<description>&lt;a href=&quot;http://dtach.sourceforge.net&quot;&gt;dtach&lt;/a&gt; + &lt;a href=&quot;http://en.poderosa.org/&quot;&gt;Poderosa&lt;/a&gt;? Or any other tabbed terminal. How much of screen&apos;s functionality do you really need? When it sounds like you&apos;re just using it to maintain a detached process?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761820</guid>
		<pubDate>Sun, 05 Nov 2006 11:13:51 -0800</pubDate>
		<dc:creator>mnology</dc:creator>
	</item><item>
		<title>By: effugas</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761832</link>	
		<description>Try a few other terminals.  $TERM=rxvt works much better in alot of situations.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761832</guid>
		<pubDate>Sun, 05 Nov 2006 11:47:07 -0800</pubDate>
		<dc:creator>effugas</dc:creator>
	</item><item>
		<title>By: majick</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761855</link>	
		<description>export TERM=xterm-noalt</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761855</guid>
		<pubDate>Sun, 05 Nov 2006 12:36:56 -0800</pubDate>
		<dc:creator>majick</dc:creator>
	</item><item>
		<title>By: easyasy3k</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761861</link>	
		<description>Aha! Point 2 has bothered me forever, and now a quick search came up with &lt;a href=&quot;http://www4.informatik.uni-erlangen.de/~jnweiger/screen-faq.html&quot;&gt;this FAQ&lt;/a&gt; that answers the problem!&lt;br&gt;
&lt;br&gt;
Just add&lt;br&gt;
&lt;br&gt;
&lt;code&gt;termcapinfo xterm ti@:te@&lt;/code&gt;&lt;br&gt;
&lt;br&gt;
to your &lt;code&gt;~/.screenrc&lt;/code&gt; file, where &quot;&lt;code&gt;xterm&lt;/code&gt;&quot; is your &lt;code&gt;$TERM&lt;/code&gt;. It fixed both scrollback and leaves less/vim/whatever text there after you exit them.&lt;br&gt;
&lt;br&gt;
&lt;small&gt;Of course, I want point 2 without point 1... *grumble grumble*&lt;/small&gt;</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761861</guid>
		<pubDate>Sun, 05 Nov 2006 12:56:18 -0800</pubDate>
		<dc:creator>easyasy3k</dc:creator>
	</item><item>
		<title>By: davar</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#761880</link>	
		<description>Thanks mnology, that is a great solution! I had never heard of Poderosa; it seems very nice.&lt;br&gt;
&lt;br&gt;
I tried all the TERM settings, but none did what I want. Maybe it is because I was using Putty, instead of a linux terminal app? With xterm-noalt I get a warning that &quot;WARNING: terminal is not fully functional&quot; when using less, and the problem is still there. When using rxvt the vim/less/man info does disappear when I quit the program, but my screen is totally empty: no history of my previous commands. So, that&apos;s not exactly what I was looking for as well.&lt;br&gt;
&lt;br&gt;
easyasy3k: Thanks, that is really useful. I will read that page more carefully or try the mailinglist if Poderosa doesn&apos;t work out. The solution you quote does not work for me though. I &lt;em&gt;do not&lt;/em&gt; want it to leave the vim text after I quite the program.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-761880</guid>
		<pubDate>Sun, 05 Nov 2006 13:34:24 -0800</pubDate>
		<dc:creator>davar</dc:creator>
	</item><item>
		<title>By: bpt</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#763492</link>	
		<description>If you want screen to clear the text when exiting &apos;visual&apos; programs, add &lt;code&gt;altscreen on&lt;/code&gt; to your ~/.screenrc.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-763492</guid>
		<pubDate>Tue, 07 Nov 2006 02:23:44 -0800</pubDate>
		<dc:creator>bpt</dc:creator>
	</item><item>
		<title>By: davar</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#763606</link>	
		<description>Thanks bpt! That does exactly what I want. This has been irritating me for ages.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-763606</guid>
		<pubDate>Tue, 07 Nov 2006 06:56:13 -0800</pubDate>
		<dc:creator>davar</dc:creator>
	</item><item>
		<title>By: majick</title>
		<link>http://ask.metafilter.com/50208/How-to-get-a-screen-session-to-work-the-way-I-want-to#766501</link>	
		<description>&lt;i&gt;&quot;I do not want it to leave the vim text after I quite the program.&quot;&lt;/i&gt;&lt;br&gt;
&lt;br&gt;
I misunderstood the question, then.  (Mostly because I can&apos;t imagine why an altscreen is at all ever desirable; when I quit less, I want to see the page I quit on so I can type commands while referring to it.  I guess I projected my own requirements onto your question.) &lt;br&gt;
&lt;br&gt;
I rescind my answer and offer my apologies for muddying the waters and wasting your time.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2006:site.50208-766501</guid>
		<pubDate>Thu, 09 Nov 2006 21:06:50 -0800</pubDate>
		<dc:creator>majick</dc:creator>
	</item>
	</channel>
</rss>
