Harald Hanche-Olsen

I think I now understand what had me confused: The terminology used is slightly different from what I am used to. I come from a Common Lisp mindset, and there...

I disagree. I much prefer having `$pwd` reflect the current physical directory, independent of the history of how you got there. I think using the symlink from earlier invocations of...

You're probably right. But then the limitations and dangers of mixing bytes and values on the same pipe should be clearly documented, so users can know exactly what will reliably...

> other than to tell people about this solution Indeed, please do! Perhaps add it to the [NetNewsWire 6.1 for iPhone and iPad Help](https://netnewswire.com/help/ios/6.1/en/) somewhere, perhaps in a separate “Tips...

There are other ways of achieving a similar goal. Here are two I just thought of: A function `run-with-values-and-bytes` taking two arguments, both of them functions. The two functions will...

@krader1961 For sure, the easiest way to resolve #1576 is likely to replace the fixed size value buffer by one that might grow without bounds, unless the process runs out...

> Would this print 1, 2, 1? That's how I read it. But I wasn't sure, until I saw the `pwd` example. And otherwise, it would be just like `var`....

Oops, discovered just now that this is not maintained. I am leaving this here anyhow, in case someone who does maintain a fork comes along and sees it.

Okay, I will give it some thought. I was hoping you (or someone) could spot the right fix easily, but if not, I will have a look myself when I...

The same problem exists for lists, very likely for a similar reason: ``` ⬥ var a = [x y z] ⬥ set a[1] a[2] = u v ⬥ put $a...