Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
"Change prompt text cursor" fails on long lines with Clink #317
first of all, thank you very much for all the work on ConEmu.
as of 150910 "Change prompt text cursor" with or without extra key fails on long lines. i.e. if the line is longer than the screen, changing text cursor only works within the very last line. if I try to click in previous 'lines', so to speak, simply nothing happens.
this only seems to be happening with Clink (official 0.4.5 in my case), with pure cmd.exe it still works fine.
now, I did see #270 but I'm not sure this is the same thing as actually Clink itself never ceased working (0.4.4 and now 0.4.5 w/ all ConEmu builds so far)
I'm not 100% sure but I think it worked fine in previous ConEmu builds - and it's no big issue as there's always
There is no way to detect where "readline" was started. That is related to many other shells, not only to cmd+clink. So, to avoid numerous beeps and hungs which are reported from time to time, I've decided to lock changing cursor position to one line only.
Possibly related, when typing a command of length greater than 8 characters and then hitting escape to clear the input,
Ref: gh-986, gh-317, gh-845 Now ‘Change prompt text cursor position with Left Click’ and ‘Ctrl+Backspace - delete word leftward to the text cursor’ are process by ConEmu GUI without posting command to ConEmuHk. The feature requires properly reported by the shell prompt start pos. For bare cmd.exe it's done automatically by ConEmuHk. All other shells must report the start of the prompt with ANSI. * https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC * https://conemu.github.io/en/CygwinMsysConnector.html For example, while using bash and connector you may add to the end of your `PS1` the following sequence: `\[\033]9;12\007\]`.