I find myself repeating a lot of:

mkdir longtitleproject
cd longtitleproject

Is there a way of doing it in one line without repeating the directory name? I'm on bash here.

10 Answers 10


There's no built-in command, but you can easily write a function that calls mkdir then cd:

mkcd () {
  mkdir "$1"
  cd "$1"

Put this code in your ~/.bashrc file (or ~/.kshrc for ksh users, or ~/.zshrc for zsh users). It defines a function called mkcd. "$1" will be replaced by the argument of the function when you run it.

This simple version has several defects:

  • You cannot create a chain of subdirectories at once. Fix: pass the -p option to mkdir. (This may or may not be desirable, as it increases the risk of a typo going undetected, e.g. mkcd mydierctory/newsub will happily create mydierctory and mydierctory/newsub when you meant to create newsub inside the existing mydirectory.)
  • If the argument begins with - but isn't just -, then mkdir and cd will interpret it as an option. If it's just -, then cd will interpret it to mean $OLDPWD. If it's + followed by 0 or more digits, then cd in zsh will interpret it as an index in the directory stack. You can fix the first problem, but not the other two, by passing -- before the argument. You can fix all of these problems by prepending ./ to the argument if it's a relative path.
  • mkdir doesn't follow CDPATH, but cd does, so if you've set CDPATH to a value that doesn't begin with . (an admittedly somewhat unusual configuration), then cd may bring you to a different directory than the one that was just created. Prepending ./ to relative paths fixes this (it causes CDPATH to be ignored).
  • If mkdir fails, it tries to execute cd. Fix: use && to separate the two commands.

Still fairly simple:

mkcd () {
  case "$1" in /*) :;; *) set -- "./$1";; esac
  mkdir -p "$1" && cd "$1"

This version still has the potential to make cd go into a different directory from the one that mkdir just created in one edge case: if the argument to mkcd contains .. and goes through a symbolic link. For example, if the current directory is /tmp/here and mylink is a symbolic link to /somewhere/else, then mkdir mylink/../foo creates /somewhere/else/foo whereas cd mylink/../foo changes into foo. It's not enough to look for symbolic links in the argument, because the shell also tracks symbolic links in its own current directory, so cd /tmp/mylink; mkdir ../foo; cd ../foo does not change into the new directory (/somewhere/else/foo) but into /tmp/foo. A fix for this is to let the cd builtin resolve all .. path components first (it doesn't make sense to use foo/.. if foo doesn't exist, so mkdir never needs to see any ..).

We come to this robust if slightly gory version:

mkcd () {
  case "$1" in
    */..|*/../) cd -- "$1";; # that doesn't make any sense unless the directory already exists
    /*/../*) (cd "${1%/../*}/.." && mkdir -p "./${1##*/../}") && cd -- "$1";;
    /*) mkdir -p "$1" && cd "$1";;
    */../*) (cd "./${1%/../*}/.." && mkdir -p "./${1##*/../}") && cd "./$1";;
    ../*) (cd .. && mkdir -p "${1#.}") && cd "$1";;
    *) mkdir -p "./$1" && cd "./$1";;

(Exercise: why am I using a subshell for the first cd call?)

If mkdir fails, I want to be sure not to change the current directory. Changing back with cd - or $OLDPWD isn't good enough if the shell doesn't have permission to change into its current directory. Also, calling cd updates OLDPWD, so we only want to do it once (or restore OLDPWD).

There are also less specialized ways to not have to retype the word from the previous line:

  • Type cd , then Esc . (or Alt+.) to insert the last argument from the previous command.
  • cd !$ executes cd on the last argument of the previous command.
  • Press Up to recall the previous command line, then edit it to change mkdir into cd.
  • Thanks! the Esc . seems the most convenient to me, does the key sequence have any special meaning? – methodofaction Mar 12 '11 at 1:36
  • It's just the Bash (and inherited from ksh, and also works in zsh) sequence for "repeat last word of previous command". I use it quite often. – geekosaur Mar 12 '11 at 1:46
  • 29
    @Gilles I'm beginning to think that the "Gilles" account is actually shared by a panel of experts. ;-) – Keith Mar 12 '11 at 3:24
  • @StephaneChazelas /a/b/..// would actually work but not /a/b/../c. Fixed. I've put the question to a broader audience. – Gilles Jan 30 '13 at 22:26
  • 1
    mkcd() { mkdir -p "$1" && cd "$1"; } doesn't seem to be a problem in (my instance of) zsh. mkdir -p /var/tmp/somewhere/else /tmp/here; cd /tmp/here; ln -s /var/tmp/somewhere/else mylink; mkdir -p mylink/../foo && cd mylink/../foo; pwd (includes the setup and) displays /tmp/here/foo which is what was created (and what I expected). bash erroneously creates and changes to /var/tmp/somewhere/foo. – Adam Katz Jan 15 '15 at 18:39

This is the one-liner that you need. No other config needed:

mkdir longtitleproject && cd $_

The $_ variable, in bash, is the last argument given to the previous command. In this case, the name of the directory you just created. As explained in man bash:

_         At  shell  startup,  set to the absolute pathname used to invoke
          the shell or shell script being executed as passed in the  envi‐
          ronment  or  argument  list.   Subsequently, expands to the last
          argument to the previous command, after expansion.  Also set  to
          the  full  pathname  used  to  invoke  each command executed and
          placed in the environment exported to that command.  When check‐
          ing  mail,  this  parameter holds the name of the mail file cur‐
          rently being checked."$_" is the last argument of the previous command.

Use cd $_ to retrieve the last argument of the previous command instead of cd !$ because cd !$ gives the last argument of previous command in the shell history:

cd ~/
mkdir folder && cd !$

you end up home (or ~/ )

cd ~/
mkdir newfolder && cd $_

you end up in newfolder under home !! ( or ~/newfolder )

  • 20
    Why on Earth this one is not the accepted answer – JSmyth Jul 24 '16 at 4:16
  • 1
    @JSmyth I agree, this is a one-liner that uses native shell functionality – sming Aug 8 '16 at 14:56
  • I think the OP is trying to avoid using the two commands. This answer is (almost) as valid as doing mkdir foo && cd foo, which isn't handy. – josemigallas Jun 13 '17 at 13:08
  • 6
    The OP is asking for a one-liner that doesn't require to repeat the directory name, and this is it – Jesús Carrera Jun 13 '17 at 18:13
  • This is the traditional one-liner you are referring to or have seen others use in docs/tutorials. There are actually 3 perfect answers here. This one, the one by @jordan-harris , and the selected answer. Depends on your setup and preference. – Wade Feb 14 at 2:14

It would never have occurred to me to script up this behaviour because I enter the following on a near-hourly basis ...

$ mkdir someDirectory<ENTER>
$ cd !$

where bash kindly substitutes !$ with the last word of the last line; i.e. the long directory name that you entered.

In addition, filename completion is your friend in such situations. If your new directory was the only file in the folder a quick double TAB would give you the new directory without re-entering it.

Although it's cool that bash allows you to script up such common tasks as the other answers suggest I think it is better to learn the command line editing features that bash has to offer so that when you are working on another machine you are not missing the syntactic sugar that your custom scripts provide.


As per What customizations have you done on your shell profile to increase productivity?, this is how I do it:

# make a directory and cd to it
    test -d "$1" || mkdir "$1" && cd "$1"

it means it also works if the directory already exists.

  • 4
    The -p option to mkdir will suppress errors. – glenn jackman Mar 12 '11 at 5:42
  • @glenn jackman: Indeed it does, thanks. – Mikel Mar 12 '11 at 6:29
  • 1
    mcd is an already existing command. Though you've just given an example, I used it myself as it's a letter shorter than mkcd. – Dharmit Apr 13 '11 at 14:44
  • @Dharmit Shah: What is the existing mcd command? Which package or project provides this command? – Mikel Apr 13 '11 at 22:05
  • 2
    mtools provides the mcd command. Its man page says "The mcd command is used to change the mtools working directory on the MS-DOS disk." – Dharmit Apr 14 '11 at 6:11

If you use Oh My Zsh, there's a command called take that does exactly this. It would look something like this.

take myfolder

I actually found this one by accident. I just looked and it's listed on this cheatsheat from the Oh My Zsh GitHub wiki. It's quite a useful command, and apparently very easy to create yourself.

  • 1
    I never knew about take :) Perfect! btw - iTerm2 with Oh My Zsh. There are actually 3 perfect answers here. This one, the one by @jesús-carrera , and the selected answer. Depends on your setup and preference. – Wade Feb 14 at 2:12

Or you could just create a short variable on-the-fly and use it twice x = longproject ; mkdir $x ; cd $x - which I admit is still longer than using a shellscript function :)


I made a script that creates the directory and then cd's to it, then i gave it an alias. And here is a gist where I describe it.



Here's a slight variant which is worthy of mention:

function mkdir() {
    local dir=$1
    command mkdir "$dir"  &&  cd "$dir"

Add this to your ~/.bash_profile and you can then use mkdir as normal (once you've source'd it), except now it will run the function above rather than the standard mkdir command.

Note, this does not validate input as per the accepted answer by Gilles, but demonstrates how you can (effectively) override builtins.

From the docs (paraphrasing slightly):

command mkdir [args] runs mkdir with args ignoring any shell function named mkdir. Only shell builtin commands or commands found by searching the PATH are executed. If there is a shell function named ls, running command ls within the function will execute the external command ls instead of calling the function recursively

I believe builtin achieves a similar result to command.

  • you should definitely quote $dir – Jeff Schaller Sep 6 '17 at 18:09
  • @Jeff, agreed, but the accepted answer has all the validation one would need. I'm just presenting the use of command as an alternative. – Arj Sep 7 '17 at 9:07

Adding helper function to BASH, ZSH or KSH

Create mkcd command to your environment in one line

echo -e 'mkcd() {\n mkdir -p "$1" && cd $_\n}' >> ~/.${0//-/}rc && . ~/.${0//-/}rc

Just automated the above answers and made a one time executable script:

mkcd ()
    mkdir -p -- "$1" && cd -P -- "$1"

echo "$fun" >> ~/.bashrc

Just copy this in a new file mkcd.sh and run it only once in terminal by bash mkcd.sh. Then execute source ~/.bashrc to make it working in the current session.

After this, you can use mkcd some_dir to create and enter directly in that directory.

  • You suggest writing a script (in a file) whose sole purpose is to append to the ~/.bashrc file (with an answer that has already been given)?  And how do you suggest creating this mkcd.sh script?  With an editor, perhaps?  This looks like more work than just editing ~/.bashrc.  What advantage does this have over the accepted answer?  … … … … … … … … … … … … … … … … … … … … … … … … … … …  P.S. This will fail because of quoting issues, which tells me that you haven’t even tried it yourself. – Scott Dec 11 '17 at 20:52
  • I am sorry to say but yes as I wrote in my answer I used the above answers. It does work. If you don't believe me, try it. And about not trying, I used my complete day to write such scripts in bash and python today. – subtleseeker Dec 11 '17 at 21:11
  • I did try what you wrote.  It does not work. – Scott Dec 11 '17 at 21:21

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.