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

[Stefan Reichör]

"J. David Smith" <address@hidden> writes:

> Not sure about tmux being able to do that, I don't use it myself. If it can, 
> great. If not, then
> (window-send-string) is the way to go.

I have one tmux session running and the following works for me:
(run-shell-command "tmux select-window -t CONTROL")

Not sure, how multiple tmux sessions will be handled.

(window-send-string "tmux select-window -t CONTROL") will only work when
you are in a shell window.

Otherwise you need to send Control-B : somehow to enter the tmux command mode.

> On Wed, Apr 9, 2014 at 11:28 AM, Michael Raskin <address@hidden> wrote:
>
>     >@Michael Raskin: that'll send the command to a *new* shell, not the
>     >existing mlterm session.
>    
>     Can't tmux send commands to a preexisting session? I use this screen
>     functionality a lot and always assumed tmux also has something like
>     that. It is somewhat more reliable than emulating key events…
>    
>     >Bjergaard's solution works -- at least with urxvt.
>     >
>     >Here is a sample that runs ls in a non-emacs urxvt client window:
>     >
>     >(defcommand ls () ()
>     >
>     >            (run-or-raise "urxvtc" '(:class "URxvt" :title "^(?!emacs)"))
>     >
>     >            (window-send-string (format nil "ls~%")))
>     >
>     >Using (format nil "ls~%") is necessary, the C-style "ls\n" will not work.
>    
>     Literal line break should work, though.
>    
>     "ls
>     "


Stefan.