Re: Bug in mksh when counting line length

2019-01-04 Thread John Ankarström
Hi Thorsten, Hope this clears it up. Massively. Thank you! Best regards, John

Re: Bug in mksh when counting line length

2019-01-04 Thread Thorsten Glaser
Hi John, >> no, you’ve discovered you did not read the manpage ☺ > > I did read it, but I didn't understand it...! Adding the \r and surrounding > all escape sequences with \1 solves my problem, but I don't understand why > (?). Ah okay. Basically, the first \1\r says: make the \1 into a

Re: Bug in mksh when counting line length

2019-01-04 Thread John
Hi Thorsten, and thanks for your solution! no, you’ve discovered you did not read the manpage ☺ I did read it, but I didn't understand it...! Adding the \r and surrounding all escape sequences with \1 solves my problem, but I don't understand why (?). Best regards, John

Re: Bug in mksh when counting line length

2019-01-04 Thread Thorsten Glaser
Hi John, > I think I've discovered a bug in mksh. According to the man page: no, you’ve discovered you did not read the manpage ☺ PS1 The primary prompt for interactive shells. Parameter, com- […] Since backslashes and other special characters may be inter-

Bug in mksh when counting line length

2019-01-04 Thread John
Hello, I think I've discovered a bug in mksh. According to the man page: In these editing modes, if a line is longer than the screen width (see the COLUMNS parameter), a ‘>’, ‘+’ or ‘<’ character is displayed in the last column indicating that there are more characters after,