Re: [STUMP] Using run-or-raise to manage pre-configured windows in a tmux session

[Ruthard Baudach]

>== Auszüge aus der Nachricht von  Alexander Stein vom 2014-04-09 15:01:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hello,
> 
> I am a recent convert to StumpWM and I have to say I am really loving the 
> power and minimalism.  This is a great project, and I am falling in love with 
> it and Common Lisp again.
> 
> Now, I have a question that I have tried to answer by browsing many 
> configurations in dotfiles and dedicated StumpWM tutorial pages (there a few, 
> but they are very informative).  I am hoping, that a novice, someone can 
> point me in the right direction.
> 
> Like others, I make frequent use of tmux in my day-to-day Linux usage.  I 
> have set up all my GUI applications with (run-or-raise), and most 
> importantly, my terminal emulator of choice (mlterm, since I use pesky 
> non-ASCII RTL languages).  I have my bashrc file configured to automatically 
> load a preconfigured main tmux session with the bells and whistles.  I spend 
> most of my time in mutt, an emacsclient running an org-mode file for work, an 
> emacsclient running an org-mode file for personal stuff, and a few other 
> random windows in this tmux session.  The first few are currently 
> instantiated manually, but in the past I had them open within tmux 
> automatically.
> 
> Is it possible to set (run-or-raise), that when a keybinding calls a function 
> that excutes it, will go to my configured mlterm, and then run the command 
> like "tmux select-window mutt" after raising the current mlterm session?  
> StumpWM is pretty fast as it is, but this would make StumpWM the best 
> experience I ever had on Linux.
> 

I don't know this, probably there is a way to do this.

I just use one xterm for every console program I want tu use (and most
of my favorite programs run in console), thus using stumpwm instead of,
well, for me it is/was screen.

yours

Ruthard