![]() ![]() not mangle the ANSI codes) even if using %PROMPT% rather than Lua. The original version hasn't had a release since 2017, nor even a commit since 2018, so it may be that the forked version I got those docs from does work correctly (i.e. So yeah, clink is destructively (in our case) filtering the PROMPT env-var, but per the fix above, doesn't damage ANSI codes in the prompt when done in Lua.Įdit: Note, those doc links turn out to be from a fork of Clink. To help with, Clink automatically detects most standard ANSI escape codes (and most of ConEmu's non-standard escape codes) and the BEL character (^G, audible bell) and surrounds them with \001 (^A) and \002 (^B) characters. Looks like you need to do the config in clink's settings, as it's probably using the PROMPT env-var itself.īefore Clink displays the prompt it filters the prompt through Lua so that the prompt can be customized. I was able to reproduce this problem by manually putting a space into my local PROMPT var, so it's not a clink problem per-se, but I guess in your case, clink is why the space is there, even though it's not visible in the displayed prompt.Īh, someone did get it working with clink in the end: #3158 (comment). So the instructions should be updated to quote the %PROMPT% as you have done. #Ubuntu open in terminal windowsMy guess would be that it's eating the ANSI codes, so the OSC command is never seen by Windows Terminal.įor the setx issue, it's probably because a " " has ended up in your prompt env-var (I would guess that clink lives in your prompt already). Somewhere in the hidden comments of this ticket, there was a note that clink was interfering with the relevant ANSI codes, and I don't believe it was ever resolved. ![]() I'm pretty sure clink is your problem here, as without it, both commands worked for me as per the instructions. Maybe this does need more specification ? What happens when this command is output over SSH? The terminal can't know that the path isn't on this machine anymore, right? How does Terminal.app handle this?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |