Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DUP: #064 - Launching a virtual environment with pipenv gets rid of blocks and autocomplete #881

Closed
Raees678 opened this issue Apr 5, 2022 · 2 comments

Comments

@Raees678
Copy link

Raees678 commented Apr 5, 2022

Discord username (optional)

raees678#0247

Describe the bug

Edit: Upon further investigation this happens when any program launches a subshell. Even just launching zsh from within warp causes this issue.

When launching a virtual environment with pipenv, pipenv launches a subshell `zsh` in the virtual environment. The warp terminal no longer has blocks or any autocomplete features.

I dont have the same issue when launching a python virtual environment with `virtualenv`.

To Reproduce

Steps to reproduce:

  1. Install Python 3.9.12, pipenv, version 2022.3.28 from homebrew
  2. Launch pipenv in any directory using pipenv shell
  3. See error: The shell is launched but now its all within the same block, there is no autocomplete.
    OR
  4. Launch zsh from within your terminal.
  5. The new shell does not support blocks.

Expected behaviour

The resulting shell should behave like a warp shell with each prompt in its own block and autocomplete support.

Screenshots

Screen Shot 2022-04-05 at 2 26 37 PM

Screen Shot 2022-04-05 at 2 40 00 PM

Operating System

MacOS

OS Version

12.3

Additional context

No response

@armona
Copy link

armona commented Apr 10, 2022

Same thing happens when using poetry (poetry shell)

@elviskahoro
Copy link

@elviskahoro elviskahoro changed the title Launching a virtual environment with pipenv gets rid of blocks and autocomplete DUP: #064 - Launching a virtual environment with pipenv gets rid of blocks and autocomplete Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants