tyriar / vscode-terminal-here Goto Github PK

if my file is on D:\ but default Terminal is pointing to C:, cd to a folder isn't work

How can i configure it to open the external terminal at the currently selected files directory also if it is selected in the explorer or in the editor?

this is windows 10,

{
"terminal.integrated.shell.windows": "C:\Program Files\Git\bin\bash.exe"
}

I set my debian.exe's path in settings.json as the intergrated shell.
But when i use the keybinding to open it, it opens at the path ~ instead of /mnt/c/xxxxx.

The plugin works well with cmd and Powershell in my vscode.

From VS Code version 1.37 you can do everything this extension by adding the following setting to your settings.json file:

"terminal.integrated.cwd": "${fileDirname}"

I just downloaded this tool as it seemed super useful. However, I am getting this error whenever I try to use it.

I have narrowed it down to it having problems with finding the vscode npm library. Is there anything I can do to fix this?

Hello, is there any chance that the option could be introduced whereby invoking Terminal Here on on existing open terminal simply closed it, in other words making it a toggle operation. Maybe it could be configurable:

"editor.terminal-here": "toggle"/"immediate"

If the shell is set to Bash on Windows (WSL), cd C:\... will not direct to the right folder. Instead it should call cd /mnt/c/...

Setting

{
  "terminal.integrated.shell.windows": "\\Windows\\sysnative\\bash.exe"
}

I am using Ubuntu Linux subsystem inside Windows 10 and have changed "terminal.integrated.shell.windows" to "C:\\Windows\\System32\\bash.exe" to make vscode use bash as the terminal.

When using terminal-here, the bash shell is launched, but the cd $DIR command fails because it still uses Windows style path like:
D:\Devel\Android\aosp
instead of Linux subsystem path:
/mnt/d/Devel/Android/aosp

When you run the command and your default terminal is the Ubuntu subsystem for Windows, the extension still applies the default behavior for Windows, giving an incorrect path:

cd "c:\Users\Whimzee\Desktop\project\"
$ cd "c:\Users\Ben\Desktop\project\"
-bash: cd: c:\Users\Whimzee\Desktop\project\: No such file or directory

This is how I have my terminal path set up in settings, which is default for the current distribution:

{
    "terminal.integrated.shell.windows": "ubuntu.exe"
}

My understanding is that something must be wrong with how the extension detects the Ubuntu subsystem.

I use this little trick to be able to switch between terminal and editor

    {
        "key": "ctrl+`",
        "command": "workbench.action.terminal.focus"
    },
    {
        "key": "ctrl+`",
        "command": "workbench.action.focusActiveEditorGroup",
        "when": "terminalFocus"
    }

With workbench.action.terminal.focus if a terminal isn't open it opens one, if a terminal is open it just switches focus. It would be nice for terminalHere.create to behave similarly

Right now I use this workaround

    {
        "key": "ctrl+shift+`",
        "command": "terminalHere.create",
        "when": "editorFocus"
    }

If I have a file "E:\testdir\test.txt" and i want open a terminal on this drive in this folder, then your extension works not correctly, because your extension will not change the drive by enter "E:". Actually the executed command "cd E:\testdir" is not enough for windows.
Could you please extend your extension and support different windows drives.
Best regards
Joe

Very useful feature --- is it hard to follow directory of active file in last active terminal?
Like by hotKey or permanently when file changed (as option) ?

I want to configure per workspace on where the terminal can start.

The extension currently opens a terminal at the current directory of the opened file.

Another feature to consider is adding a right click menu item on the project panel to start terminal in the selected directory.

macOS 10.13.1 High Sierra
1.18.1 VSCode (stable)
1.19.0 VSCode (insiders)

Hi Daniel, I’ve just installed your Terminal Here extension and it works well. Just one visual glitch, it shows the cd command twice. See attached image. Better if there was just be the one cd, and even better if that was > /dev/null. Silent, in other words!

macOS 10.13.2
VSCode 1.20.0 Insiders

I have just updated to the latest version of VSCode Insiders, and I have started to see the error A system error occurred (ENOENT: no such file or directory, stat '/Users/carlca/.vscode-insiders/extensions/Tyriar.vscode-terminal-here-0.0.5/out/src') appear on a fairly frequent basis. Do I need to add something to my config or is there some other cause?

Ctrl ` still seems to invoke the terminal ok, although I do recall reading recently that the operation of Terminal Here has changed slightly. Do I need to do something differently? Thanks.

Currently you see all logs with folder switching when you start a terminal, maybe it will be better to clear screen after initialization (in addition, this currently working directory is visible in prompt).
Command clear is suitable for almost all consoles (?), and only cmd uses cls.

I am unfamiliar with JS :) And did this as follows:

    var clearCommand = "clear";                                  // <--- Here
    var dir = path.dirname(uri.fsPath);
    var terminal = vscode.window.createTerminal();
    terminal.show(false);
    switch (kindOfShell(vscode.workspace.getConfiguration('terminal'))) {
        case "wslbash":
            // c:\workspace\foo to /mnt/c/workspace/foo
            dir = dir.replace(/(\w):/, '/mnt/$1').replace(/\\/g, '/');
            break;
        case "cmd":
            // send 1st two characters (drive letter and colon) to the terminal
            // so that drive letter is updated before running cd
            clearCommand = "cls";                                // <--- Here
            terminal.sendText(dir.slice(0, 2));
    }
    terminal.sendText("cd \"" + dir + "\"");
    terminal.sendText(clearCommand);                             // <--- Here

I can open a PR if this seems reasonable for you.