warpdotdev / warpdotdev/warp

Warp not opening at 'workspace folder' when triggered from VSCode.

Open
#4,621 1 comment 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug ready-to-implement triaged
Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Description

Discord username (optional)

Kinxyo#9096

Describe the bug

Background:
There is a keyboard shortcut in Visual Studio Code that allows opening an external terminal. I set Terminal > External: Linux Exec as warp-terminal.

Problem:
The first instance of Warp always resets the path to root. The second instance retains its path to the workspace folder (project root).
To be more clear-- when I press the shortcut for external terminal in vscode, the Warp terminal opens at ~ path. While it's open, and I press the shortcut again to open another instance only then it opens at the project root.

To reproduce
  1. Search "terminal external" in Visual Studio Code's settings.
  2. Set Terminal > External: Linux/Osx/WIndows Exec as warp-terminal.
  3. Set a shortcut for opening external terminal by searching "Open in terminal" settings in keyboard shortcut.
  4. Open any file at any project and press the shortcut.
Expected behavior

It is supposed to open the first instance at the project root itself. I tried the same with 'gnome-terminal' and that worked as expected.

Screenshots

No response

Operating system

Linux

Operating system and version

Ubuntu 22.04.4 LTS

Shell Version

zsh 5.8.1

Current Warp version

v0.2024.03.19.08.01.stable_01

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

Warp's settingRestore wIndows, tabs, panes at startup & Working directory for new session doesn't help.

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the VS Code external-terminal shortcut on Ubuntu 22.04 with Warp configured as the executable, comparing the first and second launches and the project workspace path. Trace the external launch and working-directory handling; done means the first Warp instance opens at the VS Code workspace root, as gnome-terminal does.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, vscode, zsh
Domain
cli, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.