<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Khachatur Ashotyan on Medium]]></title>
        <description><![CDATA[Stories by Khachatur Ashotyan on Medium]]></description>
        <link>https://medium.com/@lanycrost?source=rss-5574c6fe73aa------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AsrdQRqSjCKHKYxopDmGOg.jpeg</url>
            <title>Stories by Khachatur Ashotyan on Medium</title>
            <link>https://medium.com/@lanycrost?source=rss-5574c6fe73aa------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 23:03:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lanycrost/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Every Hacker should have a great terminal | TMUX | Part 2: Configuration]]></title>
            <link>https://medium.com/@lanycrost/every-hacker-should-have-a-great-terminal-tmux-part-2-configuration-abe57a8c082d?source=rss-5574c6fe73aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/abe57a8c082d</guid>
            <category><![CDATA[bash]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[shell]]></category>
            <category><![CDATA[tmux]]></category>
            <category><![CDATA[terminal]]></category>
            <dc:creator><![CDATA[Khachatur Ashotyan]]></dc:creator>
            <pubDate>Sun, 13 Jan 2019 15:11:04 GMT</pubDate>
            <atom:updated>2019-01-13T15:11:04.772Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JtL_BSoMDTjLsjhq" /><figcaption>Photo by <a href="https://unsplash.com/@atgranberry?utm_source=medium&amp;utm_medium=referral">Aidan Granberry</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Tmux is highly configurable and customizable, it’s clear that a lot of tmux users are breaking away from the defaults by creating their own customized configurations. These configurations vary from the trivial, such as adding keybindings, and adjusting the prefix key, to complex things, such as decking out the status bar with system stats and other fancy features. My opinion you are should start with a basic configuration and get used to it before you get silly. I’ve seen multiple people spend hours configuring vim or tmux only to confuse themselves and abandon the project altogether.</p><blockquote>I want to show you a wonderfulness of tmux, but also you are should use it smartly. I advise, build your own configuration step by step, by trial and error.</blockquote><h3>Configuration Interfaces</h3><p>The tmux configuration is processed just like <a href="https://en.wikipedia.org/wiki/Run_commands">run commands</a> in a ~/.zshrc or ~/.bashrc file. bind r source ~/.tmux.conf in the tmux configuration is the same as $ tmux bind r source ~/.tmux.conf. Continue reading for understand this part.</p><p>Tmux has 3 interfaces for running commands and making configurations:</p><ol><li><strong>Tmux executable</strong> - This is the tmux command available in your shell. All commands can be run directly against this, but note that any configurations set via the tmux command will be cleared when the server is shut down.</li><li><strong>Tmux command prompt </strong>- The command prompt allows you to run all the same commands as can be run against the executable but has the benefit that you can interact with it even when a process is occupying the full screen, such as Vim would. The command prompt can be accessed by running &lt;prefix&gt; + : and will temporarily take over the tmux status bar. Note, there is no need to type tmux before a command when in the command prompt. Also, just like with the executable, any configurations made will be cleared when the server is shut down.</li><li><strong>.tmux.conf file</strong> - The final (and primary) method for configuring tmux, this file lives in your home directory and is read by tmux when the server first starts up (when you start your first session). The configuration syntax is identical to what you run against the executable or in the command prompt, so both can be used to test out commands and configurations prior to adding them to your .tmux.conf. This file will be read every time the server starts up but will not be read when opening new windows, panes, or sessions after the server starts. See below for how to reload the config file manually.</li></ol><h3><strong>Easy reloading</strong></h3><p>You can bind-key to source-file ~/.tmux.conf:</p><pre>bind r source ~/.tmux.conf</pre><p>You can also have it give you a confirmation afterwards:</p><pre>bind-key r source-file ~/.tmux.conf \; display-message &quot;~/.tmux.conf reloaded&quot;</pre><p>Now, you can type &lt;prefix&gt; + r to get the config to reload.</p><p>Note that reloading the configuration only <em>re-runs</em> the configuration file. It will not reset keybindings or styling you apply to tmux.</p><h3>Server options</h3><p>Server options are set with set-option -s option value.</p><h4>Terminal coloring</h4><p>If you’re having an issue with color detail in tmux, it may help to set default-terminal to screen-256color.</p><pre>set -g default-terminal “screen-256color”</pre><p>This sets the TERM variable in new panes.</p><h3>Session options</h3><p>Aside from the status bar, most user configuration will be custom keybindings.</p><h4>Base index</h4><p>It’s a favorite tweak of many tmux users, who find it more intuitive to start their window counting at <em>1</em>, rather than the default, <em>0</em>. To set the starting number (base index) for windows:</p><pre>set -g base-index 1</pre><p>Setting base-index assures newly created windows start at 1 and count upwards.</p><h3>Window options</h3><p>Window options are set via set-option -w or set-window-option. They are the same thing.</p><h4>Automatic window naming</h4><p>Setting automatic-rename alters the name of the window based upon its active pane:</p><pre>set-window-option -g automatic-rename</pre><p>Automatic renaming will be disabled for the window if you rename it manually.</p><h3>Keybindings</h3><p>By default, all tmux key-bindings will require you to type the prefix key sequence first, then the desired key to activate the binding. There are two flags that can be used to circumvent the prefix key:</p><ul><li>-n - This flag allows the key-binding to run without need for the prefix key. Note, since tmux wraps all terminal interaction, setting any key-binding with the -n flag will essentially prevent you from sending that sequence through to underlying processes such as Vim since tmux will catch the key sequence and act on it.</li><li>-r - This flag allows key-bindings to be repeated without requiring the prefix key.</li></ul><h4>Prefix key</h4><p>The default prefix key in tmux is Ctrl + b. You can customize it by setting a new prefix and unsetting the default. To set the prefix to Ctrl + a, like GNU Screen, try this:</p><pre>unbind C-b<br>set -g prefix C-a<br>bind-key -r C-a send-prefix</pre><h3>Status bar and styling</h3><p>The status bar, or <em>status line</em>, serves as a customizable taskbar in the bottom of tmux. It is comprised of 3 sections. The status fields on either side of the status line are customizable. The center field is a list of windows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*hpci4v5kDWkk818-RDWtow.png" /></figure><p>The status-left and status-right option can be configured with variables.</p><p>It’s configurable through the .tmux.conf file and modifiable live through using $ tmux set-option.</p><p><em>Finding your current status line settings</em></p><pre>$ tmux show-options -g | grep status</pre><h3><strong>Styling</strong></h3><p>The <em>colors</em> available to tmux are:</p><ul><li>black, red, green, yellow, blue, magenta, cyan, white.</li><li>bright colors, such as brightred, brightgreen, brightyellow, brightblue, brightmagenta, brightcyan.</li><li>colour0 through colour255 from the 256-color set.</li><li>default</li><li>hexadecimal RGB code like #000000, #FFFFFF, similar to HTML colors.</li></ul><p><strong>Status Bar</strong></p><p>The status-right option configures the text displayed on the right side of the tmux status bar and configured with a combination of:</p><ul><li><strong>Literal text</strong> — Use to space out or wrap other output.</li><li><strong>Tmux format patterns</strong> — Special patterns such as #S for the session name will be replaced with the corresponding value. See the FORMATS section of the tmux man page for more options.</li><li><strong>Shell commands</strong> — Any shell command can be included in the format string, wrapped in #(...), and it will be replaced with its output.</li></ul><p>You can use [bg=color] and [fg=color] to adjust the text color and background within for status line text. This works on status-left and status-right.</p><p>Let’s say you want to style the background:</p><p>Command:</p><pre>$ tmux set-option status-style fg=white,bg=black</pre><p>In config:</p><pre>status-style fg=white,bg=black</pre><p>In the examples at the end of the chapter, you will see complete examples of how colors can be used.</p><h4>Clock styling</h4><p>You can style the color of the tmux clock via:</p><pre>set-option -g clock-mode-colour white</pre><blockquote><em>Reminder</em>: Clock mode can be opened with $ tmux clock-mode or &lt;prefix&gt; + t. Pressing any key will exit clock mode.</blockquote><h4>Prompt colors</h4><p>The benefit of wrapping your brain around this styling is you will see it message-command-style, message style and so on.</p><p>Let’s try this:</p><pre>$ tmux set-option -ag message-style fg=yellow,blink\; set-option -ag message\ -style bg=black</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o9uMR49fGnABnKgr.png" /></figure><h3>Toggling status line</h3><p>The tmux status line can be hidden, as well. Turn it off:</p><pre>$ tmux set-option status off</pre><p>And, turn it on:</p><pre>$ tmux set-option status on</pre><p>The above is best for scripting, but if you’re binding it to a keyboard shortcut, <em>toggling</em>, or reversing the current option, it can be done via omitting the on/off value:</p><pre>$ tmux set-option status</pre><p>Bind toggling status line to &lt;prefix&gt; + q :</p><pre>$ tmux bind-key q set-option status</pre><h3>Example: Default config</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*5GB0sw7dFKNCrJyEi6K0lg.png" /></figure><p>This is an example of the default config you see if your tmux configuration has no status styling.</p><pre>status on<br>status-interval 15<br>status-justify left<br>status-keys vi<br>status-left &quot;[#S] &quot;<br>status-left-length 10<br>status-left-style default<br>status-position bottom<br>status-right &quot; &quot;#{=21:pane_title}&quot; %H:%M %d-%b-%y&quot;<br>status-right-length 40<br>status-right-style default<br>status-style fg=black,bg=green</pre><h3>Example: Dressed up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*No1PZy4D-vfEUhyzeUta0Q.png" /></figure><p>This is an example of customized configuration. As you can see you can do everything, but don’t use complex configurations for now, just add something simple, but useful and grow up your skills.</p><p>Configuring the status line is optional. It can use the output of programs installed on your system to give you specialized information, such as CPU, ram, and I/O usage. By default, you’ll at least have a window list and a clock.</p><p>In addition, you can customize the colors of the status line, clock, and prompt. By default, it’s only a green bar with dark text, so take some time to customize yours, if you want, and save it to your configuration.</p><pre>set -g default-terminal &quot;screen-256color&quot;   # Use 256 colors<br>set -g history-limit 100000                 # Scrollback buffer number of lines<br> <br># Start window indexing at one instead of zero<br>set -g base-index 1<br> <br># Set the prefix key and some key bindings to match GNU Screen<br>set -g prefix C-a<br>bind-key C-a last-window<br> <br># Key bindings for horizontal and vertical panes<br>unbind %<br>bind | split-window -h<br>bind - split-window -v<br> <br># Enable window titles<br>#set -g set-titles on<br> <br># Window title string (uses statusbar variables)<br>set -g set-titles-string &#39;#T&#39;<br> <br># Status bar with load and time<br>set -g status-bg &#39;#4e4e4e&#39;<br>set -g status-fg &#39;#ffffff&#39;<br>set -g status-left &#39; &#39;<br>set -g status-right &#39;#[bg=#bbbbbb]#[fg=#000000]#(cut -d &quot; &quot; -f -3 /proc/loadavg) #[bg=#4e4e4e]#[fg=#ffffff]#(<br>date +&quot; %H:%M &quot;)&#39;<br>set -g window-status-format &#39;#I #W&#39;<br>set -g window-status-current-format &#39; #I #W &#39;<br>setw -g window-status-current-bg &#39;#55ff55&#39;<br>setw -g window-status-current-fg &#39;#000000&#39;<br> <br># Pane border colors<br>set -g pane-active-border-fg &#39;#bbbbbb&#39;<br>set -g pane-border-fg &#39;#555555&#39;<br> <br># Bind to reload config<br>bind r source-file ~/.tmux.conf</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abe57a8c082d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every Hacker should have a great terminal | TMUX | Part 1: Introduction]]></title>
            <link>https://medium.com/@lanycrost/every-hacker-should-have-a-great-terminal-tmux-part-1-introduction-82b8f4fa5e79?source=rss-5574c6fe73aa------2</link>
            <guid isPermaLink="false">https://medium.com/p/82b8f4fa5e79</guid>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[zsh]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[tmux]]></category>
            <category><![CDATA[console]]></category>
            <dc:creator><![CDATA[Khachatur Ashotyan]]></dc:creator>
            <pubDate>Sun, 28 Oct 2018 15:48:52 GMT</pubDate>
            <atom:updated>2019-01-13T11:21:10.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Itf7vYgYaXgQuSRr" /><figcaption>Photo by <a href="https://unsplash.com/@ngeshlew?utm_source=medium&amp;utm_medium=referral">Lewis Ngugi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Nearly all my friends afraid a tmux. We are the representatives of “new school” of IT. We are the generation of the century when GUI is everywhere, we don’t have the need to compile, package managers solve our needs and all configuration tricks are available in a web (don’t have the need to read manuals, RFS’s, etc.). Many peoples can’t use git without GUI. And command line stays only for enthusiasts (plus sysadmins, although they also start working with cloud providers and GUI’s) or for starting “webpack”.</p><p>I love working with the command line. Seriously, I think there’s hardly any more productive and more versatile tool for an IT people than the command line. I spend the vast majority of my day in the terminal, and I spend 100% of this time in tmux. And it highly boosts my workflow and my efficiency.</p><p>If someone sees me with my laptop. Usually, this is the point where they will ask something like “WTF am I looking at?” and it’s my time to shine!</p><p>I’ll proceed to give them a two-minute tour about what you can do with tmux. After that, they’re either hooked and want to try it themselves or they tell me to go away with my ancient tools.</p><p>My struggle is not against evolution. I want to show: How much simple become the things, when you understand principles.</p><p>So Let’s get started…</p><h3>WTF am I looking at? (WTF is tmux)</h3><p>Tmux is the <strong>“terminal multiplexer”</strong> behind this fancy term hides a simple concept:</p><p>Within one terminal window, you can open multiple windows and split-views (called “panes”). Each pane will contain its own, independently running terminal instance. This allows you to have multiple terminal commands and applications running visually next to each other without the need to open multiple terminal emulator windows. If you are familiar with GNU Screen this is nothing new. Think of tmux as an easier-to-use and a little more powerful alternative to Screen.</p><p>On top of that tmux keeps these windows and panes in a session. You can exit a session at any point. This is called <em>“detaching”</em>. tmux will keep this session alive until you kill the tmux server (e.g. when you reboot). This is incredibly useful because at any later point in time you can pick that session up exactly from where you left it by simply <em>“attaching”</em> to that session.</p><h3>What? tmux is a server?</h3><p>Often, when “server” is mentioned, what comes to mind for many may be rack-mounted hardware; to others, it may be software running daemonized on a server and managed through a utility, like upstart, supervisor, and so on.</p><p>Unlike web or database software, tmux doesn’t require specialized configuration settings or creating a service entry to start things.</p><p>tmux uses a client-server model, but the server is forked to the background for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AeIgGAt0gJkOPjndBr4awQ.png" /><figcaption>tmux as a server</figcaption></figure><p>You can retrieve a list of active client connections via:</p><pre>$ tmux list-clients</pre><h3>Use Cases</h3><ul><li><strong><em>Long-running processes </em></strong>- When attached to a remote machine via ssh, long-running processes can be started and left running without needing to stay attached via ssh. If you’ve ever worked with remote servers over ssh you can guess where this will be useful: When you lose your ssh connection the tmux session will simply be detached but will keep running on the server in the background including all the processes that run within your session. To continue your session simply ssh to the server again and attach to the running session.</li><li><strong><em>Pair Programming</em></strong> - Tmux can be used to allow two or more users to attach to the same session and share control providing an efficient pair programming setup.</li><li><strong><em>Local Development</em></strong> - By enabling various layouts and communication between multiple processes, tmux can enable enhanced efficiency for local development.</li></ul><h3>Installation</h3><p>Fortunately installing tmux is pretty straightforward on most distributions a simple:</p><ul><li>brew install tmux (MacOS),</li><li>sudo pkg install tmux (FreeBSD),</li><li>sudo apt-get install tmux (Ubuntu, Mint, Debian, etc.),</li><li>sudo yum install tmux (CentOS, Fedora, Redhat, etc.),</li><li>sudo pacman -S tmux (Arch Linux),</li><li>sudo emerge --ask tmux (Gentoo).</li></ul><h3>Tmux Objects Overview</h3><p>Let’s talk about the core modules of tmux.</p><ul><li>Session- the highest-level entity residing in the server instance. Server instances are forked to the background upon starting a fresh instance and reconnected to when reattaching sessions. Your interaction with tmux will have <em>at least</em> one session running. A named collection of one or more windows.</li><li>Window- A single screen within tmux, similar to tabs in terminal applications. At any given time, a client will be attached to a single window.</li><li>Pane- A portion of a window running a single process, e.g. Vim, zsh, man, etc. Panes can be oriented either vertically or horizontally and resized as needed.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSTC9eb8zdmh-sRiLrQ84w.png" /><figcaption>tmux conception</figcaption></figure><h3>Initial Commands</h3><p>The easiest way to start a tmux session is to run the bare tmux command from your terminal.</p><p>Once running, the most tmux interaction will occur by using tmux’s key bindings. By default, all tmux key bindings will require a &lt;prefix&gt; key sequence followed by a <strong>command key</strong> (quite similar to emacs) before they are active. This prefix is initially defined as Ctrl + b (Ctrl and b together).</p><p>The prefix can also be changed, which I’ll show you how to do later.</p><h3>Session Management</h3><p>Figure out which sessions are running by using</p><pre>tmux ls</pre><p>This will give you a list of all running sessions, which in our example should be something like</p><blockquote><em>0: 2 windows (created Sat Aug 15 17:55:34 2015) [199x44] (detached)</em></blockquote><p>To connect to that session you start tmux again but this time tell it which session to attach to:</p><pre>tmux attach -t 0</pre><p>Note that the -t 0 is the parameter that tells tmux which session to attach to. “0” is the first part of your tmux ls output.</p><p>If you prefer to give your sessions a more meaningful name (instead of a numerical one starting with 0) you can create your next session using</p><pre>tmux new -s database</pre><p>This will create a new session with the name “database”.</p><p>You could also rename your existing session:</p><pre>tmux rename-session -t 0 database</pre><p>The next time you attach to that session you simply use tmux attach -t database. If you’re using multiple sessions at once this can become an essential feature.</p><p>tmux new -s session_name - Creates a new tmux session named session_name</p><p>tmux attach -t session_name - Attaches to an existing tmux session named session_name</p><p>tmux switch -t session_name - Switches to an existing session named session_name</p><p>tmux list-sessions - Lists existing tmux sessions tmux detach (prefix + d) detach the currently attached session</p><p><strong>Shortcuts</strong></p><ul><li>&lt;prefix&gt; + ( - Switch the attached client to the previous session.</li><li>&lt;prefix&gt; + ) - Switch the attached client to the next session.</li><li>&lt;prefix&gt; + L - Switch the attached client back to the last session.</li><li>&lt;prefix&gt; + s - Select a new session for the attached client interactively.</li></ul><h3>Window Management</h3><p><strong>Shortcuts</strong></p><ul><li>&lt;prefix&gt; + c- Create a new window (tmux select-window -t :0-9),</li><li>&lt;prefix&gt; + 0-9- Move to the window based on index,</li><li>&lt;prefix&gt; + , - Rename the current window,</li></ul><h3>Pane Management</h3><p>Closing a pane is as simple as closing a regular terminal session. Either type exit or hit Ctrl + d and it’s gone.</p><p><strong>Shortcuts</strong></p><ul><li>&lt;prefix&gt; + %- Split window horizontally (to the right of the current pane),</li><li>&lt;prefix&gt; + &quot;- Split window vertically (below current pane),</li><li>&lt;prefix&gt; + &lt;arrow keys&gt;- Navigate under panes.</li><li>(keep pressed &lt;prefix&gt;) + &lt;arrow keys&gt;- Resize panes.</li></ul><h3>Starting Your First Session</h3><p>For your first session simply start tmux with a new session:</p><pre>$ tmux</pre><p>This will create a new tmux session with a nice all-green status bar at the bottom:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6u-U-EM6U6hFFmuXKlmjA.png" /><figcaption>tmux first session.</figcaption></figure><p>The status bar is an important part of tmux. Apart from the currently opened windows (on the left) it also shows some system information like date and time (on the right). The status bar can also be customized and I’ve seen some really fancy stuff around (upcoming calendar events, battery status, to name a few) but this is something we’ll leave for later.</p><h3>Splitting Panes</h3><p>Now that we’ve created our first session we can get a feeling for panes. When you create a new session, tmux will by default start with one window and a single panel inside. We want a nice split-screen, so let’s split this bad boy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LBLnk9pDMDYvAbNNIFzb5A.png" /><figcaption>tmux with vertical splitting</figcaption></figure><p>Where there’s a split into left and right, there’s also a split into top and bottom pane. To split a pane into the top and bottom panes use the &lt;prefix&gt; + &quot; shortcut.</p><h3>Tmux Configuration File</h3><p>The tmux configuration file lives at ~/.tmux.conf. Edit it to redefine the prefix key by adding the following lines:</p><pre># Use C-s (control and s key at the same time) as the prefix key<br>unbind C-b<br>set -g prefix C-s</pre><p>After saving the file, you can reload the configuration by running:</p><pre>$ tmux source-file ~/.tmux.conf</pre><h3>Workflow Recommendations</h3><ul><li>Use a single client — Although it is possible to run multiple tmux clients by opening multiple terminal tabs or windows, I find it better to focus on one client in a single terminal window. This provides a single high-level abstraction, which is easier to reason about and interact with.</li><li>One project per session — I will open each project, roughly mapping to a git repository in its own session. Typically I will have Vim in the first window along with a pane for running tests and any background processes like the rails server running in additional windows.</li><li>One Vim instance per session — In order to avoid conflicts with temp files and buffers getting out of sync, I will only use a single Vim instance per tmux session. Since each session maps to a specific project, this tends to keep me safe from conflicting edits and similar complications.</li></ul><h3>What about screen?</h3><p>Tmux is a lot like screen, only better. The short answer for how it’s better is that tmux is better designed to perform the same functions. Screen gets you there (kind of) but does so precariously.</p><p>Here are a few of the key advantages of tmux over screen:</p><ul><li>A clearly defined cilent/server model (windows are their own clients which allows flexibility on how you handle windows. You can attach and detach different windows in different sessions without any issues).</li><li>Consistent, well-documented command interface. (You can use the same commands interactively as in the .tmux.conf file, more on that later).</li><li>Easily scriptable.</li><li>Multiple paste buffers.</li><li>A more usable status line syntax (which also allows you to embed the output of a shell command, handy indeed.</li><li>Tmux supports both emacs and vim shortcuts.</li><li>Tmux is highly scriptable.</li></ul><h3>Recommended reading</h3><p>If you want to learn more about how processes and TTYs work at the kernel level (data structures and all), the book <a href="http://amzn.to/2iTmVyv"><em>The Design and Implementation of the FreeBSD Operating System (2nd Edition)</em></a> by Marshall Kirk McKusick is nice, particularly, Chapter 4, <em>Process Management</em> and Section 8.6, <em>Terminal Handling</em>. <a href="http://www.linusakesson.net/programming/tty/index.php"><em>The TTY demystified</em></a> by Linus Åkesson (available online) dives into the TTY.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82b8f4fa5e79" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>