generated from Templates/Baseline
disable starship python module
All checks were successful
ci/woodpecker/push/test Pipeline was successful
ci/woodpecker/push/deploy Pipeline was successful
ci/woodpecker/push/next Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/deploy Pipeline was successful
ci/woodpecker/pr/next Pipeline was successful
All checks were successful
ci/woodpecker/push/test Pipeline was successful
ci/woodpecker/push/deploy Pipeline was successful
ci/woodpecker/push/next Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/deploy Pipeline was successful
ci/woodpecker/pr/next Pipeline was successful
This commit is contained in:
parent
5922aabe3d
commit
26dd610c85
|
@ -218,6 +218,11 @@ Additionally we install these extensions on container startup:
|
||||||
|
|
||||||
## 💣 Known Issues
|
## 💣 Known Issues
|
||||||
|
|
||||||
|
### Starship.rs
|
||||||
|
|
||||||
|
Starship detects workspaces as active python projects. It always appends the prompt
|
||||||
|
fragment `via 🐍 (lsiopy)`. For now I disabled the python module in starship.
|
||||||
|
|
||||||
### 🐛 Default extensions installation timing error
|
### 🐛 Default extensions installation timing error
|
||||||
|
|
||||||
If the automatic installation of the default extension fails, you can always retry he installation with the
|
If the automatic installation of the default extension fails, you can always retry he installation with the
|
||||||
|
|
|
@ -59,6 +59,9 @@ symbol = " "
|
||||||
[package]
|
[package]
|
||||||
symbol = " "
|
symbol = " "
|
||||||
|
|
||||||
|
[python]
|
||||||
|
disabled = true
|
||||||
|
|
||||||
[rust]
|
[rust]
|
||||||
symbol = " "
|
symbol = " "
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user