I use it for just about everything work-related, but given that my day job is literally "connect to sets of remote servers and bang out code" it'd be insane not to. Some of my coworkers still use screen, but tmux + wemux having the automatic "scale to the smallest attached screen" + "automatically follow the driver in pair mode" means there's a lot less "can you shrink your window"/"which window are you in now?" types of interruptions.
Apart from that, I've got a perpetual tmux running on my linode for irssi, and I've also got tmux running locally-- being able to set up multiple sessions connected to the same tmux server means that I can have a different tmux session per physical monitor, which means both a shared tmux copy/paste buffer and the ability to easily flip from window to window depending on what I want on which monitor. Ctrl+B for the local tmux, Ctrl+A for remote tmux means that there's no weird double-control-characters necessary. Add in some sneaky scripts to symlink login SSH agents to a known location that's exported to all tmux sessions for ease of git and you end up with a really clean overall workflow.
I work mostly locally, but I still use tmux. I've found it much easier to use than multiple tabs or windows of iterm, and it's nice to have power line right there on the screen at all times. As others have said, the clipboard functionality is nice as well.
The most common thing that comes to mind is altering huge database tables. You may need from minutes to hours to perform heavy SQL operations and if you run your commands from a client you want it to survive the ssh session, no matter what.
Another example is the import/export of large quantities of data (e.g. to clone/move a machine) or perform a long running task (e.g. you found a better way to compress images and want to run it once on every image).
Of course these are not everyday tasks, but once in a while they may be required.
That said, if you connect via ssh to a server you are rarely happy to "lose" whatever task you have run, there aren't major drawbacks in using screen/tmux everytime you connect to a remote server.
Where I work, most of our development (includes building, testing and packaging) is done on remote machines to which we ssh to. Few people prefer gui ide's so most ssh and then run vim or emacs. Having tmux on the server hub is pretty convenient. Especially nice if you want to run a set of tests over night.
Awesome to hear! I thought there must be lots of people who need something like this. I did - hence the build.
I did tweet it to George Nachman so he knows about the project (https://twitter.com/gnachman/status/629372966879526917). I think he is quite busy working on the next big iTerm release, but I've been reporting issues there. Part of what George is working on is far improved Applescript support, allowing for improved addition of these sorts of features. :)
In particular, we would very much like to talk to digital marketing / SEO consultants in any of our cities.
We recently had an all-hands email thread where the whole team discussed what brought them to Distilled, and why they are still here. It got many great replies (including a number talking about how people's friends had typically had 2-3 jobs in the time they'd been with us), but this one stood out:
"A combination of an informal environment, freedom, and high expectations - I wanted a place where I could be myself and grow doing/learning things that I was passionate about, while having lots of smart people around me to collaborate with in doing so. I came from a huge, strictly regimented and siloed company, and was fed up with being told "that's a great idea, but it's not your job", and Distilled seemed to be the polar opposite."
Distilled | London (On-Site) | Full time | Junior Python Developer
I'm Tom - I'm Head of R&D at Distilled, and I'm looking to hire a new developer to join my team. The R&D team is quite new and is still small (just 3 of us) and operates somewhat like a small startup within the larger company.
Distilled are a creative online marketing agency with an HQ in London and offices in New York and Seattle. We work with companies both big and small.
Our main technology is Python, with Django for serving front ends. We make use of a number of other technologies such as Celery, Ansible, PhantomJS, R, and ReactJS.
We don’t mind too much about your prior experience (basic Python is enough), but we care a lot about your mindset. You should be very smart, have an inquisitive nature, and above all else, you need to be passionate about becoming a great programmer.
We aren't planning to throw you in the deep end, but instead care much more about finding someone who is a cultural fit than exactly hitting all the exact criteria. We are ready and willing to help you learn and grow into this role.
We are offering a starting salary of £25,000 - £30,000 depending on your experience.
Andrew Wilson (the translator) was my Latin teacher in school (20 years ago!), and I remember he made the subject quite fun. Having someone who is so passionate about their subject makes a huge difference as a student.
The effort and ingenuity he put into the translation is wonderful. I can't speak any Greek, so having the translations and logic laid out is a wonderful insight into translation as a process.
Discoverability. With fish i would have to type something that would be a good match to the command i want to re-run before pressing up. With bash i type ctrl+r and start typing and i can continue to type until it's narrowed down to the correct command.
> This whole articles seems to presuppose that the only alternative to plain text is Microsoft Word.
The article addresses a particular area in which Microsoft Word is the dominant status quo choice, and lays out why the author thinks that "plain text" is a desirable alternative.
It does not, either explicitly or implicitly, suggest that Microsoft Word is the only alternative to plain text, or vice versa.
> Also by his definition 'plain text' seems to include other markup, including LaTeX.
I think its reasonable to describe a format where what you see if you load the file in a text editor is the same as the text you actually work with as an author as a "plain text" format.
> Many academic books and articles are written this way.
The author doesn't claim that it is unique, though he does suggest that there is resistance, particularly in his field.
> Am I missing something?
I would say it seems like two things:
1. The explicitly stated point of the article ("I want to focus on the specific, idiosyncratic reasons why I wanted (and still want) to write this way, using nothing more than a text editor and Pandoc."), and
2. the implicit target audience of the article (academics in history and similar fields).
Original author here. Yes, I'm mainly assuming my reader is a humanities person less familiar with LaTeX. Though there's increasing interest in Markdown and LaTeX among historians since I wrote this post. See, for example: