Regarding the perserval of the CWD in > term bash panes

[yum13241]

Hello everyone, I just have a small question.

I like to use > hsplit to have some code open in one pane (P1) and then I do > term bash in the other (P2), is it possible to have P2 automatically have the working directory of P1?

I tried the solution at #3724 but it doesn't seem to work when executed in an > hsplit'd pane (doing > termx instead of > term bash, only in a completely new tab.

~/.config/micro/init.lua

local config = import("micro/config")
local filepath = import("filepath")

function init()
    config.MakeCommand("termx", termInCurrentDir, config.NoComplete)
end

function termInCurrentDir(bufpane, args)
    local shellCommand = (args == nil or #args == 0) and "/bin/bash" or args[1]
    local workdir = filepath.Dir(bufpane.Buf.Path)
    -- WARNING: if you need to deal with paths that contain double quotes you will need better shell quoting than this
    bufpane:HandleCommand(string.format("term env --chdir=\"%s\" %s", workdir, shellCommand))
end

Thanks for reading!

[Andriamanitra]

You could dig up a reference to the first BufPane in the current tab (P1) through micro.CurTab() ¹ which returns a *Tab. The BufPane that is passed to the function as an argument is the one that was active before you opened the command prompt (P2).

Footnotes

1. help plugins ↩