AoC_2021_day_3

Reminder of fun we had. :] Solution is still very expensive, but submarine is saved for now. :] Best regards, Razzy. scratch_2021_3.l Description: Binary data

Re: [PicoLisp] [PiL] im Betreff verwenden

On Wed, Dec 29, 2021 at 07:59:08PM +0900, Jean-Christophe Helary wrote: > > > > On Dec 29, 2021, at 18:50, Alexander Burger wrote: > > > > Hi Rolf, hi all, > > > >> könnten wir [PicoLisp] oder [PiL] in der Betreffzeil verwenden. > >> Somit könnten wir schneller erkennen, dass diese Info zum

Re: Extending 'VIP' editor

Hi all. To Erik: Thank you for sharing, i am gradually starting to use parts of your viprc. I think it is very healthy to have viprc bigger than vip itself. To all: I think we should strive for small, clean and simple default version of Picolisp and Vip. Only put in ideas that are clean, powerful

vip shortcut for (doc 'fun)

vip has to be run in debug mode for (doc) to work. $pil -vi + (de *KeyMap-g ("h" # Search word under cursor (and (getWord T "~") (doc (car (str (pack @)) #str is troublesome, be carefull when modifying ) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Blitzing debugger, fzf history search

Hello, sorry for delay, i am sending code Olaf was asking for. Best regards, Razzy. : (pretty rdeb) (NIL (println "q quit | d (d) | e safe-eval | unbug-all") (case (key) ("d" (d)) ("e" (unless (fork) (msg (e)) (bye))) ("q" NIL) ) ) : (pretty f) (NIL (let? A (pipe (call 's

Re: PilCon topic canvas.l

Hi all, I also remember topic "=3== efficient pil workflow", represented by many questions with same underlying problem. I am mainly focused on speeding up my pil development now, before i go for project. I would like anything efficient with linux<->pil interaction, pil<->programmer interacti

Re: PilCon yesterday - the screen share hassle

Hello, I offer my humble opinions: I do not mind loose/chaotic/not-100%-productive meeting. PilCon is also about socialization and trust-building. I am against video recording. I think it would be beneficial for trust-building to agree about no-recording. I think it is not practical to have re

Re: New blog - "PicoLisp for beginners"

Hi, I consider myself beginer. I like your blog (have i read it sooner, i would save my time). PilCon afterthoughts: as beginer I face problem of too big search space for possible answers. I think that your top-down clarification proposal is aimed at that. 60 beginer functions from your blog helps

Re: PilCon tomorrow

Hi all, I think I would find value in topics (most value on top): vip workflow with focus on linux terminal interaction. (I know i missed PilCons with vip topic.) linux-terminals\picolisp interaction linux processes\linux terminal interaction. I can offer introduction to linux-fuzzy-search workfl

Subscribe