RGBCube/nu_scripts
1
Fork 0
mirror of https://github.com/RGBCube/nu_scripts synced 2025-08-02 07:07:46 +00:00
Code Issues Activity

Show activated python VE at beginning of prompt. (#722)

Browse source 
By default, the script that activates a python virtual environment for
nushell blindly prepends the virtual environment name to the existing
prompt, which causes the full-line prompt to wrap.
This change shows the virtual environment name properly positioned in
the prompt line.

To activate a python virtual environment with a pretty prompt:
```nu
---------------------------------------------------------- ~ ------------------------------------------------------- |V|
> $env.VIRTUAL_ENV_DISABLE_PROMPT = true; overlay use ve/mp2/bin/activate.nu
(mp2) ------------------------------------ ~/src/rust/nushell_worktrees/main ------------------------- [main ≡] --- |.V|
> 
```
(the unobvious environment prefix is the subject of
nushell/nushell#11469)
This commit is contained in:
Bob Hyman 2024-01-02 11:53:37 -05:00 • committed by GitHub
parent 9b7c1772e2
commit cc4e573a24
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

25
modules/prompt/full-line.nu
View file

@ -1,9 +1,9 @@
# Build a full-line prompt with widgets for: # Build a full-line prompt with widgets for:
# current working directory (duh) # activated python virtual environment (from `overlay use <ve>/bin/activate.nu`)
# current working directory
# git status (branch, branch ahead/behind remote, files changed) # git status (branch, branch ahead/behind remote, files changed)
# ; current position in remembered working directories (`std dirs`, a.k.a. `shells`) (try it to see) # current position in remembered working directories (`std dirs`, a.k.a. `shells`)
# also, as a nu dev special, widget for active nu executable. (flags `cargo run` vs "installed" and which branch built from) # also, as a nu dev special, widget for active nu executable (flags `cargo run` vs "installed" and which branch built from).
#
# #
# to use: # to use:
# 1. copy this file to `($nu.default-config-dir | path add 'scripts')` (Or someplace on your $env.NU_LIB_DIRS path, defined in env.nu) # 1. copy this file to `($nu.default-config-dir | path add 'scripts')` (Or someplace on your $env.NU_LIB_DIRS path, defined in env.nu)
@ -21,20 +21,21 @@
# credit panache-git for the git status widget. # credit panache-git for the git status widget.
use std dirs use std dirs
use std assert
# returns the prompt string # build the prompt from segments, looks like:
# #
# looks like: # ^(<py ve>) ------------ <workingDirectory> ------ <gitRepoStatus> --- <dirs>$
# ---<exeStatus>---------- <workingDirectory> ------ <gitRepoStatus> --- <dirs>
# >
# #
# <exeStatus> shows <exe-path> <exe-branch>, but is empty if # or, if no git repo current directory
# * nu exe running from a "bin" folder (based on `$nu.current-exe` path) #
# * nu exe built from a "main" branch (otherwise shows `(version | get branch)`) # ^------------------------------------ <workingDirectory> ------------ <dirs>$
export def main [ export def main [
--pad_char (-p) = '-' # character to fill with --pad_char (-p) = '-' # character to fill with
] { ] {
let left_content = ($"($pad_char + $pad_char + $pad_char)(current_exe)") let left_content = ($"(
if 'VIRTUAL_ENV_PROMPT' in $env {'(' + $env.VIRTUAL_ENV_PROMPT + ') '}
)($pad_char + $pad_char + $pad_char)(current_exe)")
let left_content_len = ($left_content | ansi strip | str length -g) let left_content_len = ($left_content | ansi strip | str length -g)
let mid_content = ($" (dir_string) ") let mid_content = ($" (dir_string) ")
let mid_content_len = ($mid_content | ansi strip | str length -g) let mid_content_len = ($mid_content | ansi strip | str length -g)