Run program from anywhere without changing directory
I wish to create an alias, which runs program x, without changing the current directory I am in. What I have now is:
alias x = "cd /home/path_to_x && ./x"
This works, but changes my directory. What I wish to do is something like:
alias x="./home/path_to_x/x
But then I get no such file or directory. Anyone know a workaround for this?
command-line alias
add a comment |
I wish to create an alias, which runs program x, without changing the current directory I am in. What I have now is:
alias x = "cd /home/path_to_x && ./x"
This works, but changes my directory. What I wish to do is something like:
alias x="./home/path_to_x/x
But then I get no such file or directory. Anyone know a workaround for this?
command-line alias
9
set an alias likealias x='/home/path_to_x/x'
. Don't use.
before/home
..
(dot) refers to current directory.
– souravc
Oct 15 '14 at 8:05
2
Doesx
really need to be run while being in/home/path_to_x
? Or are you just unsure about how to run a program residing in a specific directory?
– Adaephon
Oct 15 '14 at 8:47
possible duplicate of Execute command with relative (upper) path. Using another working directory
– c0rp
Oct 16 '14 at 6:26
One more similar question askubuntu.com/questions/427818/…
– c0rp
Oct 16 '14 at 6:29
add a comment |
I wish to create an alias, which runs program x, without changing the current directory I am in. What I have now is:
alias x = "cd /home/path_to_x && ./x"
This works, but changes my directory. What I wish to do is something like:
alias x="./home/path_to_x/x
But then I get no such file or directory. Anyone know a workaround for this?
command-line alias
I wish to create an alias, which runs program x, without changing the current directory I am in. What I have now is:
alias x = "cd /home/path_to_x && ./x"
This works, but changes my directory. What I wish to do is something like:
alias x="./home/path_to_x/x
But then I get no such file or directory. Anyone know a workaround for this?
command-line alias
command-line alias
edited Oct 15 '14 at 8:07
αғsнιη
24.9k23100161
24.9k23100161
asked Oct 15 '14 at 8:00
TheFishermanTheFisherman
183117
183117
9
set an alias likealias x='/home/path_to_x/x'
. Don't use.
before/home
..
(dot) refers to current directory.
– souravc
Oct 15 '14 at 8:05
2
Doesx
really need to be run while being in/home/path_to_x
? Or are you just unsure about how to run a program residing in a specific directory?
– Adaephon
Oct 15 '14 at 8:47
possible duplicate of Execute command with relative (upper) path. Using another working directory
– c0rp
Oct 16 '14 at 6:26
One more similar question askubuntu.com/questions/427818/…
– c0rp
Oct 16 '14 at 6:29
add a comment |
9
set an alias likealias x='/home/path_to_x/x'
. Don't use.
before/home
..
(dot) refers to current directory.
– souravc
Oct 15 '14 at 8:05
2
Doesx
really need to be run while being in/home/path_to_x
? Or are you just unsure about how to run a program residing in a specific directory?
– Adaephon
Oct 15 '14 at 8:47
possible duplicate of Execute command with relative (upper) path. Using another working directory
– c0rp
Oct 16 '14 at 6:26
One more similar question askubuntu.com/questions/427818/…
– c0rp
Oct 16 '14 at 6:29
9
9
set an alias like
alias x='/home/path_to_x/x'
. Don't use .
before /home
. .
(dot) refers to current directory.– souravc
Oct 15 '14 at 8:05
set an alias like
alias x='/home/path_to_x/x'
. Don't use .
before /home
. .
(dot) refers to current directory.– souravc
Oct 15 '14 at 8:05
2
2
Does
x
really need to be run while being in /home/path_to_x
? Or are you just unsure about how to run a program residing in a specific directory?– Adaephon
Oct 15 '14 at 8:47
Does
x
really need to be run while being in /home/path_to_x
? Or are you just unsure about how to run a program residing in a specific directory?– Adaephon
Oct 15 '14 at 8:47
possible duplicate of Execute command with relative (upper) path. Using another working directory
– c0rp
Oct 16 '14 at 6:26
possible duplicate of Execute command with relative (upper) path. Using another working directory
– c0rp
Oct 16 '14 at 6:26
One more similar question askubuntu.com/questions/427818/…
– c0rp
Oct 16 '14 at 6:29
One more similar question askubuntu.com/questions/427818/…
– c0rp
Oct 16 '14 at 6:29
add a comment |
5 Answers
5
active
oldest
votes
DON'T CD, just run it using its absolute path
This version:
cd /home/path_to_x && ./x
changes directory to an absolute path (you see how /home/...
starts at the root directory) and then runs the executable at the relative path ./x
(that is, relative to the new working directory).
This version:
./home/path_to_x/x
tries to run the executable at the relative path ./home/path_to_x/x
, which means relative to whatever your current working directory is now. That explains why you get the error - this relative path really doesn't exist.
The command you want would be:
/home/path_to_x/x
using the absolute path (starting at the root directory /
) again.
Oh, and you can also just add /home/path_to_x
to your PATH
instead of creating the alias. See: How to run scripts without typing the full path?
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
1
This would only be incorrect if the program needed to be run in a specific directory that it gets frompwd
– Kaz Wolfe
Oct 15 '14 at 23:06
@Whaaaaaat is right./home/path_to_x/x
is not functionally equivalent to(cd /home/path_to_x && ./x)
; if it works or not is application dependent.
– Rmano
Oct 16 '14 at 9:13
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
add a comment |
If you do not want the cd
to stick after the alias substitution, use a subshell with (
y )
:
alias my_x="(cd /home/path_to_x && ./x)&"
you can check it with
alias test_y="(cd /tmp && sleep 10 ) & "
Note that the solution
alias my_y="/home/path_to_x/x"
is not exactly equivalent. In fact, if called via my_x
, the x
program is run with a current directory /home/path_to_x/
, while if called by my_y
, x
is run with a current directory which is the one where the command my_y
was issued. This can be important or not depending on what x
is doing.
About the OP solution, it works in bash
:
romano@RRyS:~$ pwd
/home/romano
romano@RRyS:~$ alias x="cd /bin && ./echo A >/dev/null &"
romano@RRyS:~$ x
[1] 16611
romano@RRyS:~$ pwd
/home/romano
but not in zsh
:
[romano:~] % pwd
/home/romano
[romano:~] % alias x="cd /bin && ./echo A >/dev/null &"
[romano:~] % x
[1] 16744
[1] + 16744 done ./echo A > /dev/null
1& [romano:/bin] % pwd
/bin
[romano:/bin] %
It seems that bash and zsh execute lists in different ways ...so it's better to add the explicit parenthesis... thanks @EliahKagan for pointing it to me.
1
Giving the trailing&
higher precedence than&&
seems like it may be unique tozsh
. I triedsleep 5 && echo done &
inzsh
,bash
,ksh
,mksh
,dash
, and even one non-Bourne-style shell (tcsh
). Onlyzsh
evaluatedsleep 5
in the foreground; all the others returned immediately (then also printeddone
five seconds later, of course). On the other hand, even if this is entirely a peculiarity ofzsh
, I think adding explicit( )
(or{ ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).
– Eliah Kagan
Oct 15 '14 at 19:37
add a comment |
Putting a &
at the end seems to do the trick:
alias x = "cd /home/path_to_x && ./x &"
2
Are you sure? After executingx
you are in/home/path_to_x
. The&
at the end simply send the process in background.
– Rmano
Oct 15 '14 at 8:33
2
@Rmano This actually works.cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what&
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with( )
syntax, as you suggest, is probably a better solution most of the time though.)
– Eliah Kagan
Oct 15 '14 at 13:46
@EliahKagan you are right. I checked the solution withzsh
and effectively it works inbash
and not inzsh
... must be some difference in how the aliases are expanded.
– Rmano
Oct 15 '14 at 15:24
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
@Rmano did you enable the settings related topushd
inzsh
(I havesetopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)
– muru
Oct 15 '14 at 16:07
|
show 1 more comment
If the file which you want to run is already executeable, why don't you add it to you PATH variable?
If your executable file is /home/user/aplication/appX
just enter
PATH=$PATH:/home/user/application
to your ~/.bashrc
or ~/.profile
After restarting your console, you can run it simply with appX
I think this is the most clean solution.
add a comment |
Get Backup of your current pwd and and after running your command, undo your last pwd.
alias x='dwp=$(pwd) && cd /home/path_to_x && ./x && cd $dwp'
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).
– muru
Oct 15 '14 at 16:05
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,pushd
andpopd
do what your answer does.alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f537298%2frun-program-from-anywhere-without-changing-directory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
DON'T CD, just run it using its absolute path
This version:
cd /home/path_to_x && ./x
changes directory to an absolute path (you see how /home/...
starts at the root directory) and then runs the executable at the relative path ./x
(that is, relative to the new working directory).
This version:
./home/path_to_x/x
tries to run the executable at the relative path ./home/path_to_x/x
, which means relative to whatever your current working directory is now. That explains why you get the error - this relative path really doesn't exist.
The command you want would be:
/home/path_to_x/x
using the absolute path (starting at the root directory /
) again.
Oh, and you can also just add /home/path_to_x
to your PATH
instead of creating the alias. See: How to run scripts without typing the full path?
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
1
This would only be incorrect if the program needed to be run in a specific directory that it gets frompwd
– Kaz Wolfe
Oct 15 '14 at 23:06
@Whaaaaaat is right./home/path_to_x/x
is not functionally equivalent to(cd /home/path_to_x && ./x)
; if it works or not is application dependent.
– Rmano
Oct 16 '14 at 9:13
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
add a comment |
DON'T CD, just run it using its absolute path
This version:
cd /home/path_to_x && ./x
changes directory to an absolute path (you see how /home/...
starts at the root directory) and then runs the executable at the relative path ./x
(that is, relative to the new working directory).
This version:
./home/path_to_x/x
tries to run the executable at the relative path ./home/path_to_x/x
, which means relative to whatever your current working directory is now. That explains why you get the error - this relative path really doesn't exist.
The command you want would be:
/home/path_to_x/x
using the absolute path (starting at the root directory /
) again.
Oh, and you can also just add /home/path_to_x
to your PATH
instead of creating the alias. See: How to run scripts without typing the full path?
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
1
This would only be incorrect if the program needed to be run in a specific directory that it gets frompwd
– Kaz Wolfe
Oct 15 '14 at 23:06
@Whaaaaaat is right./home/path_to_x/x
is not functionally equivalent to(cd /home/path_to_x && ./x)
; if it works or not is application dependent.
– Rmano
Oct 16 '14 at 9:13
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
add a comment |
DON'T CD, just run it using its absolute path
This version:
cd /home/path_to_x && ./x
changes directory to an absolute path (you see how /home/...
starts at the root directory) and then runs the executable at the relative path ./x
(that is, relative to the new working directory).
This version:
./home/path_to_x/x
tries to run the executable at the relative path ./home/path_to_x/x
, which means relative to whatever your current working directory is now. That explains why you get the error - this relative path really doesn't exist.
The command you want would be:
/home/path_to_x/x
using the absolute path (starting at the root directory /
) again.
Oh, and you can also just add /home/path_to_x
to your PATH
instead of creating the alias. See: How to run scripts without typing the full path?
DON'T CD, just run it using its absolute path
This version:
cd /home/path_to_x && ./x
changes directory to an absolute path (you see how /home/...
starts at the root directory) and then runs the executable at the relative path ./x
(that is, relative to the new working directory).
This version:
./home/path_to_x/x
tries to run the executable at the relative path ./home/path_to_x/x
, which means relative to whatever your current working directory is now. That explains why you get the error - this relative path really doesn't exist.
The command you want would be:
/home/path_to_x/x
using the absolute path (starting at the root directory /
) again.
Oh, and you can also just add /home/path_to_x
to your PATH
instead of creating the alias. See: How to run scripts without typing the full path?
edited Feb 20 at 3:52
Olorin
1
1
answered Oct 15 '14 at 16:56
UselessUseless
29014
29014
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
1
This would only be incorrect if the program needed to be run in a specific directory that it gets frompwd
– Kaz Wolfe
Oct 15 '14 at 23:06
@Whaaaaaat is right./home/path_to_x/x
is not functionally equivalent to(cd /home/path_to_x && ./x)
; if it works or not is application dependent.
– Rmano
Oct 16 '14 at 9:13
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
add a comment |
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
1
This would only be incorrect if the program needed to be run in a specific directory that it gets frompwd
– Kaz Wolfe
Oct 15 '14 at 23:06
@Whaaaaaat is right./home/path_to_x/x
is not functionally equivalent to(cd /home/path_to_x && ./x)
; if it works or not is application dependent.
– Rmano
Oct 16 '14 at 9:13
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
This is the correct answer for the question as posed.
– Dennis Williamson
Oct 15 '14 at 21:34
1
1
This would only be incorrect if the program needed to be run in a specific directory that it gets from
pwd
– Kaz Wolfe
Oct 15 '14 at 23:06
This would only be incorrect if the program needed to be run in a specific directory that it gets from
pwd
– Kaz Wolfe
Oct 15 '14 at 23:06
@Whaaaaaat is right.
/home/path_to_x/x
is not functionally equivalent to (cd /home/path_to_x && ./x)
; if it works or not is application dependent.– Rmano
Oct 16 '14 at 9:13
@Whaaaaaat is right.
/home/path_to_x/x
is not functionally equivalent to (cd /home/path_to_x && ./x)
; if it works or not is application dependent.– Rmano
Oct 16 '14 at 9:13
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
Although you're right in general, for this specific question OP was visibly trying to run from the absolute path (just with a one-character mistake). However, I'm sure they can clarify if working directory is important in this case.
– Useless
Oct 16 '14 at 10:24
add a comment |
If you do not want the cd
to stick after the alias substitution, use a subshell with (
y )
:
alias my_x="(cd /home/path_to_x && ./x)&"
you can check it with
alias test_y="(cd /tmp && sleep 10 ) & "
Note that the solution
alias my_y="/home/path_to_x/x"
is not exactly equivalent. In fact, if called via my_x
, the x
program is run with a current directory /home/path_to_x/
, while if called by my_y
, x
is run with a current directory which is the one where the command my_y
was issued. This can be important or not depending on what x
is doing.
About the OP solution, it works in bash
:
romano@RRyS:~$ pwd
/home/romano
romano@RRyS:~$ alias x="cd /bin && ./echo A >/dev/null &"
romano@RRyS:~$ x
[1] 16611
romano@RRyS:~$ pwd
/home/romano
but not in zsh
:
[romano:~] % pwd
/home/romano
[romano:~] % alias x="cd /bin && ./echo A >/dev/null &"
[romano:~] % x
[1] 16744
[1] + 16744 done ./echo A > /dev/null
1& [romano:/bin] % pwd
/bin
[romano:/bin] %
It seems that bash and zsh execute lists in different ways ...so it's better to add the explicit parenthesis... thanks @EliahKagan for pointing it to me.
1
Giving the trailing&
higher precedence than&&
seems like it may be unique tozsh
. I triedsleep 5 && echo done &
inzsh
,bash
,ksh
,mksh
,dash
, and even one non-Bourne-style shell (tcsh
). Onlyzsh
evaluatedsleep 5
in the foreground; all the others returned immediately (then also printeddone
five seconds later, of course). On the other hand, even if this is entirely a peculiarity ofzsh
, I think adding explicit( )
(or{ ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).
– Eliah Kagan
Oct 15 '14 at 19:37
add a comment |
If you do not want the cd
to stick after the alias substitution, use a subshell with (
y )
:
alias my_x="(cd /home/path_to_x && ./x)&"
you can check it with
alias test_y="(cd /tmp && sleep 10 ) & "
Note that the solution
alias my_y="/home/path_to_x/x"
is not exactly equivalent. In fact, if called via my_x
, the x
program is run with a current directory /home/path_to_x/
, while if called by my_y
, x
is run with a current directory which is the one where the command my_y
was issued. This can be important or not depending on what x
is doing.
About the OP solution, it works in bash
:
romano@RRyS:~$ pwd
/home/romano
romano@RRyS:~$ alias x="cd /bin && ./echo A >/dev/null &"
romano@RRyS:~$ x
[1] 16611
romano@RRyS:~$ pwd
/home/romano
but not in zsh
:
[romano:~] % pwd
/home/romano
[romano:~] % alias x="cd /bin && ./echo A >/dev/null &"
[romano:~] % x
[1] 16744
[1] + 16744 done ./echo A > /dev/null
1& [romano:/bin] % pwd
/bin
[romano:/bin] %
It seems that bash and zsh execute lists in different ways ...so it's better to add the explicit parenthesis... thanks @EliahKagan for pointing it to me.
1
Giving the trailing&
higher precedence than&&
seems like it may be unique tozsh
. I triedsleep 5 && echo done &
inzsh
,bash
,ksh
,mksh
,dash
, and even one non-Bourne-style shell (tcsh
). Onlyzsh
evaluatedsleep 5
in the foreground; all the others returned immediately (then also printeddone
five seconds later, of course). On the other hand, even if this is entirely a peculiarity ofzsh
, I think adding explicit( )
(or{ ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).
– Eliah Kagan
Oct 15 '14 at 19:37
add a comment |
If you do not want the cd
to stick after the alias substitution, use a subshell with (
y )
:
alias my_x="(cd /home/path_to_x && ./x)&"
you can check it with
alias test_y="(cd /tmp && sleep 10 ) & "
Note that the solution
alias my_y="/home/path_to_x/x"
is not exactly equivalent. In fact, if called via my_x
, the x
program is run with a current directory /home/path_to_x/
, while if called by my_y
, x
is run with a current directory which is the one where the command my_y
was issued. This can be important or not depending on what x
is doing.
About the OP solution, it works in bash
:
romano@RRyS:~$ pwd
/home/romano
romano@RRyS:~$ alias x="cd /bin && ./echo A >/dev/null &"
romano@RRyS:~$ x
[1] 16611
romano@RRyS:~$ pwd
/home/romano
but not in zsh
:
[romano:~] % pwd
/home/romano
[romano:~] % alias x="cd /bin && ./echo A >/dev/null &"
[romano:~] % x
[1] 16744
[1] + 16744 done ./echo A > /dev/null
1& [romano:/bin] % pwd
/bin
[romano:/bin] %
It seems that bash and zsh execute lists in different ways ...so it's better to add the explicit parenthesis... thanks @EliahKagan for pointing it to me.
If you do not want the cd
to stick after the alias substitution, use a subshell with (
y )
:
alias my_x="(cd /home/path_to_x && ./x)&"
you can check it with
alias test_y="(cd /tmp && sleep 10 ) & "
Note that the solution
alias my_y="/home/path_to_x/x"
is not exactly equivalent. In fact, if called via my_x
, the x
program is run with a current directory /home/path_to_x/
, while if called by my_y
, x
is run with a current directory which is the one where the command my_y
was issued. This can be important or not depending on what x
is doing.
About the OP solution, it works in bash
:
romano@RRyS:~$ pwd
/home/romano
romano@RRyS:~$ alias x="cd /bin && ./echo A >/dev/null &"
romano@RRyS:~$ x
[1] 16611
romano@RRyS:~$ pwd
/home/romano
but not in zsh
:
[romano:~] % pwd
/home/romano
[romano:~] % alias x="cd /bin && ./echo A >/dev/null &"
[romano:~] % x
[1] 16744
[1] + 16744 done ./echo A > /dev/null
1& [romano:/bin] % pwd
/bin
[romano:/bin] %
It seems that bash and zsh execute lists in different ways ...so it's better to add the explicit parenthesis... thanks @EliahKagan for pointing it to me.
edited Apr 13 '17 at 12:37
Community♦
1
1
answered Oct 15 '14 at 8:38
RmanoRmano
25.5k880147
25.5k880147
1
Giving the trailing&
higher precedence than&&
seems like it may be unique tozsh
. I triedsleep 5 && echo done &
inzsh
,bash
,ksh
,mksh
,dash
, and even one non-Bourne-style shell (tcsh
). Onlyzsh
evaluatedsleep 5
in the foreground; all the others returned immediately (then also printeddone
five seconds later, of course). On the other hand, even if this is entirely a peculiarity ofzsh
, I think adding explicit( )
(or{ ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).
– Eliah Kagan
Oct 15 '14 at 19:37
add a comment |
1
Giving the trailing&
higher precedence than&&
seems like it may be unique tozsh
. I triedsleep 5 && echo done &
inzsh
,bash
,ksh
,mksh
,dash
, and even one non-Bourne-style shell (tcsh
). Onlyzsh
evaluatedsleep 5
in the foreground; all the others returned immediately (then also printeddone
five seconds later, of course). On the other hand, even if this is entirely a peculiarity ofzsh
, I think adding explicit( )
(or{ ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).
– Eliah Kagan
Oct 15 '14 at 19:37
1
1
Giving the trailing
&
higher precedence than &&
seems like it may be unique to zsh
. I tried sleep 5 && echo done &
in zsh
, bash
, ksh
, mksh
, dash
, and even one non-Bourne-style shell (tcsh
). Only zsh
evaluated sleep 5
in the foreground; all the others returned immediately (then also printed done
five seconds later, of course). On the other hand, even if this is entirely a peculiarity of zsh
, I think adding explicit ( )
(or { ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).– Eliah Kagan
Oct 15 '14 at 19:37
Giving the trailing
&
higher precedence than &&
seems like it may be unique to zsh
. I tried sleep 5 && echo done &
in zsh
, bash
, ksh
, mksh
, dash
, and even one non-Bourne-style shell (tcsh
). Only zsh
evaluated sleep 5
in the foreground; all the others returned immediately (then also printed done
five seconds later, of course). On the other hand, even if this is entirely a peculiarity of zsh
, I think adding explicit ( )
(or { ;}
) is reasonable, as it conveys the intent to other humans (or to oneself, when reading the script or history later).– Eliah Kagan
Oct 15 '14 at 19:37
add a comment |
Putting a &
at the end seems to do the trick:
alias x = "cd /home/path_to_x && ./x &"
2
Are you sure? After executingx
you are in/home/path_to_x
. The&
at the end simply send the process in background.
– Rmano
Oct 15 '14 at 8:33
2
@Rmano This actually works.cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what&
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with( )
syntax, as you suggest, is probably a better solution most of the time though.)
– Eliah Kagan
Oct 15 '14 at 13:46
@EliahKagan you are right. I checked the solution withzsh
and effectively it works inbash
and not inzsh
... must be some difference in how the aliases are expanded.
– Rmano
Oct 15 '14 at 15:24
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
@Rmano did you enable the settings related topushd
inzsh
(I havesetopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)
– muru
Oct 15 '14 at 16:07
|
show 1 more comment
Putting a &
at the end seems to do the trick:
alias x = "cd /home/path_to_x && ./x &"
2
Are you sure? After executingx
you are in/home/path_to_x
. The&
at the end simply send the process in background.
– Rmano
Oct 15 '14 at 8:33
2
@Rmano This actually works.cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what&
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with( )
syntax, as you suggest, is probably a better solution most of the time though.)
– Eliah Kagan
Oct 15 '14 at 13:46
@EliahKagan you are right. I checked the solution withzsh
and effectively it works inbash
and not inzsh
... must be some difference in how the aliases are expanded.
– Rmano
Oct 15 '14 at 15:24
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
@Rmano did you enable the settings related topushd
inzsh
(I havesetopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)
– muru
Oct 15 '14 at 16:07
|
show 1 more comment
Putting a &
at the end seems to do the trick:
alias x = "cd /home/path_to_x && ./x &"
Putting a &
at the end seems to do the trick:
alias x = "cd /home/path_to_x && ./x &"
edited Oct 15 '14 at 13:48
Eliah Kagan
82.8k22228369
82.8k22228369
answered Oct 15 '14 at 8:05
TheFishermanTheFisherman
183117
183117
2
Are you sure? After executingx
you are in/home/path_to_x
. The&
at the end simply send the process in background.
– Rmano
Oct 15 '14 at 8:33
2
@Rmano This actually works.cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what&
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with( )
syntax, as you suggest, is probably a better solution most of the time though.)
– Eliah Kagan
Oct 15 '14 at 13:46
@EliahKagan you are right. I checked the solution withzsh
and effectively it works inbash
and not inzsh
... must be some difference in how the aliases are expanded.
– Rmano
Oct 15 '14 at 15:24
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
@Rmano did you enable the settings related topushd
inzsh
(I havesetopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)
– muru
Oct 15 '14 at 16:07
|
show 1 more comment
2
Are you sure? After executingx
you are in/home/path_to_x
. The&
at the end simply send the process in background.
– Rmano
Oct 15 '14 at 8:33
2
@Rmano This actually works.cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what&
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with( )
syntax, as you suggest, is probably a better solution most of the time though.)
– Eliah Kagan
Oct 15 '14 at 13:46
@EliahKagan you are right. I checked the solution withzsh
and effectively it works inbash
and not inzsh
... must be some difference in how the aliases are expanded.
– Rmano
Oct 15 '14 at 15:24
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
@Rmano did you enable the settings related topushd
inzsh
(I havesetopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)
– muru
Oct 15 '14 at 16:07
2
2
Are you sure? After executing
x
you are in /home/path_to_x
. The &
at the end simply send the process in background.– Rmano
Oct 15 '14 at 8:33
Are you sure? After executing
x
you are in /home/path_to_x
. The &
at the end simply send the process in background.– Rmano
Oct 15 '14 at 8:33
2
2
@Rmano This actually works.
cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what &
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with ( )
syntax, as you suggest, is probably a better solution most of the time though.)– Eliah Kagan
Oct 15 '14 at 13:46
@Rmano This actually works.
cd
s in background jobs don't affect the caller (which makes sense--it'd be really weird if they did). This is because asynchronous execution uses a subshell. Though this would be better if it explained why it works and what &
does--and how running in the background is sometimes undesirable--this is (already) a correct answer. (Explicitly making a subshell with ( )
syntax, as you suggest, is probably a better solution most of the time though.)– Eliah Kagan
Oct 15 '14 at 13:46
@EliahKagan you are right. I checked the solution with
zsh
and effectively it works in bash
and not in zsh
... must be some difference in how the aliases are expanded.– Rmano
Oct 15 '14 at 15:24
@EliahKagan you are right. I checked the solution with
zsh
and effectively it works in bash
and not in zsh
... must be some difference in how the aliases are expanded.– Rmano
Oct 15 '14 at 15:24
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
Asked a question: unix.stackexchange.com/questions/162286/…
– Rmano
Oct 15 '14 at 15:42
@Rmano did you enable the settings related to
pushd
in zsh
(I have setopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)– muru
Oct 15 '14 at 16:07
@Rmano did you enable the settings related to
pushd
in zsh
(I have setopt autopushd pushdsilent pushdtohome
, and it remembers my cwd.)– muru
Oct 15 '14 at 16:07
|
show 1 more comment
If the file which you want to run is already executeable, why don't you add it to you PATH variable?
If your executable file is /home/user/aplication/appX
just enter
PATH=$PATH:/home/user/application
to your ~/.bashrc
or ~/.profile
After restarting your console, you can run it simply with appX
I think this is the most clean solution.
add a comment |
If the file which you want to run is already executeable, why don't you add it to you PATH variable?
If your executable file is /home/user/aplication/appX
just enter
PATH=$PATH:/home/user/application
to your ~/.bashrc
or ~/.profile
After restarting your console, you can run it simply with appX
I think this is the most clean solution.
add a comment |
If the file which you want to run is already executeable, why don't you add it to you PATH variable?
If your executable file is /home/user/aplication/appX
just enter
PATH=$PATH:/home/user/application
to your ~/.bashrc
or ~/.profile
After restarting your console, you can run it simply with appX
I think this is the most clean solution.
If the file which you want to run is already executeable, why don't you add it to you PATH variable?
If your executable file is /home/user/aplication/appX
just enter
PATH=$PATH:/home/user/application
to your ~/.bashrc
or ~/.profile
After restarting your console, you can run it simply with appX
I think this is the most clean solution.
edited Oct 16 '14 at 10:58
answered Oct 15 '14 at 17:11
0xAffe0xAffe
26718
26718
add a comment |
add a comment |
Get Backup of your current pwd and and after running your command, undo your last pwd.
alias x='dwp=$(pwd) && cd /home/path_to_x && ./x && cd $dwp'
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).
– muru
Oct 15 '14 at 16:05
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,pushd
andpopd
do what your answer does.alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
add a comment |
Get Backup of your current pwd and and after running your command, undo your last pwd.
alias x='dwp=$(pwd) && cd /home/path_to_x && ./x && cd $dwp'
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).
– muru
Oct 15 '14 at 16:05
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,pushd
andpopd
do what your answer does.alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
add a comment |
Get Backup of your current pwd and and after running your command, undo your last pwd.
alias x='dwp=$(pwd) && cd /home/path_to_x && ./x && cd $dwp'
Get Backup of your current pwd and and after running your command, undo your last pwd.
alias x='dwp=$(pwd) && cd /home/path_to_x && ./x && cd $dwp'
edited Oct 16 '14 at 5:58
answered Oct 15 '14 at 15:57
αғsнιηαғsнιη
24.9k23100161
24.9k23100161
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).
– muru
Oct 15 '14 at 16:05
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,pushd
andpopd
do what your answer does.alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
add a comment |
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).
– muru
Oct 15 '14 at 16:05
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,pushd
andpopd
do what your answer does.alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (
test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).– muru
Oct 15 '14 at 16:05
You misunderstood the effect of that Rmano's alias. The command line is not blocked. It's just that the output of the alias (
test
) pushed the cursor to the next line. You can still do whatever you want there (including pressing enter to open a fresh new prompt).– muru
Oct 15 '14 at 16:05
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
yup, yes correct. @mure :|
– αғsнιη
Oct 15 '14 at 16:07
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,
pushd
and popd
do what your answer does. alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
Note that since you use double quotes the variable will include the current directory at the time the alias is defined. Use single quotes to defer evaluation until the alias is expanded. However,
pushd
and popd
do what your answer does. alias x='pushd /home/path_to_x && ./x && popd'
– Dennis Williamson
Oct 15 '14 at 21:39
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f537298%2frun-program-from-anywhere-without-changing-directory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
9
set an alias like
alias x='/home/path_to_x/x'
. Don't use.
before/home
..
(dot) refers to current directory.– souravc
Oct 15 '14 at 8:05
2
Does
x
really need to be run while being in/home/path_to_x
? Or are you just unsure about how to run a program residing in a specific directory?– Adaephon
Oct 15 '14 at 8:47
possible duplicate of Execute command with relative (upper) path. Using another working directory
– c0rp
Oct 16 '14 at 6:26
One more similar question askubuntu.com/questions/427818/…
– c0rp
Oct 16 '14 at 6:29