Script to change current directory (cd, pwd)

I want to run a script to simply change the current working directory:

#!/bin/bash

cd web/www/project

But, after I run it, the current pwd remains unchanged! How can I do that?

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

asked Dec 19 '11 at 7:55

Sony Santos

268137

Can your provide more information? Some thing like your directory structure, or the context...

– favadi
Dec 19 '11 at 8:06

2

This is a rite of passage problem

– zzapper
Aug 25 '16 at 11:41

1

Heh. You cracked me up, @zzapper

– SDsolar
Jul 24 '17 at 15:16

add a comment |

I want to run a script to simply change the current working directory:

#!/bin/bash

cd web/www/project

But, after I run it, the current pwd remains unchanged! How can I do that?

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

asked Dec 19 '11 at 7:55

Sony Santos

268137

Can your provide more information? Some thing like your directory structure, or the context...

– favadi
Dec 19 '11 at 8:06

2

This is a rite of passage problem

– zzapper
Aug 25 '16 at 11:41

1

Heh. You cracked me up, @zzapper

– SDsolar
Jul 24 '17 at 15:16

add a comment |

I want to run a script to simply change the current working directory:

#!/bin/bash

cd web/www/project

But, after I run it, the current pwd remains unchanged! How can I do that?

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

asked Dec 19 '11 at 7:55

Sony Santos

268137

I want to run a script to simply change the current working directory:

#!/bin/bash

cd web/www/project

But, after I run it, the current pwd remains unchanged! How can I do that?

bash scripting environment-variables cd-command

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

asked Dec 19 '11 at 7:55

Sony Santos

268137

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

asked Dec 19 '11 at 7:55

Sony Santos

268137

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

edited Dec 19 '11 at 20:44

Sachin Divekar

3,92811719

asked Dec 19 '11 at 7:55

Sony Santos

268137

asked Dec 19 '11 at 7:55

Sony Santos

268137

asked Dec 19 '11 at 7:55

Sony Santos

268137

Can your provide more information? Some thing like your directory structure, or the context...

– favadi
Dec 19 '11 at 8:06

2

This is a rite of passage problem

– zzapper
Aug 25 '16 at 11:41

1

Heh. You cracked me up, @zzapper

– SDsolar
Jul 24 '17 at 15:16

add a comment |

Can your provide more information? Some thing like your directory structure, or the context...

– favadi
Dec 19 '11 at 8:06

2

This is a rite of passage problem

– zzapper
Aug 25 '16 at 11:41

1

Heh. You cracked me up, @zzapper

– SDsolar
Jul 24 '17 at 15:16

Can your provide more information? Some thing like your directory structure, or the context...

– favadi
Dec 19 '11 at 8:06

This is a rite of passage problem

– zzapper
Aug 25 '16 at 11:41

Heh. You cracked me up, @zzapper

– SDsolar
Jul 24 '17 at 15:16

add a comment |

6 Answers
6

active

oldest

votes

It is an expected behavior, and already discussed several times.

The script is run in a subshell, and cannot change the parent shell working directory. Its effects are lost when it finishes.

To change directory permanently you should source the script, as in

. ./script

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

8

@Sony: Note that you should use return to escape from a script sourced in this way, not exit - they are like shell functions, and exit will exit the shell that sourced the script.

– Charles Stewart
Dec 19 '11 at 8:19

@CharlesStewart In fact, I'm not familiar with sourced scripts. Thank you!

– Sony Santos
Dec 19 '11 at 12:56

5

is source ./script the same?

– amyassin
Dec 19 '11 at 13:04

2

@amyassin: yes, it is

– enzotib
Dec 19 '11 at 13:05

2

1. . and source are equal in bash. 2. we don't need to use ./ before filename if it's in the same directory. It is ok to run only this: . script

– sobi3ch
Jun 16 '16 at 15:02

|
show 2 more comments

For small tasks such as this, instead of creating script, create an alias like this,

$ alias cdproj='cd /dir/web/www/proj'

You should add this to your .bashrc file, if you want it set for every interactive shell.

Now you can run this as $ cdproj.

edited Dec 19 '11 at 20:42

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

That's a good tip! I'll consider to use it for some tasks. Thank you! :)

– Sony Santos
Dec 19 '11 at 20:26

1

You can also have the script echo the commands to be executed, and then use eval `./script` or eval $(./script) to execute those commands. This is a common approach for commands that need to update the invoking shell's environment.

– Keith Thompson
Dec 20 '11 at 10:41

2

Just be very careful about what you output if you are going to go the eval approach.

– jw013
Sep 14 '12 at 20:08

add a comment |

While there are answers that do the exact action that you want, a more standard method for such purpose is to create symbolic link:

ln -s ~/web/www/project proj   #use full path to dir!

Then you could cd to the directory using the name proj:

cd proj

This method is more flexible because you could access files using the short name without cd:

ls proj/   #note the endslash!

vim proj/file.x

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

answered Dec 22 '11 at 14:25

corvinus

1462

add a comment |

Use `exec bash` at the end

A bash script operates on its current environment or on that of its
children, but never on its parent environment.

However, this question often gets asked because one wants to be left at the bash prompt in a certain directory after the execution of a bash script from another directory.

If this is the case, simply execute a child bash instance at the end of the script:

#!/bin/bash

cd desired/directory

exec bash

edited 3 hours ago

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

You are a genius!

– Kasper
Aug 15 '16 at 3:05

Better to just source the script, as in accepted answer: using exec is typically considered the last resort of a scoundrel.. :)

– neuronet
Aug 16 '16 at 0:18

this trick doesn't work in debian 9 stretch.

– vdegenne
May 5 '18 at 0:41

This is the wrong way to go about this!

– Dennis Williamson
4 hours ago

add a comment |

If you change between directories far away in the filesystem. I will recommend autojump.

answered Dec 23 '11 at 2:30

stnly

34624

add a comment |

Depends on what you're going to do, another solution can be creating a function instead of a script.

Example:

Create a function in a file, let's say /home/aidin/my-cd-script:

function my-cd() {

  cd /to/my/path

}

Then include it in your bashrc or zshrc file:

# Somewhere in rc file

source /home/aidin/my-cd-script

Now you can use it like a command:

$ my-cd

edited Jun 20 '18 at 1:36

muru

answered Jun 20 '18 at 0:59

Aidin

1943

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f27139%2fscript-to-change-current-directory-cd-pwd%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

6 Answers
6

active

oldest

votes

6 Answers
6

active

oldest

votes

It is an expected behavior, and already discussed several times.

The script is run in a subshell, and cannot change the parent shell working directory. Its effects are lost when it finishes.

To change directory permanently you should source the script, as in

. ./script

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

8

@Sony: Note that you should use return to escape from a script sourced in this way, not exit - they are like shell functions, and exit will exit the shell that sourced the script.

– Charles Stewart
Dec 19 '11 at 8:19

@CharlesStewart In fact, I'm not familiar with sourced scripts. Thank you!

– Sony Santos
Dec 19 '11 at 12:56

5

is source ./script the same?

– amyassin
Dec 19 '11 at 13:04

2

@amyassin: yes, it is

– enzotib
Dec 19 '11 at 13:05

2

1. . and source are equal in bash. 2. we don't need to use ./ before filename if it's in the same directory. It is ok to run only this: . script

– sobi3ch
Jun 16 '16 at 15:02

|
show 2 more comments

It is an expected behavior, and already discussed several times.

The script is run in a subshell, and cannot change the parent shell working directory. Its effects are lost when it finishes.

To change directory permanently you should source the script, as in

. ./script

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

8

@Sony: Note that you should use return to escape from a script sourced in this way, not exit - they are like shell functions, and exit will exit the shell that sourced the script.

– Charles Stewart
Dec 19 '11 at 8:19

@CharlesStewart In fact, I'm not familiar with sourced scripts. Thank you!

– Sony Santos
Dec 19 '11 at 12:56

5

is source ./script the same?

– amyassin
Dec 19 '11 at 13:04

2

@amyassin: yes, it is

– enzotib
Dec 19 '11 at 13:05

2

1. . and source are equal in bash. 2. we don't need to use ./ before filename if it's in the same directory. It is ok to run only this: . script

– sobi3ch
Jun 16 '16 at 15:02

|
show 2 more comments

It is an expected behavior, and already discussed several times.

The script is run in a subshell, and cannot change the parent shell working directory. Its effects are lost when it finishes.

To change directory permanently you should source the script, as in

. ./script

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

It is an expected behavior, and already discussed several times.

The script is run in a subshell, and cannot change the parent shell working directory. Its effects are lost when it finishes.

To change directory permanently you should source the script, as in

. ./script

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

edited Dec 19 '11 at 15:31

Tomasz Nurkiewicz

1032

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

answered Dec 19 '11 at 8:13

enzotib

34.4k710395

8

@Sony: Note that you should use return to escape from a script sourced in this way, not exit - they are like shell functions, and exit will exit the shell that sourced the script.

– Charles Stewart
Dec 19 '11 at 8:19

@CharlesStewart In fact, I'm not familiar with sourced scripts. Thank you!

– Sony Santos
Dec 19 '11 at 12:56

5

is source ./script the same?

– amyassin
Dec 19 '11 at 13:04

2

@amyassin: yes, it is

– enzotib
Dec 19 '11 at 13:05

2

1. . and source are equal in bash. 2. we don't need to use ./ before filename if it's in the same directory. It is ok to run only this: . script

– sobi3ch
Jun 16 '16 at 15:02

|
show 2 more comments

8

@Sony: Note that you should use return to escape from a script sourced in this way, not exit - they are like shell functions, and exit will exit the shell that sourced the script.

– Charles Stewart
Dec 19 '11 at 8:19

@CharlesStewart In fact, I'm not familiar with sourced scripts. Thank you!

– Sony Santos
Dec 19 '11 at 12:56

5

is source ./script the same?

– amyassin
Dec 19 '11 at 13:04

2

@amyassin: yes, it is

– enzotib
Dec 19 '11 at 13:05

2

1. . and source are equal in bash. 2. we don't need to use ./ before filename if it's in the same directory. It is ok to run only this: . script

– sobi3ch
Jun 16 '16 at 15:02

@Sony: Note that you should use return to escape from a script sourced in this way, not exit - they are like shell functions, and exit will exit the shell that sourced the script.

– Charles Stewart
Dec 19 '11 at 8:19

@CharlesStewart In fact, I'm not familiar with sourced scripts. Thank you!

– Sony Santos
Dec 19 '11 at 12:56

is source ./script the same?

– amyassin
Dec 19 '11 at 13:04

@amyassin: yes, it is

– enzotib
Dec 19 '11 at 13:05

1. . and source are equal in bash. 2. we don't need to use ./ before filename if it's in the same directory. It is ok to run only this: . script

– sobi3ch
Jun 16 '16 at 15:02

|
show 2 more comments

For small tasks such as this, instead of creating script, create an alias like this,

$ alias cdproj='cd /dir/web/www/proj'

You should add this to your .bashrc file, if you want it set for every interactive shell.

Now you can run this as $ cdproj.

edited Dec 19 '11 at 20:42

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

That's a good tip! I'll consider to use it for some tasks. Thank you! :)

– Sony Santos
Dec 19 '11 at 20:26

1

You can also have the script echo the commands to be executed, and then use eval `./script` or eval $(./script) to execute those commands. This is a common approach for commands that need to update the invoking shell's environment.

– Keith Thompson
Dec 20 '11 at 10:41

2

Just be very careful about what you output if you are going to go the eval approach.

– jw013
Sep 14 '12 at 20:08

add a comment |

For small tasks such as this, instead of creating script, create an alias like this,

$ alias cdproj='cd /dir/web/www/proj'

You should add this to your .bashrc file, if you want it set for every interactive shell.

Now you can run this as $ cdproj.

edited Dec 19 '11 at 20:42

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

That's a good tip! I'll consider to use it for some tasks. Thank you! :)

– Sony Santos
Dec 19 '11 at 20:26

1

You can also have the script echo the commands to be executed, and then use eval `./script` or eval $(./script) to execute those commands. This is a common approach for commands that need to update the invoking shell's environment.

– Keith Thompson
Dec 20 '11 at 10:41

2

Just be very careful about what you output if you are going to go the eval approach.

– jw013
Sep 14 '12 at 20:08

add a comment |

For small tasks such as this, instead of creating script, create an alias like this,

$ alias cdproj='cd /dir/web/www/proj'

You should add this to your .bashrc file, if you want it set for every interactive shell.

Now you can run this as $ cdproj.

edited Dec 19 '11 at 20:42

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

For small tasks such as this, instead of creating script, create an alias like this,

$ alias cdproj='cd /dir/web/www/proj'

You should add this to your .bashrc file, if you want it set for every interactive shell.

Now you can run this as $ cdproj.

edited Dec 19 '11 at 20:42

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

edited Dec 19 '11 at 20:42

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

answered Dec 19 '11 at 14:12

Sachin Divekar

3,92811719

That's a good tip! I'll consider to use it for some tasks. Thank you! :)

– Sony Santos
Dec 19 '11 at 20:26

1

You can also have the script echo the commands to be executed, and then use eval `./script` or eval $(./script) to execute those commands. This is a common approach for commands that need to update the invoking shell's environment.

– Keith Thompson
Dec 20 '11 at 10:41

2

Just be very careful about what you output if you are going to go the eval approach.

– jw013
Sep 14 '12 at 20:08

add a comment |

That's a good tip! I'll consider to use it for some tasks. Thank you! :)

– Sony Santos
Dec 19 '11 at 20:26

1

You can also have the script echo the commands to be executed, and then use eval `./script` or eval $(./script) to execute those commands. This is a common approach for commands that need to update the invoking shell's environment.

– Keith Thompson
Dec 20 '11 at 10:41

2

Just be very careful about what you output if you are going to go the eval approach.

– jw013
Sep 14 '12 at 20:08

That's a good tip! I'll consider to use it for some tasks. Thank you! :)

– Sony Santos
Dec 19 '11 at 20:26

You can also have the script echo the commands to be executed, and then use eval `./script` or eval $(./script) to execute those commands. This is a common approach for commands that need to update the invoking shell's environment.

– Keith Thompson
Dec 20 '11 at 10:41

Just be very careful about what you output if you are going to go the eval approach.

– jw013
Sep 14 '12 at 20:08

add a comment |

While there are answers that do the exact action that you want, a more standard method for such purpose is to create symbolic link:

ln -s ~/web/www/project proj   #use full path to dir!

Then you could cd to the directory using the name proj:

cd proj

This method is more flexible because you could access files using the short name without cd:

ls proj/   #note the endslash!

vim proj/file.x

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

answered Dec 22 '11 at 14:25

corvinus

1462

add a comment |

While there are answers that do the exact action that you want, a more standard method for such purpose is to create symbolic link:

ln -s ~/web/www/project proj   #use full path to dir!

Then you could cd to the directory using the name proj:

cd proj

This method is more flexible because you could access files using the short name without cd:

ls proj/   #note the endslash!

vim proj/file.x

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

answered Dec 22 '11 at 14:25

corvinus

1462

add a comment |

While there are answers that do the exact action that you want, a more standard method for such purpose is to create symbolic link:

ln -s ~/web/www/project proj   #use full path to dir!

Then you could cd to the directory using the name proj:

cd proj

This method is more flexible because you could access files using the short name without cd:

ls proj/   #note the endslash!

vim proj/file.x

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

answered Dec 22 '11 at 14:25

corvinus

1462

While there are answers that do the exact action that you want, a more standard method for such purpose is to create symbolic link:

ln -s ~/web/www/project proj   #use full path to dir!

Then you could cd to the directory using the name proj:

cd proj

This method is more flexible because you could access files using the short name without cd:

ls proj/   #note the endslash!

vim proj/file.x

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

answered Dec 22 '11 at 14:25

corvinus

1462

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

edited Jan 28 '12 at 18:20

Kevin

27.6k1065103

answered Dec 22 '11 at 14:25

corvinus

1462

answered Dec 22 '11 at 14:25

corvinus

1462

answered Dec 22 '11 at 14:25

corvinus

1462

add a comment |

Use `exec bash` at the end

A bash script operates on its current environment or on that of its
children, but never on its parent environment.

However, this question often gets asked because one wants to be left at the bash prompt in a certain directory after the execution of a bash script from another directory.

If this is the case, simply execute a child bash instance at the end of the script:

#!/bin/bash

cd desired/directory

exec bash

edited 3 hours ago

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

You are a genius!

– Kasper
Aug 15 '16 at 3:05

Better to just source the script, as in accepted answer: using exec is typically considered the last resort of a scoundrel.. :)

– neuronet
Aug 16 '16 at 0:18

this trick doesn't work in debian 9 stretch.

– vdegenne
May 5 '18 at 0:41

This is the wrong way to go about this!

– Dennis Williamson
4 hours ago

add a comment |

Use `exec bash` at the end

A bash script operates on its current environment or on that of its
children, but never on its parent environment.

However, this question often gets asked because one wants to be left at the bash prompt in a certain directory after the execution of a bash script from another directory.

If this is the case, simply execute a child bash instance at the end of the script:

#!/bin/bash

cd desired/directory

exec bash

edited 3 hours ago

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

You are a genius!

– Kasper
Aug 15 '16 at 3:05

Better to just source the script, as in accepted answer: using exec is typically considered the last resort of a scoundrel.. :)

– neuronet
Aug 16 '16 at 0:18

this trick doesn't work in debian 9 stretch.

– vdegenne
May 5 '18 at 0:41

This is the wrong way to go about this!

– Dennis Williamson
4 hours ago

add a comment |

Use `exec bash` at the end

A bash script operates on its current environment or on that of its
children, but never on its parent environment.

However, this question often gets asked because one wants to be left at the bash prompt in a certain directory after the execution of a bash script from another directory.

If this is the case, simply execute a child bash instance at the end of the script:

#!/bin/bash

cd desired/directory

exec bash

edited 3 hours ago

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

Use `exec bash` at the end

A bash script operates on its current environment or on that of its
children, but never on its parent environment.

However, this question often gets asked because one wants to be left at the bash prompt in a certain directory after the execution of a bash script from another directory.

If this is the case, simply execute a child bash instance at the end of the script:

#!/bin/bash

cd desired/directory

exec bash

edited 3 hours ago

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

edited 3 hours ago

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

answered Apr 21 '16 at 11:36

Serge Stroobandt

84321327

You are a genius!

– Kasper
Aug 15 '16 at 3:05

Better to just source the script, as in accepted answer: using exec is typically considered the last resort of a scoundrel.. :)

– neuronet
Aug 16 '16 at 0:18

this trick doesn't work in debian 9 stretch.

– vdegenne
May 5 '18 at 0:41

This is the wrong way to go about this!

– Dennis Williamson
4 hours ago

add a comment |

You are a genius!

– Kasper
Aug 15 '16 at 3:05

Better to just source the script, as in accepted answer: using exec is typically considered the last resort of a scoundrel.. :)

– neuronet
Aug 16 '16 at 0:18

this trick doesn't work in debian 9 stretch.

– vdegenne
May 5 '18 at 0:41

This is the wrong way to go about this!

– Dennis Williamson
4 hours ago

You are a genius!

– Kasper
Aug 15 '16 at 3:05

Better to just source the script, as in accepted answer: using exec is typically considered the last resort of a scoundrel.. :)

– neuronet
Aug 16 '16 at 0:18

this trick doesn't work in debian 9 stretch.

– vdegenne
May 5 '18 at 0:41

This is the wrong way to go about this!

– Dennis Williamson
4 hours ago

add a comment |

If you change between directories far away in the filesystem. I will recommend autojump.

answered Dec 23 '11 at 2:30

stnly

34624

add a comment |

If you change between directories far away in the filesystem. I will recommend autojump.

answered Dec 23 '11 at 2:30

stnly

34624

add a comment |

If you change between directories far away in the filesystem. I will recommend autojump.

answered Dec 23 '11 at 2:30

stnly

34624

If you change between directories far away in the filesystem. I will recommend autojump.

answered Dec 23 '11 at 2:30

stnly

34624

answered Dec 23 '11 at 2:30

stnly

34624

answered Dec 23 '11 at 2:30

stnly

34624

answered Dec 23 '11 at 2:30

stnly

34624

add a comment |

Depends on what you're going to do, another solution can be creating a function instead of a script.

Example:

Create a function in a file, let's say /home/aidin/my-cd-script:

function my-cd() {

  cd /to/my/path

}

Then include it in your bashrc or zshrc file:

# Somewhere in rc file

source /home/aidin/my-cd-script

Now you can use it like a command:

$ my-cd

edited Jun 20 '18 at 1:36

muru

answered Jun 20 '18 at 0:59

Aidin

1943

add a comment |

Depends on what you're going to do, another solution can be creating a function instead of a script.

Example:

Create a function in a file, let's say /home/aidin/my-cd-script:

function my-cd() {

  cd /to/my/path

}

Then include it in your bashrc or zshrc file:

# Somewhere in rc file

source /home/aidin/my-cd-script

Now you can use it like a command:

$ my-cd

edited Jun 20 '18 at 1:36

muru

answered Jun 20 '18 at 0:59

Aidin

1943

add a comment |

Depends on what you're going to do, another solution can be creating a function instead of a script.

Example:

Create a function in a file, let's say /home/aidin/my-cd-script:

function my-cd() {

  cd /to/my/path

}

Then include it in your bashrc or zshrc file:

# Somewhere in rc file

source /home/aidin/my-cd-script

Now you can use it like a command:

$ my-cd

edited Jun 20 '18 at 1:36

muru

answered Jun 20 '18 at 0:59

Aidin

1943

Depends on what you're going to do, another solution can be creating a function instead of a script.

Example:

Create a function in a file, let's say /home/aidin/my-cd-script:

function my-cd() {

  cd /to/my/path

}

Then include it in your bashrc or zshrc file:

# Somewhere in rc file

source /home/aidin/my-cd-script

Now you can use it like a command:

$ my-cd

edited Jun 20 '18 at 1:36

muru

answered Jun 20 '18 at 0:59

Aidin

1943

edited Jun 20 '18 at 1:36

muru

edited Jun 20 '18 at 1:36

muru

edited Jun 20 '18 at 1:36

muru

answered Jun 20 '18 at 0:59

Aidin

1943

answered Jun 20 '18 at 0:59

Aidin

1943

answered Jun 20 '18 at 0:59

Aidin

1943

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cdtjkyj

Script to change current directory (cd, pwd)

6 Answers
6

Use `exec bash` at the end

Your Answer

Post as a guest

6 Answers
6

6 Answers
6

Use `exec bash` at the end

Use `exec bash` at the end

Use `exec bash` at the end

Use `exec bash` at the end

Post as a guest

Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

Connection limited (no internet access)

Script to change current directory (cd, pwd)

6 Answers 6

Use exec bash at the end

Your Answer

Sign up or log in

Post as a guest

Post as a guest

6 Answers 6

6 Answers 6

Use exec bash at the end

Use exec bash at the end

Use exec bash at the end

Use exec bash at the end

Sign up or log in

Post as a guest

Post as a guest

Sign up or log in

Post as a guest

Sign up or log in

Post as a guest

Sign up or log in

Post as a guest

Popular posts from this blog

Loup dans la culture

How to solve the problem of ntp “Unable to contact time server” from KDE?

Connection limited (no internet access)

6 Answers
6

Use `exec bash` at the end

6 Answers
6

6 Answers
6

Use `exec bash` at the end

Use `exec bash` at the end

Use `exec bash` at the end

Use `exec bash` at the end