adjust where prompt markers go#5491
adjust where prompt markers go#5491fdncred merged 2 commits intonushell:mainfrom fdncred:tweak_shell_integration
Conversation
|
ugh - works great in kitty. stinks in iterm and terminal.app. not sure why. |
|
Research (K=Kitty, I=iTerm2, W=WezTerm) -
Docs on semantic prompts |
|
I was looking into this in a TDD way. My idea was that the |
|
@schrieveslaach I have just had a minor breakthrough with the latest main. I was able to use the |
|
I think I finally figured it out. Markers are working in terminal.app, iterm2, wezterm, and kitty. |
|
@fdncred, I tested the current |
|
@schrieveslaach you don't know how happy that makes me feel. this was a real battle for me to figure out how to do it. I would've given up if it weren't for the new hooks functionality. |
|
I'm happy to use Nushell. 😉 Thanks for working on it. |
* adjust where prompt markers go * marks are working, yipee!
Description
The prompt markers were being placed at the wrong spot.
Hopefully this fixes #5449 once and for all.
Tests
Make sure you've run and fixed any issues with these commands:
cargo fmt --all -- --checkto check standard code formatting (cargo fmt --allapplies these changes)cargo clippy --all --all-features -- -D warnings -D clippy::unwrap_used -A clippy::needless_collectto check that you're using the standard code stylecargo build; cargo test --all --all-featuresto check that all the tests pass