Where to define shell aliases in configs for projects in tmuxinator?

Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
I define Bash aliases in my ~/.tmuxinator/*.yml files like this:
pre_window: alias cc=heh/path/that;alias ccc='cc clean; clear; cc' ;alias selenium-restart=bin/docker/restart-selenium-chrome ;alias yii=bin/docker/yii/yii
Is there a better way? It works, but, obviously, it is not convenient to add them like that.
tmux alias
add a comment |Â
up vote
1
down vote
favorite
I define Bash aliases in my ~/.tmuxinator/*.yml files like this:
pre_window: alias cc=heh/path/that;alias ccc='cc clean; clear; cc' ;alias selenium-restart=bin/docker/restart-selenium-chrome ;alias yii=bin/docker/yii/yii
Is there a better way? It works, but, obviously, it is not convenient to add them like that.
tmux alias
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I define Bash aliases in my ~/.tmuxinator/*.yml files like this:
pre_window: alias cc=heh/path/that;alias ccc='cc clean; clear; cc' ;alias selenium-restart=bin/docker/restart-selenium-chrome ;alias yii=bin/docker/yii/yii
Is there a better way? It works, but, obviously, it is not convenient to add them like that.
tmux alias
I define Bash aliases in my ~/.tmuxinator/*.yml files like this:
pre_window: alias cc=heh/path/that;alias ccc='cc clean; clear; cc' ;alias selenium-restart=bin/docker/restart-selenium-chrome ;alias yii=bin/docker/yii/yii
Is there a better way? It works, but, obviously, it is not convenient to add them like that.
tmux alias
edited Jul 30 at 2:16
slmâ¦
232k65479649
232k65479649
asked Jul 29 at 23:40
jojman
169112
169112
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Based on this ticket in tmuxinator's issue tracker titled: "pre" option not using zsh options, alias, configuration (running as sh) #286 it looks like you'd either do it as a pre: or a pre_window:. The OP to that ticket was trying pre:
pre:
- setopt clobber
- source ~/projects/auv/devel/setup.zsh
- stt
and getting this error:
> mux start auv-core
sh: 13: setopt: not found
sh: 13: source: not found
sh: 13: stt: not found
arranging in: main-vertical
arranging in: main-vertical
[exited]
and one of the developers says this:
Things like setopt, source and alias are all built in shell commands and don't make sense in a shell script.
Your only option would be to put them in pre_window so send-keys is used in each window / pane.
Based on this comment I think your only option is to use pre_window: as you're doing. You might want to take a different tactic rather than list all the aliases in a pre_window: directly, put them in a file:
$ cat ~/my_aliases
alias cc=heh/path/that
alias ccc='cc clean; clear; cc'
alias selenium-restart=bin/docker/restart-selenium-chrome
alias yii=bin/docker/yii/yii
and have a pre_window: like this:
pre_window: source ~/my_aliases
But your approach looks consistent with how the project intends you to use pre_window: at the very least.
I didn't realize for some reason that I can put commands in separate list items forpre/pre_window, thanks!
â jojman
Aug 3 at 1:21
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases inpre_windowwork fine.
â jojman
Aug 3 at 1:23
@jojman - no you can put aliases inpre_windowyou can't put them inpreis what the thread stated.
â slmâ¦
Aug 3 at 1:26
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Based on this ticket in tmuxinator's issue tracker titled: "pre" option not using zsh options, alias, configuration (running as sh) #286 it looks like you'd either do it as a pre: or a pre_window:. The OP to that ticket was trying pre:
pre:
- setopt clobber
- source ~/projects/auv/devel/setup.zsh
- stt
and getting this error:
> mux start auv-core
sh: 13: setopt: not found
sh: 13: source: not found
sh: 13: stt: not found
arranging in: main-vertical
arranging in: main-vertical
[exited]
and one of the developers says this:
Things like setopt, source and alias are all built in shell commands and don't make sense in a shell script.
Your only option would be to put them in pre_window so send-keys is used in each window / pane.
Based on this comment I think your only option is to use pre_window: as you're doing. You might want to take a different tactic rather than list all the aliases in a pre_window: directly, put them in a file:
$ cat ~/my_aliases
alias cc=heh/path/that
alias ccc='cc clean; clear; cc'
alias selenium-restart=bin/docker/restart-selenium-chrome
alias yii=bin/docker/yii/yii
and have a pre_window: like this:
pre_window: source ~/my_aliases
But your approach looks consistent with how the project intends you to use pre_window: at the very least.
I didn't realize for some reason that I can put commands in separate list items forpre/pre_window, thanks!
â jojman
Aug 3 at 1:21
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases inpre_windowwork fine.
â jojman
Aug 3 at 1:23
@jojman - no you can put aliases inpre_windowyou can't put them inpreis what the thread stated.
â slmâ¦
Aug 3 at 1:26
add a comment |Â
up vote
1
down vote
accepted
Based on this ticket in tmuxinator's issue tracker titled: "pre" option not using zsh options, alias, configuration (running as sh) #286 it looks like you'd either do it as a pre: or a pre_window:. The OP to that ticket was trying pre:
pre:
- setopt clobber
- source ~/projects/auv/devel/setup.zsh
- stt
and getting this error:
> mux start auv-core
sh: 13: setopt: not found
sh: 13: source: not found
sh: 13: stt: not found
arranging in: main-vertical
arranging in: main-vertical
[exited]
and one of the developers says this:
Things like setopt, source and alias are all built in shell commands and don't make sense in a shell script.
Your only option would be to put them in pre_window so send-keys is used in each window / pane.
Based on this comment I think your only option is to use pre_window: as you're doing. You might want to take a different tactic rather than list all the aliases in a pre_window: directly, put them in a file:
$ cat ~/my_aliases
alias cc=heh/path/that
alias ccc='cc clean; clear; cc'
alias selenium-restart=bin/docker/restart-selenium-chrome
alias yii=bin/docker/yii/yii
and have a pre_window: like this:
pre_window: source ~/my_aliases
But your approach looks consistent with how the project intends you to use pre_window: at the very least.
I didn't realize for some reason that I can put commands in separate list items forpre/pre_window, thanks!
â jojman
Aug 3 at 1:21
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases inpre_windowwork fine.
â jojman
Aug 3 at 1:23
@jojman - no you can put aliases inpre_windowyou can't put them inpreis what the thread stated.
â slmâ¦
Aug 3 at 1:26
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Based on this ticket in tmuxinator's issue tracker titled: "pre" option not using zsh options, alias, configuration (running as sh) #286 it looks like you'd either do it as a pre: or a pre_window:. The OP to that ticket was trying pre:
pre:
- setopt clobber
- source ~/projects/auv/devel/setup.zsh
- stt
and getting this error:
> mux start auv-core
sh: 13: setopt: not found
sh: 13: source: not found
sh: 13: stt: not found
arranging in: main-vertical
arranging in: main-vertical
[exited]
and one of the developers says this:
Things like setopt, source and alias are all built in shell commands and don't make sense in a shell script.
Your only option would be to put them in pre_window so send-keys is used in each window / pane.
Based on this comment I think your only option is to use pre_window: as you're doing. You might want to take a different tactic rather than list all the aliases in a pre_window: directly, put them in a file:
$ cat ~/my_aliases
alias cc=heh/path/that
alias ccc='cc clean; clear; cc'
alias selenium-restart=bin/docker/restart-selenium-chrome
alias yii=bin/docker/yii/yii
and have a pre_window: like this:
pre_window: source ~/my_aliases
But your approach looks consistent with how the project intends you to use pre_window: at the very least.
Based on this ticket in tmuxinator's issue tracker titled: "pre" option not using zsh options, alias, configuration (running as sh) #286 it looks like you'd either do it as a pre: or a pre_window:. The OP to that ticket was trying pre:
pre:
- setopt clobber
- source ~/projects/auv/devel/setup.zsh
- stt
and getting this error:
> mux start auv-core
sh: 13: setopt: not found
sh: 13: source: not found
sh: 13: stt: not found
arranging in: main-vertical
arranging in: main-vertical
[exited]
and one of the developers says this:
Things like setopt, source and alias are all built in shell commands and don't make sense in a shell script.
Your only option would be to put them in pre_window so send-keys is used in each window / pane.
Based on this comment I think your only option is to use pre_window: as you're doing. You might want to take a different tactic rather than list all the aliases in a pre_window: directly, put them in a file:
$ cat ~/my_aliases
alias cc=heh/path/that
alias ccc='cc clean; clear; cc'
alias selenium-restart=bin/docker/restart-selenium-chrome
alias yii=bin/docker/yii/yii
and have a pre_window: like this:
pre_window: source ~/my_aliases
But your approach looks consistent with how the project intends you to use pre_window: at the very least.
answered Jul 30 at 2:32
slmâ¦
232k65479649
232k65479649
I didn't realize for some reason that I can put commands in separate list items forpre/pre_window, thanks!
â jojman
Aug 3 at 1:21
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases inpre_windowwork fine.
â jojman
Aug 3 at 1:23
@jojman - no you can put aliases inpre_windowyou can't put them inpreis what the thread stated.
â slmâ¦
Aug 3 at 1:26
add a comment |Â
I didn't realize for some reason that I can put commands in separate list items forpre/pre_window, thanks!
â jojman
Aug 3 at 1:21
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases inpre_windowwork fine.
â jojman
Aug 3 at 1:23
@jojman - no you can put aliases inpre_windowyou can't put them inpreis what the thread stated.
â slmâ¦
Aug 3 at 1:26
I didn't realize for some reason that I can put commands in separate list items for
pre/pre_window, thanks!â jojman
Aug 3 at 1:21
I didn't realize for some reason that I can put commands in separate list items for
pre/pre_window, thanks!â jojman
Aug 3 at 1:21
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases in
pre_window work fine.â jojman
Aug 3 at 1:23
By the way, what I'm doing is what your post suggests to be impossible. Bash aliases in
pre_window work fine.â jojman
Aug 3 at 1:23
@jojman - no you can put aliases in
pre_window you can't put them in pre is what the thread stated.â slmâ¦
Aug 3 at 1:26
@jojman - no you can put aliases in
pre_window you can't put them in pre is what the thread stated.â slmâ¦
Aug 3 at 1:26
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459236%2fwhere-to-define-shell-aliases-in-configs-for-projects-in-tmuxinator%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password