Re: history not saved anymore?
hi all, > > I just switched to pil21 because I noticed a bug with pil64 in “pil +” and > wanted to see if it was > corrected… (when inserting a closing paren, the cursor jumps to the opening > one and freezes) > This is not pil64's issue, but muslc's brutal change: https://git.musl-libc.org/cgit/musl/tree/WHATSNEW#n2141 I seen this behavior on AlpineLinux for years till now. p.s. Pil21 tested on Alpine Linux since creation and successfully passing everything. (mike) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: history not saved anymore?
Le 01/03/2021 à 12:26, Alexander Burger a écrit : I faintly remember to have seen this too, a long time ago. Anybody else here with a better memory? I'm not sure at the moment, but is it perhaps that (wait) does not work? What happens if you call : (wait 200) in non-debug mode? If so, it must depend on the OS. Yep! This freezes pil64 on archlinux (pil21 works correctly) Pil21 reads "~/.pil/rc" at startup. You could put the lines (history (in "~/.pil/history" (make (while (line) (link @))) ) ) (push1 '*Bye '(out "~/.pil/history" (mapc prinl (history into "~/.pil/rc". Instead of "~/.pil/history" you can use any other name (for example, I keep separate histories per directory). Thanks! It solves my problem! Regards. -- Laurent ARTAUD (laurent.art...@free.fr) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: history not saved anymore?
On Mon, Mar 01, 2021 at 12:34:47PM +, Mike wrote: > > I just switched to pil21 because I noticed a bug with pil64 in “pil +” and > > wanted to see if it was > > corrected… (when inserting a closing paren, the cursor jumps to the opening > > one and freezes) > > > > This is not pil64's issue, but muslc's brutal change: > https://git.musl-libc.org/cgit/musl/tree/WHATSNEW#n2141 > I seen this behavior on AlpineLinux for years till now. Ah, yes, now I remember. Thanks Mike! It is the behavior of the select(2) system call, which behaves not as stated in the man page: "On Linux, select(2) modifies timeout to reflect the amount of time not slept". Pil32+64 relied on that. Pil21 does not use select(2) any longer, but poll(2), which has also some other advantages. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: history not saved anymore?
Hi Laurent, > I just switched to pil21 because I noticed a > bug with pil64 in “pil +” and wanted to see if > it was corrected… (when inserting a closing > paren, the cursor jumps to the opening one and > freezes) I faintly remember to have seen this too, a long time ago. Anybody else here with a better memory? I'm not sure at the moment, but is it perhaps that (wait) does not work? What happens if you call : (wait 200) in non-debug mode? If so, it must depend on the OS. > I notice that the history is now limited to the beginning of the session… > “.pil/history” isn’t saved nor read anymore? Oh, yes, sorry! There are so many strategies and preferrences for handling the REPL history, so that it is now no longer done by default. Instead, you can now easily manage it by yourself with the new 'history' function: Pil21 reads "~/.pil/rc" at startup. You could put the lines (history (in "~/.pil/history" (make (while (line) (link @))) ) ) (push1 '*Bye '(out "~/.pil/history" (mapc prinl (history into "~/.pil/rc". Instead of "~/.pil/history" you can use any other name (for example, I keep separate histories per directory). ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
history not saved anymore?
Hello. I just switched to pil21 because I noticed a bug with pil64 in “pil +” and wanted to see if it was corrected… (when inserting a closing paren, the cursor jumps to the opening one and freezes) I notice that the history is now limited to the beginning of the session… “.pil/history” isn’t saved nor read anymore? Regards. -- Laurent ARTAUD -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
