Hi Lindsay,
> I've been tinkering with some picolisp code and in
> investigating the use of "run" I am seeing an inconsistency
> between the docs and my environment.
>
> The 'cnt parameter does not seem to reference the nth call environment (see
> full code at end).
Oops, sorry! The example in t
Hi,
I've been tinkering with some picolisp code and in
investigating the use of "run" I am seeing an inconsistency
between the docs and my environment.
The 'cnt parameter does not seem to reference the nth call environment (see
full code at end).
In the example in the docs
the result is
..
(Prg
Thanks Alex!
/Lindsay
On Sat, Jan 4, 2025 at 10:54 AM Alexander Burger
wrote:
> Hi Lindsay,
>
> > I've been tinkering with some picolisp code and in
> > investigating the use of "run" I am seeing an inconsistency
> > between the docs and my environment.
> >
> > The 'cnt parameter does not s
I have been digging into the vip code recently. Initially to get a better
understanding on namespacing and scope in pil21.
However, I am really appreciating how powerfully extensible vip is.
I added a couple of cmds (not yet moved to viprc) to encrypt and decrypt
entire buffers (see below where
Hi Lindsay,
> I have been digging into the vip code recently. Initially to get a better
> understanding on namespacing and scope in pil21.
> ...
> I added a couple of cmds (not yet moved to viprc) to encrypt and decrypt
> entire buffers ...
>
> I've been a bit stuck on how to enter the "yek" enc
On Sun, Jan 05, 2025 at 06:50:17AM +0100, Alexander Burger wrote:
> In some other project I used this:
>
>(de getPw ()
> (pack
> (make
> (until (sub? (setq C (key)) "^J^M")
>...
This was out of context, originally not a separate function but inline
i
