What is the difference between the commands builtin cd and cd?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












17















I encountered a Linux command, builtin cd.



What is the difference between the commands builtin cd and cd?



In fact, I made some researches about the difference, but I could not find a remarkable and significant explanation about this.










share|improve this question



















  • 1





    See also unix.stackexchange.com/q/38808/117549

    – Jeff Schaller
    Jan 19 at 10:49











  • See also: stackoverflow.com/q/15691977/974555

    – gerrit
    Jan 19 at 17:45















17















I encountered a Linux command, builtin cd.



What is the difference between the commands builtin cd and cd?



In fact, I made some researches about the difference, but I could not find a remarkable and significant explanation about this.










share|improve this question



















  • 1





    See also unix.stackexchange.com/q/38808/117549

    – Jeff Schaller
    Jan 19 at 10:49











  • See also: stackoverflow.com/q/15691977/974555

    – gerrit
    Jan 19 at 17:45













17












17








17


7






I encountered a Linux command, builtin cd.



What is the difference between the commands builtin cd and cd?



In fact, I made some researches about the difference, but I could not find a remarkable and significant explanation about this.










share|improve this question
















I encountered a Linux command, builtin cd.



What is the difference between the commands builtin cd and cd?



In fact, I made some researches about the difference, but I could not find a remarkable and significant explanation about this.







bash shell cd-command






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 19 at 12:26









Peter Mortensen

90158




90158










asked Jan 19 at 9:31









GoktugGoktug

33111




33111







  • 1





    See also unix.stackexchange.com/q/38808/117549

    – Jeff Schaller
    Jan 19 at 10:49











  • See also: stackoverflow.com/q/15691977/974555

    – gerrit
    Jan 19 at 17:45












  • 1





    See also unix.stackexchange.com/q/38808/117549

    – Jeff Schaller
    Jan 19 at 10:49











  • See also: stackoverflow.com/q/15691977/974555

    – gerrit
    Jan 19 at 17:45







1




1





See also unix.stackexchange.com/q/38808/117549

– Jeff Schaller
Jan 19 at 10:49





See also unix.stackexchange.com/q/38808/117549

– Jeff Schaller
Jan 19 at 10:49













See also: stackoverflow.com/q/15691977/974555

– gerrit
Jan 19 at 17:45





See also: stackoverflow.com/q/15691977/974555

– gerrit
Jan 19 at 17:45










2 Answers
2






active

oldest

votes


















41














The cd command is a built-in, so normally builtin cd will do the same thing as cd. But there is a difference if cd is redefined as a function or alias, in which case cd will call the function/alias but builtin cd will still change the directory (in other words, will keep the built-in accessible even if clobbered by a function.)



For example:





user:~$ cd () echo "I won't let you change directories"; 
user:~$ cd mysubdir
I won't let you change directories
user:~$ builtin cd mysubdir
user:~/mysubdir$ unset -f cd # undefine function


Or with an alias:



user:~$ alias cd='echo Trying to cd to'
user:~$ cd mysubdir
Trying to cd to mysubdir
user:~$ builtin cd mysubdir
user:~/mysubdir$ unalias cd # undefine alias


Using builtin is also a good way to define a cd function that does something and changes directory (since calling cd from it would just keep calling the function again in an endless recursion.)



For example:



user:~ $ cd () echo "Changing directory to $1-home"; builtin cd "$@"; 
user:~ $ cd mysubdir
Changing directory to mysubdir
user:~/mysubdir $ cd
Changing directory to home
user:~ $ unset -f cd # undefine function





share|improve this answer




















  • 5





    +1 The examples are particularly illustrative here.

    – Tashus
    Jan 19 at 16:09






  • 2





    In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

    – gerrit
    Jan 19 at 17:46






  • 2





    @gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

    – wjandrea
    Jan 19 at 22:08



















15














In most instances, there is no difference (but see below). The cd command is a built-in command in all shells. It needs to be built-in1 as an external command can not change the environment of the invoking shell, and changing the working directory constitutes a change in its environment.



The bash command builtin forces the shell to use the built-in version of a command, even though there may be a shell function, alias, or external command available with the same name.



In the case where there is e.g. a shell function with the name cd, then builtin cd would not call that. Using builtin cd bypasses any overloaded functionality that may have been added through a shell function or alias by the user.



Example:



The cd built-in command may be overloaded by a function that updates the prompt:



cd() 
builtin cd "$@" && PS1=$(__update_prompt)



where __update_prompt is some other user-supplied function that outputs a string.



The builtin cd in the function would not call the function recursively. Using builtin cd in a shell where this function is active, would additionally not call the function.




1There are Unices with an external cd command (macOS, and, I believe, Solaris). The purpose of that command, which can't change the working directory for a shell, is possibly to satisfy the POSIX standard, which lists cd as one of the external utilities that should be available (cd is not one of the "special builtin utilities"). It may also serve as a test to see whether changing work directory to a given directory would be possible.






share|improve this answer

























  • FWIW, MacOS would also fall in the category of OSs with an external cd command.

    – yoann
    Jan 19 at 10:40











  • @yoann Indeed it does.

    – Kusalananda
    Jan 19 at 10:42











  • Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

    – james
    Jan 19 at 18:27











  • most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

    – Grump
    Jan 20 at 9:37











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


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495422%2fwhat-is-the-difference-between-the-commands-builtin-cd-and-cd%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









41














The cd command is a built-in, so normally builtin cd will do the same thing as cd. But there is a difference if cd is redefined as a function or alias, in which case cd will call the function/alias but builtin cd will still change the directory (in other words, will keep the built-in accessible even if clobbered by a function.)



For example:





user:~$ cd () echo "I won't let you change directories"; 
user:~$ cd mysubdir
I won't let you change directories
user:~$ builtin cd mysubdir
user:~/mysubdir$ unset -f cd # undefine function


Or with an alias:



user:~$ alias cd='echo Trying to cd to'
user:~$ cd mysubdir
Trying to cd to mysubdir
user:~$ builtin cd mysubdir
user:~/mysubdir$ unalias cd # undefine alias


Using builtin is also a good way to define a cd function that does something and changes directory (since calling cd from it would just keep calling the function again in an endless recursion.)



For example:



user:~ $ cd () echo "Changing directory to $1-home"; builtin cd "$@"; 
user:~ $ cd mysubdir
Changing directory to mysubdir
user:~/mysubdir $ cd
Changing directory to home
user:~ $ unset -f cd # undefine function





share|improve this answer




















  • 5





    +1 The examples are particularly illustrative here.

    – Tashus
    Jan 19 at 16:09






  • 2





    In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

    – gerrit
    Jan 19 at 17:46






  • 2





    @gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

    – wjandrea
    Jan 19 at 22:08
















41














The cd command is a built-in, so normally builtin cd will do the same thing as cd. But there is a difference if cd is redefined as a function or alias, in which case cd will call the function/alias but builtin cd will still change the directory (in other words, will keep the built-in accessible even if clobbered by a function.)



For example:





user:~$ cd () echo "I won't let you change directories"; 
user:~$ cd mysubdir
I won't let you change directories
user:~$ builtin cd mysubdir
user:~/mysubdir$ unset -f cd # undefine function


Or with an alias:



user:~$ alias cd='echo Trying to cd to'
user:~$ cd mysubdir
Trying to cd to mysubdir
user:~$ builtin cd mysubdir
user:~/mysubdir$ unalias cd # undefine alias


Using builtin is also a good way to define a cd function that does something and changes directory (since calling cd from it would just keep calling the function again in an endless recursion.)



For example:



user:~ $ cd () echo "Changing directory to $1-home"; builtin cd "$@"; 
user:~ $ cd mysubdir
Changing directory to mysubdir
user:~/mysubdir $ cd
Changing directory to home
user:~ $ unset -f cd # undefine function





share|improve this answer




















  • 5





    +1 The examples are particularly illustrative here.

    – Tashus
    Jan 19 at 16:09






  • 2





    In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

    – gerrit
    Jan 19 at 17:46






  • 2





    @gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

    – wjandrea
    Jan 19 at 22:08














41












41








41







The cd command is a built-in, so normally builtin cd will do the same thing as cd. But there is a difference if cd is redefined as a function or alias, in which case cd will call the function/alias but builtin cd will still change the directory (in other words, will keep the built-in accessible even if clobbered by a function.)



For example:





user:~$ cd () echo "I won't let you change directories"; 
user:~$ cd mysubdir
I won't let you change directories
user:~$ builtin cd mysubdir
user:~/mysubdir$ unset -f cd # undefine function


Or with an alias:



user:~$ alias cd='echo Trying to cd to'
user:~$ cd mysubdir
Trying to cd to mysubdir
user:~$ builtin cd mysubdir
user:~/mysubdir$ unalias cd # undefine alias


Using builtin is also a good way to define a cd function that does something and changes directory (since calling cd from it would just keep calling the function again in an endless recursion.)



For example:



user:~ $ cd () echo "Changing directory to $1-home"; builtin cd "$@"; 
user:~ $ cd mysubdir
Changing directory to mysubdir
user:~/mysubdir $ cd
Changing directory to home
user:~ $ unset -f cd # undefine function





share|improve this answer















The cd command is a built-in, so normally builtin cd will do the same thing as cd. But there is a difference if cd is redefined as a function or alias, in which case cd will call the function/alias but builtin cd will still change the directory (in other words, will keep the built-in accessible even if clobbered by a function.)



For example:





user:~$ cd () echo "I won't let you change directories"; 
user:~$ cd mysubdir
I won't let you change directories
user:~$ builtin cd mysubdir
user:~/mysubdir$ unset -f cd # undefine function


Or with an alias:



user:~$ alias cd='echo Trying to cd to'
user:~$ cd mysubdir
Trying to cd to mysubdir
user:~$ builtin cd mysubdir
user:~/mysubdir$ unalias cd # undefine alias


Using builtin is also a good way to define a cd function that does something and changes directory (since calling cd from it would just keep calling the function again in an endless recursion.)



For example:



user:~ $ cd () echo "Changing directory to $1-home"; builtin cd "$@"; 
user:~ $ cd mysubdir
Changing directory to mysubdir
user:~/mysubdir $ cd
Changing directory to home
user:~ $ unset -f cd # undefine function






share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 20 at 1:37

























answered Jan 19 at 9:50









filbrandenfilbranden

8,09621139




8,09621139







  • 5





    +1 The examples are particularly illustrative here.

    – Tashus
    Jan 19 at 16:09






  • 2





    In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

    – gerrit
    Jan 19 at 17:46






  • 2





    @gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

    – wjandrea
    Jan 19 at 22:08













  • 5





    +1 The examples are particularly illustrative here.

    – Tashus
    Jan 19 at 16:09






  • 2





    In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

    – gerrit
    Jan 19 at 17:46






  • 2





    @gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

    – wjandrea
    Jan 19 at 22:08








5




5





+1 The examples are particularly illustrative here.

– Tashus
Jan 19 at 16:09





+1 The examples are particularly illustrative here.

– Tashus
Jan 19 at 16:09




2




2





In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

– gerrit
Jan 19 at 17:46





In the case of an alias, is there any difference between builtin cd mysubdir and cd mysubdir?

– gerrit
Jan 19 at 17:46




2




2





@gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

– wjandrea
Jan 19 at 22:08






@gerrit Only if there is a function named cd, in which case cd would bypass the alias and run the function. See stackoverflow.com/a/16506263/4518341

– wjandrea
Jan 19 at 22:08














15














In most instances, there is no difference (but see below). The cd command is a built-in command in all shells. It needs to be built-in1 as an external command can not change the environment of the invoking shell, and changing the working directory constitutes a change in its environment.



The bash command builtin forces the shell to use the built-in version of a command, even though there may be a shell function, alias, or external command available with the same name.



In the case where there is e.g. a shell function with the name cd, then builtin cd would not call that. Using builtin cd bypasses any overloaded functionality that may have been added through a shell function or alias by the user.



Example:



The cd built-in command may be overloaded by a function that updates the prompt:



cd() 
builtin cd "$@" && PS1=$(__update_prompt)



where __update_prompt is some other user-supplied function that outputs a string.



The builtin cd in the function would not call the function recursively. Using builtin cd in a shell where this function is active, would additionally not call the function.




1There are Unices with an external cd command (macOS, and, I believe, Solaris). The purpose of that command, which can't change the working directory for a shell, is possibly to satisfy the POSIX standard, which lists cd as one of the external utilities that should be available (cd is not one of the "special builtin utilities"). It may also serve as a test to see whether changing work directory to a given directory would be possible.






share|improve this answer

























  • FWIW, MacOS would also fall in the category of OSs with an external cd command.

    – yoann
    Jan 19 at 10:40











  • @yoann Indeed it does.

    – Kusalananda
    Jan 19 at 10:42











  • Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

    – james
    Jan 19 at 18:27











  • most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

    – Grump
    Jan 20 at 9:37
















15














In most instances, there is no difference (but see below). The cd command is a built-in command in all shells. It needs to be built-in1 as an external command can not change the environment of the invoking shell, and changing the working directory constitutes a change in its environment.



The bash command builtin forces the shell to use the built-in version of a command, even though there may be a shell function, alias, or external command available with the same name.



In the case where there is e.g. a shell function with the name cd, then builtin cd would not call that. Using builtin cd bypasses any overloaded functionality that may have been added through a shell function or alias by the user.



Example:



The cd built-in command may be overloaded by a function that updates the prompt:



cd() 
builtin cd "$@" && PS1=$(__update_prompt)



where __update_prompt is some other user-supplied function that outputs a string.



The builtin cd in the function would not call the function recursively. Using builtin cd in a shell where this function is active, would additionally not call the function.




1There are Unices with an external cd command (macOS, and, I believe, Solaris). The purpose of that command, which can't change the working directory for a shell, is possibly to satisfy the POSIX standard, which lists cd as one of the external utilities that should be available (cd is not one of the "special builtin utilities"). It may also serve as a test to see whether changing work directory to a given directory would be possible.






share|improve this answer

























  • FWIW, MacOS would also fall in the category of OSs with an external cd command.

    – yoann
    Jan 19 at 10:40











  • @yoann Indeed it does.

    – Kusalananda
    Jan 19 at 10:42











  • Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

    – james
    Jan 19 at 18:27











  • most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

    – Grump
    Jan 20 at 9:37














15












15








15







In most instances, there is no difference (but see below). The cd command is a built-in command in all shells. It needs to be built-in1 as an external command can not change the environment of the invoking shell, and changing the working directory constitutes a change in its environment.



The bash command builtin forces the shell to use the built-in version of a command, even though there may be a shell function, alias, or external command available with the same name.



In the case where there is e.g. a shell function with the name cd, then builtin cd would not call that. Using builtin cd bypasses any overloaded functionality that may have been added through a shell function or alias by the user.



Example:



The cd built-in command may be overloaded by a function that updates the prompt:



cd() 
builtin cd "$@" && PS1=$(__update_prompt)



where __update_prompt is some other user-supplied function that outputs a string.



The builtin cd in the function would not call the function recursively. Using builtin cd in a shell where this function is active, would additionally not call the function.




1There are Unices with an external cd command (macOS, and, I believe, Solaris). The purpose of that command, which can't change the working directory for a shell, is possibly to satisfy the POSIX standard, which lists cd as one of the external utilities that should be available (cd is not one of the "special builtin utilities"). It may also serve as a test to see whether changing work directory to a given directory would be possible.






share|improve this answer















In most instances, there is no difference (but see below). The cd command is a built-in command in all shells. It needs to be built-in1 as an external command can not change the environment of the invoking shell, and changing the working directory constitutes a change in its environment.



The bash command builtin forces the shell to use the built-in version of a command, even though there may be a shell function, alias, or external command available with the same name.



In the case where there is e.g. a shell function with the name cd, then builtin cd would not call that. Using builtin cd bypasses any overloaded functionality that may have been added through a shell function or alias by the user.



Example:



The cd built-in command may be overloaded by a function that updates the prompt:



cd() 
builtin cd "$@" && PS1=$(__update_prompt)



where __update_prompt is some other user-supplied function that outputs a string.



The builtin cd in the function would not call the function recursively. Using builtin cd in a shell where this function is active, would additionally not call the function.




1There are Unices with an external cd command (macOS, and, I believe, Solaris). The purpose of that command, which can't change the working directory for a shell, is possibly to satisfy the POSIX standard, which lists cd as one of the external utilities that should be available (cd is not one of the "special builtin utilities"). It may also serve as a test to see whether changing work directory to a given directory would be possible.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 19 at 12:31

























answered Jan 19 at 9:39









KusalanandaKusalananda

128k16241398




128k16241398












  • FWIW, MacOS would also fall in the category of OSs with an external cd command.

    – yoann
    Jan 19 at 10:40











  • @yoann Indeed it does.

    – Kusalananda
    Jan 19 at 10:42











  • Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

    – james
    Jan 19 at 18:27











  • most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

    – Grump
    Jan 20 at 9:37


















  • FWIW, MacOS would also fall in the category of OSs with an external cd command.

    – yoann
    Jan 19 at 10:40











  • @yoann Indeed it does.

    – Kusalananda
    Jan 19 at 10:42











  • Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

    – james
    Jan 19 at 18:27











  • most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

    – Grump
    Jan 20 at 9:37

















FWIW, MacOS would also fall in the category of OSs with an external cd command.

– yoann
Jan 19 at 10:40





FWIW, MacOS would also fall in the category of OSs with an external cd command.

– yoann
Jan 19 at 10:40













@yoann Indeed it does.

– Kusalananda
Jan 19 at 10:42





@yoann Indeed it does.

– Kusalananda
Jan 19 at 10:42













Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

– james
Jan 19 at 18:27





Thank you - you've made my day with top notch, well researched,, footnoted pedantry.

– james
Jan 19 at 18:27













most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

– Grump
Jan 20 at 9:37






most shells -- it's an external program for execlineb, but then it's cd will then exec its remaining arguments

– Grump
Jan 20 at 9:37


















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














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495422%2fwhat-is-the-difference-between-the-commands-builtin-cd-and-cd%23new-answer', 'question_page');

);

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






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay