I'm not sure whether you mean that I should just add the actions
sections empty or with ssh1=ssh host1.org. I'm not sure where you want
me to create the submenu.
I tried with version 0.12.
Also when ever I start terminator I miss the title bars on the terms. Is
that a known bug?
Kind Regards
Martin
Jordan Callicoat schrieb:
> This should be relatively easy to implement. Just add a new section
> (e.g., "[actions]") to the config file. If that section exists, create a
> submenu in the right-click menu, and populate it with the values from
> that section (e.g., "SSH1 = ssh host1.org"). When an action is
> activated, feed the active term the command associated with the action.
> The only drawback would be that action names must be valid config item
> names (e.g., no spaces). It would also be relatively easy to add UI for
> this in the profile editor.
>
> An alternate approach would be to use a separate config file (e.g.,
> ~/.config/terminator/actions), that allows for arbitrary action names
> (simply split lines on "="?), without all the bells and whistles of the
> config class.
>
> I'll try to play with this in the next few days.
>
>
Hi Jordan,
thanks for the reply.
I'm not sure whether you mean that I should just add the actions
sections empty or with ssh1=ssh host1.org. I'm not sure where you want
me to create the submenu.
I tried with version 0.12.
Also when ever I start terminator I miss the title bars on the terms. Is
that a known bug?
Kind Regards
Martin
Jordan Callicoat schrieb: terminator/ actions) , that allows for arbitrary action names
> This should be relatively easy to implement. Just add a new section
> (e.g., "[actions]") to the config file. If that section exists, create a
> submenu in the right-click menu, and populate it with the values from
> that section (e.g., "SSH1 = ssh host1.org"). When an action is
> activated, feed the active term the command associated with the action.
> The only drawback would be that action names must be valid config item
> names (e.g., no spaces). It would also be relatively easy to add UI for
> this in the profile editor.
>
> An alternate approach would be to use a separate config file (e.g.,
> ~/.config/
> (simply split lines on "="?), without all the bells and whistles of the
> config class.
>
> I'll try to play with this in the next few days.
>
>