i3 FAQ - Individual question feed

How to launch a terminal "from here"?

Thu, 21 Jun 2012 07:44:55 +0000

I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by joepd for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Sun, 23 Sep 2012 18:51:05 +0000

Wanted to comment, but there was not enough space... I worked with Tahtisilma's script. I needed to add 1 to the PID, in stead of 2. This is because the working directory of the terminal is irrelevant, we need to have the one of the shell contained in the terminal. I used `pstree -p` to find the heuristics of PID-enumeration, and made a keybind to $mod+Shift+Return. Beware: urxvt{d,c} does not work, as only the PID of the daemon is returned with `xprop`. Would be cool to have a cwd-parser for more than just terminals, so you can open a term in the directory where you have a pdf loaded...

Comment by Tahtisilma for
Wanted to comment, but there was not enough space...

I worked with Tahtisilma's script. I needed to add 1 to the PID, in stead of 2. This is because the working directory of the terminal is irrelevant, we need to have the one of the shell contained in the terminal. I used `pstree -p` to find the heuristics of PID-enumeration, and made a keybind to $mod+Shift+Return.

Beware: urxvt{d,c} does not work, as only the PID of the daemon is returned with `xprop`.

Would be cool to have a cwd-parser for more than just terminals, so you can open a term in the directory where you have a pdf loaded...

Fri, 09 Nov 2012 14:30:00 +0000

Based on your idea of pstree I modified the script to walk to the deepest child with proper working directory. Here it is:http://pastebin.com/MEy9hXdr

Answer by victor for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Thu, 21 Jun 2012 10:33:40 +0000

I wrote a simple script which seems to work: #!/bin/bash ID=$(xdpyinfo | grep focus | cut -f4 -d " ") PID=$(($(xprop -id $ID | grep -m 1 PID | cut -d " " -f 3) + 2)) if [ -e "/proc/$PID/cwd" ] then urxvt -cd $(readlink /proc/$PID/cwd) & else urxvt fi With bindsym $mod+b exec ~/.i3/shell.sh in your config file.

Comment by Tahtisilma for

I wrote a simple script which seems to work:

#!/bin/bash
ID=$(xdpyinfo | grep focus | cut -f4 -d " ")
PID=$(($(xprop -id $ID | grep -m 1 PID | cut -d " " -f 3) + 2))
if [ -e "/proc/$PID/cwd" ]
then
    urxvt -cd $(readlink /proc/$PID/cwd) &
else
    urxvt
fi

With bindsym $mod+b exec ~/.i3/shell.sh in your config file.

Thu, 21 Jun 2012 15:04:41 +0000

Great idea and quite simple solution! For me your script works only for terminals like urxvt or xterm. It does not work for gvim for example. Why you add 2 to pid ? Anyway this is version of your script that works for me: http://pastebin.com/eKy1smm1

Comment by viking for

I wrote a simple script which seems to work:

#!/bin/bash
ID=$(xdpyinfo | grep focus | cut -f4 -d " ")
PID=$(($(xprop -id $ID | grep -m 1 PID | cut -d " " -f 3) + 2))
if [ -e "/proc/$PID/cwd" ]
then
    urxvt -cd $(readlink /proc/$PID/cwd) &
else
    urxvt
fi

With bindsym $mod+b exec ~/.i3/shell.sh in your config file.

Mon, 24 Jun 2013 15:47:56 +0000

I've modified the script to more reliably find the child process. It uses the pstree command. https://gist.github.com/viking/5851049

Comment by kevin for

I wrote a simple script which seems to work:

#!/bin/bash
ID=$(xdpyinfo | grep focus | cut -f4 -d " ")
PID=$(($(xprop -id $ID | grep -m 1 PID | cut -d " " -f 3) + 2))
if [ -e "/proc/$PID/cwd" ]
then
    urxvt -cd $(readlink /proc/$PID/cwd) &
else
    urxvt
fi

With bindsym $mod+b exec ~/.i3/shell.sh in your config file.

Mon, 25 Mar 2013 15:17:46 +0000

+2 is (certainly) to get the pid of the *child* processs of the terminal, ie the shell (after a fork). However, this trick doesn't work with urxvtd/c, as only the daemon opens all the shells ...

Comment by napcode for

I wrote a simple script which seems to work:

#!/bin/bash
ID=$(xdpyinfo | grep focus | cut -f4 -d " ")
PID=$(($(xprop -id $ID | grep -m 1 PID | cut -d " " -f 3) + 2))
if [ -e "/proc/$PID/cwd" ]
then
    urxvt -cd $(readlink /proc/$PID/cwd) &
else
    urxvt
fi

With bindsym $mod+b exec ~/.i3/shell.sh in your config file.

Thu, 21 Jun 2012 12:31:35 +0000

Thanks victor! IGood idea!

Answer by bruno.braga for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Tue, 26 Mar 2013 01:06:33 +0000

@Victor's snippet doesn't work for me on Ubuntu/Gnome-Terminal... some how the xdpyinfo returns the wrong window ID. From @Tahtisilma code, with small adjustments, I got it working for me: #!/bin/bash ID=$(xprop -root | awk '/_NET_ACTIVE_WINDOW$WINDOW$/{print $NF}') PID=($(xprop -id $ID | awk '/_NET_WM_PID$CARDINAL$/{print $NF}')) for CPID in `ps --ppid $PID | awk '/^ [0-9]/ {print $1}'`; do [ -e "/proc/$CPID/cwd" ] && PID=$CPID # loop to get last tty done [ -e "/proc/$PID/cwd" ] && gnome-terminal --working-directory="`readlink "/proc/$PID/cwd"`" || gnome-terminal

Answer by V0id for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Mon, 01 Jul 2013 18:31:59 +0000

For zsh, I have the keybinding CTRL+N to open a terminal in the cwd of the current one. # Open a new window in this term's cwd alias nw="urxvt256c-mlc" nwZle() { zle push-line; BUFFER="nw"; zle accept-line; } zle -N nwZle # CTRL+n bindkey '^n' nwZle Note the keybinding is only a shortcut to a command, so it works only when the prompt can accept a command. That is, either the line is blank or a command has been typed (in this case it will be restored upon launch), but not if you're in a pager, vim, a command is blocking, etc.

Comment by joepd for

For zsh, I have the keybinding CTRL+N to open a terminal in the cwd of the current one.

# Open a new window in this term's cwd
alias nw="urxvt256c-mlc"
nwZle() { zle push-line; BUFFER="nw"; zle accept-line; }
zle -N nwZle
# CTRL+n
bindkey '^n' nwZle

Note the keybinding is only a shortcut to a command, so it works only when the prompt can accept a command. That is, either the line is blank or a command has been typed (in this case it will be restored upon launch), but not if you're in a pager, vim, a command is blocking, etc.

Mon, 24 Mar 2014 08:43:32 +0000

Excellent idea! I did away with the alias, and altered the function so it becomes like this: ``nwZle() { zle push-line; BUFFER="setsid urxvt"; zle accept-line; }``

Answer by ctemplin for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Tue, 30 Jun 2015 18:43:52 +0000

For users of xfce4-terminal, like me, I put together a little shell script. [Here's a gist](https://gist.github.com/ctemplin/3c626af969c67e51d805) In ~/.i3/config: bindsym $mod+T exec "~/.i3/xfce4-terminal-pwd.sh"

Answer by machielo for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Fri, 10 Apr 2015 12:21:42 +0000

For those of you using urxvtd/c, none of the above answers work. This, however, works: github.com/myeisha/urxvt-fork-here I use it like this in my .Xresources: URxvt.perl-ext-common: others,fork-here URxvt.keysym.Mod4-Shift-Return: perl:fork-here:fork-at-cwd Then with `Mod4+Enter` I open a normal `urxvtc` terminal, but with `Mod4+Shift+Enter` I have the new `urxvtc` terminal "here", as the OP wants. Remember to reread resources with `xrdb ~/.Xresources`, relaunch `urxvtd` to load the new perl extension, then relaunch a new `urxvtc` for it to take effect (or just reboot). Hope this helps!

Comment by machielo for

For those of you using urxvtd/c, none of the above answers work. This, however, works:

github.com/myeisha/urxvt-fork-here

I use it like this in my .Xresources:

URxvt.perl-ext-common: others,fork-here
URxvt.keysym.Mod4-Shift-Return: perl:fork-here:fork-at-cwd

Then with Mod4+Enter I open a normal urxvtc terminal, but with Mod4+Shift+Enter I have the new urxvtc terminal "here", as the OP wants.

Remember to reread resources with xrdb ~/.Xresources, relaunch urxvtd to load the new perl extension, then relaunch a new urxvtc for it to take effect (or just reboot).

Hope this helps!

Thu, 07 May 2015 14:37:58 +0000

Awesome! But credit to where it's due: I didn't made the original fork-here extension, I just documented it here because it solved my needs :)

Comment by i3convert for

For those of you using urxvtd/c, none of the above answers work. This, however, works:

github.com/myeisha/urxvt-fork-here

I use it like this in my .Xresources:

URxvt.perl-ext-common: others,fork-here
URxvt.keysym.Mod4-Shift-Return: perl:fork-here:fork-at-cwd

Then with Mod4+Enter I open a normal urxvtc terminal, but with Mod4+Shift+Enter I have the new urxvtc terminal "here", as the OP wants.

Remember to reread resources with xrdb ~/.Xresources, relaunch urxvtd to load the new perl extension, then relaunch a new urxvtc for it to take effect (or just reboot).

Hope this helps!

Tue, 05 May 2015 16:00:33 +0000

@machielo: My current solution is I modified fork-here to get the pid of the shell for urxvtd/c and then I use another solution to extract the folder of the deepest child. This works at least in the Midnight Commander case I mentioned above. Thanks for the fork-here extension!

Comment by machielo for

For those of you using urxvtd/c, none of the above answers work. This, however, works:

github.com/myeisha/urxvt-fork-here

I use it like this in my .Xresources:

URxvt.perl-ext-common: others,fork-here
URxvt.keysym.Mod4-Shift-Return: perl:fork-here:fork-at-cwd

Then with Mod4+Enter I open a normal urxvtc terminal, but with Mod4+Shift+Enter I have the new urxvtc terminal "here", as the OP wants.

Remember to reread resources with xrdb ~/.Xresources, relaunch urxvtd to load the new perl extension, then relaunch a new urxvtc for it to take effect (or just reboot).

Hope this helps!

Tue, 05 May 2015 08:53:58 +0000

Perhaps a hybrid approach can be done inside the perl script, with xprop and if the process returned is URxvt then follow with this fork-here approach, but ideally we would use the xprop approach for everything, to launch a terminal in the same folder as, say, a pdf viewer, as explained by others :S

Comment by machielo for

For those of you using urxvtd/c, none of the above answers work. This, however, works:

github.com/myeisha/urxvt-fork-here

I use it like this in my .Xresources:

URxvt.perl-ext-common: others,fork-here
URxvt.keysym.Mod4-Shift-Return: perl:fork-here:fork-at-cwd

Then with Mod4+Enter I open a normal urxvtc terminal, but with Mod4+Shift+Enter I have the new urxvtc terminal "here", as the OP wants.

Remember to reread resources with xrdb ~/.Xresources, relaunch urxvtd to load the new perl extension, then relaunch a new urxvtc for it to take effect (or just reboot).

Hope this helps!

Tue, 05 May 2015 08:52:15 +0000

Hmmm I see, different use-cases :S I really like urxvtd/c to save some memory, but processes forked (launched) from urxvtc don't usually modify the parent terminal cwd so this doesn't work for those :(

Comment by i3convert for

For those of you using urxvtd/c, none of the above answers work. This, however, works:

github.com/myeisha/urxvt-fork-here

I use it like this in my .Xresources:

URxvt.perl-ext-common: others,fork-here
URxvt.keysym.Mod4-Shift-Return: perl:fork-here:fork-at-cwd

Then with Mod4+Enter I open a normal urxvtc terminal, but with Mod4+Shift+Enter I have the new urxvtc terminal "here", as the OP wants.

Remember to reread resources with xrdb ~/.Xresources, relaunch urxvtd to load the new perl extension, then relaunch a new urxvtc for it to take effect (or just reboot).

Hope this helps!

Fri, 01 May 2015 05:39:23 +0000

This does indeed work with pure urxvtd/c. However, it doesn't work in another situation which I find important. If I run mc (Midnight Commander), it switches to the folder from which mc was started, not to the current folder of mc. Some previous solutions work in this case with regular urxvt.

Answer by ack006 for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Mon, 01 Jul 2013 18:02:18 +0000

Here's my simple snippet for use with Bash, to be added to ${HOME}/.bashrc: # Commands to be executed before the prompt is displayed # Save current working dir PROMPT_COMMAND='pwd > "${HOME}/.cwd"' # Change to saved working dir [[ -f "${HOME}/.cwd" ]] && cd "$(< ${HOME}/.cwd)" No need to find the pid of the most recent shell, the only requirement is a shell which supports running a command either when the prompt is displayed or each time a command is entered at the prompt. The saved directory even persists across logout/login, if you don't want that, simply delete ${HOME}/.cwd on logout. Note: If you have multiple terminals open at different directories, switch to the terminal whose directory you want to 'clone', type or run some other command at the prompt to save that directory, then open a new terminal.

Comment by ack006 for

Here's my simple snippet for use with Bash, to be added to ${HOME}/.bashrc:

# Commands to be executed before the prompt is displayed
# Save current working dir
PROMPT_COMMAND='pwd > "${HOME}/.cwd"'

# Change to saved working dir
[[ -f "${HOME}/.cwd" ]] && cd "$(< ${HOME}/.cwd)"

No need to find the pid of the most recent shell, the only requirement is a shell which supports running a command either when the prompt is displayed or each time a command is entered at the prompt.

The saved directory even persists across logout/login, if you don't want that, simply delete ${HOME}/.cwd on logout.

Note: If you have multiple terminals open at different directories, switch to the terminal whose directory you want to 'clone', type <enter> or run some other command at the prompt to save that directory, then open a new terminal.

Mon, 10 Aug 2015 19:48:45 +0000

For those who worry about too many disk writes, on a relatively modern Linux installation you can change $HOME to $XDG_RUNTIME_DIR which should expand to a per-user directory for run-time volatile storage. This should normally be mounted as a tmpfs, so no worries wearing out your precious SSDs :)

Comment by ShadowPrince for

Here's my simple snippet for use with Bash, to be added to ${HOME}/.bashrc:

# Commands to be executed before the prompt is displayed
# Save current working dir
PROMPT_COMMAND='pwd > "${HOME}/.cwd"'

# Change to saved working dir
[[ -f "${HOME}/.cwd" ]] && cd "$(< ${HOME}/.cwd)"

No need to find the pid of the most recent shell, the only requirement is a shell which supports running a command either when the prompt is displayed or each time a command is entered at the prompt.

The saved directory even persists across logout/login, if you don't want that, simply delete ${HOME}/.cwd on logout.

Fri, 12 Jul 2013 21:09:00 +0000

But that will force HDD to write data on every [Enter] press!

Comment by bruno.braga for

Here's my simple snippet for use with Bash, to be added to ${HOME}/.bashrc:

# Commands to be executed before the prompt is displayed
# Save current working dir
PROMPT_COMMAND='pwd > "${HOME}/.cwd"'

# Change to saved working dir
[[ -f "${HOME}/.cwd" ]] && cd "$(< ${HOME}/.cwd)"

No need to find the pid of the most recent shell, the only requirement is a shell which supports running a command either when the prompt is displayed or each time a command is entered at the prompt.

The saved directory even persists across logout/login, if you don't want that, simply delete ${HOME}/.cwd on logout.

Mon, 01 Jul 2013 22:19:22 +0000

Awesome! This works great for me! First solution that actually works with gnome-terminal... and taking the simplicity of this, I am sure it will work anywhere with bash. Cheers for sharing!

Comment by bruno.braga for

Here's my simple snippet for use with Bash, to be added to ${HOME}/.bashrc:

# Commands to be executed before the prompt is displayed
# Save current working dir
PROMPT_COMMAND='pwd > "${HOME}/.cwd"'

# Change to saved working dir
[[ -f "${HOME}/.cwd" ]] && cd "$(< ${HOME}/.cwd)"

No need to find the pid of the most recent shell, the only requirement is a shell which supports running a command either when the prompt is displayed or each time a command is entered at the prompt.

The saved directory even persists across logout/login, if you don't want that, simply delete ${HOME}/.cwd on logout.

Sun, 14 Jul 2013 11:14:02 +0000

That's what "history" command does anyway, right?

Answer by schischi for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Thu, 25 Apr 2013 13:07:48 +0000

Hi, Being faced with the same problem, I wrote a simple program, which seems to work in most cases: [xcwd on github](https://github.com/schischi-a/xcwd)

Comment by syban for
Hi,

Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Wed, 30 Sep 2015 14:11:21 +0000

xcwd works as expected when launched from the command line but I can't make it work with a shortcut like this bindsym $mod+Return exec gnome-terminal --working-directory="`xcwd`"

Comment by cee for
Hi,

Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Thu, 20 Jun 2013 16:04:05 +0000

I tried all the other scripts mentioned in this thread, but this small c program was the only one that really worked for me. Thank you

Comment by syl20bnr for
Hi,

Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Tue, 30 Jul 2013 02:15:57 +0000

Works great (Ubuntu 12.04 and 13.04), thank you.

Answer by Michael for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Thu, 21 Jun 2012 09:29:58 +0000

There is a script called cwd-spawn for urvxt which does this: http://labs.qu.cx/urxvt-perl/tree/cwd-spawn

Comment by bricksoup for
There is a script called cwd-spawn for urvxt which does this:

http://labs.qu.cx/urxvt-perl/tree/cwd...

Sat, 15 Sep 2012 19:30:12 +0000

The link is dead and I can't find any other copies of or references to cwd-spawn. Any chance you could mirror the script?

Comment by Michael for
There is a script called cwd-spawn for urvxt which does this:

http://labs.qu.cx/urxvt-perl/tree/cwd...

Sun, 23 Sep 2012 19:09:44 +0000

Sure, there you go: http://code.stapelberg.de/git/configfiles/tree/cwd-spawn

Answer by gehidore for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Wed, 01 May 2013 04:44:39 +0000

If only this worked in tabbed mode on a new tab...

i3 FAQ - Individual question feed

How to launch a terminal "from here"?

Answer by joepd for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by victor for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by bruno.braga for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by V0id for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by ctemplin for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by machielo for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by ack006 for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by schischi for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Comment by syban for Hi, Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Comment by cee for Hi, Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Comment by syl20bnr for Hi, Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Answer by Michael for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Comment by bricksoup for There is a script called cwd-spawn for urvxt which does this: http://labs.qu.cx/urxvt-perl/tree/cwd...

Comment by Michael for There is a script called cwd-spawn for urvxt which does this: http://labs.qu.cx/urxvt-perl/tree/cwd...

Answer by gehidore for I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by joepd for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by victor for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by bruno.braga for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by V0id for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by ctemplin for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by machielo for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by ack006 for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Answer by schischi for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Comment by syban for
Hi,

Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Comment by cee for
Hi,

Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Comment by syl20bnr for
Hi,

Being faced with the same problem, I wrote a simple program, which seems to work in most cases: xcwd on github

Answer by Michael for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?

Comment by bricksoup for
There is a script called cwd-spawn for urvxt which does this:

http://labs.qu.cx/urxvt-perl/tree/cwd...

Comment by Michael for
There is a script called cwd-spawn for urvxt which does this:

http://labs.qu.cx/urxvt-perl/tree/cwd...

Answer by gehidore for
I often need another terminal in the same working directory (debugging, compiling... there are many use cases). How can I launch a terminal (rxvt) via i3 and set it to the working directory of the currently selected window?