<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ghostbar &#187; tmux</title>
	<atom:link href="http://ghostbar.ath.cx/tag/tmux/feed/" rel="self" type="application/rss+xml" />
	<link>http://ghostbar.ath.cx</link>
	<description></description>
	<lastBuildDate>Sun, 29 Apr 2012 15:49:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title> and  issues on vim with $TERM=&#8221;screen&#8221;</title>
		<link>http://ghostbar.ath.cx/2011/10/26/and-issues-on-vim-with-termscreen/</link>
		<comments>http://ghostbar.ath.cx/2011/10/26/and-issues-on-vim-with-termscreen/#comments</comments>
		<pubDate>Wed, 26 Oct 2011 05:06:51 +0000</pubDate>
		<dc:creator>ghostbar</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Tecnología]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Planet Debian]]></category>
		<category><![CDATA[tmux]]></category>
		<category><![CDATA[VIM]]></category>
		<category><![CDATA[XTerm]]></category>

		<guid isPermaLink="false">http://ghostbar.ath.cx/?p=622</guid>
		<description><![CDATA[Because of tmux I run with $TERM=&#8221;screen&#8221; instead of my regular rxvt-unicode, but I had a big issue with VIM because of this, it kept writing and F\n and H\n each time I pressed and keys respectively. I finally found the way to solve this, making VIM use $TERM=&#8221;xterm&#8221; internally writing this on my ~/.vimrc: [...]]]></description>
			<content:encoded><![CDATA[<p>Because of tmux I run with $TERM=&#8221;screen&#8221; instead of my regular rxvt-unicode, but I had a big issue with VIM because of this, it kept writing and F\n and H\n each time I pressed <End> and <Home> keys respectively. I finally found the way to solve this, making VIM use $TERM=&#8221;xterm&#8221; internally writing this on my ~/.vimrc:<br />
<code>if &#038;term == "screen"<br />
  set term=xterm<br />
endif</code></p>
<p>So, this way, even in my servers without XTerm installed (but ncurses-term) I can use VIM as I&#8217;m used to.</p>
]]></content:encoded>
			<wfw:commentRss>http://ghostbar.ath.cx/2011/10/26/and-issues-on-vim-with-termscreen/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Moving from Screen to Tmux</title>
		<link>http://ghostbar.ath.cx/2011/10/02/moving-from-screen-to-tmux/</link>
		<comments>http://ghostbar.ath.cx/2011/10/02/moving-from-screen-to-tmux/#comments</comments>
		<pubDate>Sun, 02 Oct 2011 23:16:30 +0000</pubDate>
		<dc:creator>ghostbar</dc:creator>
				<category><![CDATA[English]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Tecnología]]></category>
		<category><![CDATA[Free Software]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Planet Debian]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[screen]]></category>
		<category><![CDATA[tmux]]></category>

		<guid isPermaLink="false">http://ghostbar.ath.cx/?p=616</guid>
		<description><![CDATA[I&#8217;ve been a long-time user of GNU Screen, as almost every person I know that spend a lot of time in a terminal. I must admit I was happy, I really was. I was used to my workflow with 4 terminals 8&#215;25 and a bunch of screens, with several nested-screens. I used awesome-wm before, so [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been a long-time user of GNU Screen, as almost every person I know that spend a lot of time in a terminal.</p>
<p>I must admit I was happy, I really was. I was used to my workflow with 4 terminals 8&#215;25 and a bunch of screens, with several nested-screens. I used awesome-wm before, so definitely I felt I wasn&#8217;t using all the space in my laptop screen (my laptop is a ThinkPad X61, so 1024&#215;768 in a 12 inches-screen) but that was OK, after all my workflow was, well, good.</p>
<p>Until 2 days ago, I was told to try tmux, in fact, I was told «<em>and why are you using screen? use tmux</em>». As a daily-user of Screen my first reaction was «<em>I&#8217;m used to</em>», «<em>I can use it as I want</em>», and a lot of excuses for just not trying something new. But then I made a little research (on Google, of course). In about 30 minutes I ended up with a multiplexer working as I wanted and as I never got Screen to work. Finally I was using just a terminal and using all the space available in my tiny-laptop-screen and plus: saving a lot of bandwidth with my permanent <abbr title="Secure Shell">SSH</abbr> connection (a really big plus now that I&#8217;m living with a capped link to the net with a GSM-modem).</p>
<p><a href="http://ghostbar.ath.cx/wp-content/uploads/2011/10/tmux-fullscreen.png"><img src="http://ghostbar.ath.cx/wp-content/uploads/2011/10/tmux-fullscreen-300x225.png" alt="" title="tmux-fullscreen" width="300" height="225" class="aligncenter size-medium wp-image-618" /></a></p>
<p>I changed the Ctrl-b shortcut to Ctrl-a (b is too far for using it with only one hand), configured so I could use nested tmux&#8217;es like screen when I push Ctrl-a a, activated visual monitoring and even got to use the tmux&#8217;s buffer along with my X11 buffer when I press Ctrl-a >!!</p>
<p>It&#8217;s all in my <a href="https://github.com/ghostbar/userdotfiles/blob/master/tmux.conf">~/.tmux.conf</a>, use it at will. Later I will make a screencast about using tmux, so more people can get a working tmux easily.</p>
<p>ATM, I&#8217;m even more happy than I was with GNU Screen, so, any other recommendation, people?</p>
]]></content:encoded>
			<wfw:commentRss>http://ghostbar.ath.cx/2011/10/02/moving-from-screen-to-tmux/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>

