Re: [R-SIG-Mac] ANSI escape weirdness on M1 (libedit issue?)

2021-11-12 Thread Gábor Csárdi
Thanks for the answer, I actually just saw this today, it went into my spam folder for some reason. Anyway, I tried to build readline 5.2 and it wasn't that bad. I got the source for the libreadline-gplv2-dev Debian package (https://packages.debian.org/stretch/libreadline-gplv2-dev). This is

Re: [R-SIG-Mac] ANSI escape weirdness on M1 (libedit issue?)

2021-11-03 Thread Simon Urbanek
Gabor, as you can see the x86_64 readline is a very old build 5.2-14 - it is the last version released under GPL-2. Later versions are to my best knowledge license-incompatible since they are released under GPL-3 only and thus do not allow the use in GPL-2 software. The arm64 version

Re: [R-SIG-Mac] ANSI escape weirdness on M1 (libedit issue?)

2021-11-03 Thread Gábor Csárdi
On Wed, Nov 3, 2021 at 7:00 PM Prof Brian Ripley wrote: [...] > AFAIK the reason for not distributing readline with binary distributions > of R is perceived licence restrictions. So is the license different for x86_64? Because those builds come with readline: ❯ R-4.1 -q -e

Re: [R-SIG-Mac] ANSI escape weirdness on M1 (libedit issue?)

2021-11-03 Thread Prof Brian Ripley
On 03/11/2021 12:21, Gábor Csárdi wrote: Anyone else noticed some weirdness with the arm build when the prompt has ANSI escape codes? E.g. in a terminal run this options(prompt = "\033[1m> \033[0m") and then at the new prompt type in some longer word and press CTRL+A. Longer than what? The

[R-SIG-Mac] ANSI escape weirdness on M1 (libedit issue?)

2021-11-03 Thread Gábor Csárdi
Anyone else noticed some weirdness with the arm build when the prompt has ANSI escape codes? E.g. in a terminal run this options(prompt = "\033[1m> \033[0m") and then at the new prompt type in some longer word and press CTRL+A. The cursor does not go back to the beginning of the line, probably