beneroth changed the topic of #picolisp to: PicoLisp language | The scalpel of software development | Channel Log: https://libera.irclog.whitequark.org/picolisp | Check www.picolisp.com for more information
theruran has quit [Quit: Connection closed for inactivity]
bjorkintosh has quit [Remote host closed the connection]
bjorkintosh has joined #picolisp
_whitelogger has joined #picolisp
_whitelogger has joined #picolisp
aw- has joined #picolisp
aw- has quit [Read error: Connection reset by peer]
aw- has joined #picolisp
aw- has quit [Client Quit]
kickstatue has joined #picolisp
aw- has joined #picolisp
<kickstatue> Hi! I'm new to picolisp and wonder if it's normal for vip to not show blinking paren match. I turned it on in .inputrc, and it works in pil but not in vip.
<abu[7]> Hi kickstatue, yes, Vip does not show matching parens this way. The reason is that i was lazy and did not find it necessary ;)
<abu[7]> I match parens with %
<abu[7]> and check indentation with "," (comma)
<abu[7]> But you are right, it would be happful
<kickstatue> ah :). I see! Well, I'll just see if I can get used to it then! I really like a built-in ide. I'm just used to emacs and CL, so this style is new to me.
<abu[7]> helpful
<abu[7]> OK :)
<kickstatue> Is it because you generally have rather short lines with few parens nesting that you don't need the blinking parens?
<abu[7]> It is more because it is quite difficult to implement
<abu[7]> The blinking would need an additional machinery (timing)
<abu[7]> In der REPL it works, because readline() takes care of it
<kickstatue> I see! I'm able to get paren matching if I run vip in emacs eshell, but eshell doesn't have suspend, so I think I will just try to get used to vip as it is instead. It seems like a great fit for me in every other respect (once I get used to vi editing that is). Thank you for explaining!
<abu[7]> Great! Thanks for the feedback!
kickstatue has quit [Quit: leaving]
aw- has quit [Quit: Leaving.]
stultulo is now known as f8l