It sounds like you already have a workflow, are happy with it, and don't see any need for alteration. :)Īnyway, I don't want you to think I'm trying to persuade you into adopting what I consider awesome and useful. '.but transient windows don't need splits' well, in my universe transient windows are splits. How can I determine in the rc. I've some autostart commands in rc.lua and they are executed every time I restart the window manager. Even if I have iTerm or Konsole using another session. Does awesome window manager set some kind of flag during restart. For Macs, that is often Font Book or Font Explorer X.

:) I normally have a TMUX session dedicated to an ansi-term buffer in Emacs. install these into the Font Manager that your operating system uses to manage fonts. If you are an Emacs user, it's also worth noting that TMUX totally works well with ansi-term. Sessions and windows can be given labels which is a nice touch too. Except the benefit is that now you can use this workflow on any system with a posix compliant shell and a tmux binary (which I'm pretty certain is practically all the things at this point).

Sounds like your use case could be mapped by TMUX windows acting like Terminal tabs, and TMUX sessions acting like multiple Terminal windows. It's also scriptable if you aren't happy with some aspect of it's default presentation or interaction. Create, deploy, run, and manage APIs, API proxies and services with a. TMUX is a transferable implementation of terminal session and 'tab' organization. Fully SaaS enterprise-grade API-first development and management.

Awesome window manager