Looking a possible ways around this I saw this in the tutorial :)

(in "/home/me/test_fl.txt"
   (until (eof)
      (echo 1)
      (key)))

and it works great. My problem is I don't know how to
capture (echo 1)  into a symbol's val.


On 13 February 2017 at 23:03, dean <deangwillia...@gmail.com> wrote:

> Thank you very much for this!
> I tried (cd src; make tools) both from the command line...because of "$"
> and from within Picolisps RPL because of the parens.
> I looked in src and there is just the utf2.c file.
> When I do $ (cd src; make tools) from the command line I get...
> $ (cd src; make tools)
> *** Parse error in /home/me/picoLisp/src: Missing dependency operator
> (Makefile:20)
> *** Parse error: Need an operator in 'else' (Makefile:28)
> *** Parse error: Missing dependency operator (Makefile:29)
> *** Parse error: Need an operator in 'else' (Makefile:37)
> etc.
>
> which looks like
> the block beginning
> ifeg ($(shell uname), Linux)
> .
> .
> else
> ifeg ($(shell uname, OpenBSD)
> .
> .
> I'm the second i.e. OpenBSD option and know very nothing about makefiles.
> I'm on a 64 bit OS but am looking at two -m32 options in there.
> That might well be ok but I thought I'd mention it.
>
> Best Regards
> Dean
>
>
>
>
>
>
>
> On 13 February 2017 at 21:52, Alexander Burger <a...@software-lab.de>
> wrote:
>
>> Hi Dean,
>>
>> > 6869 a074 6865 6972 3aa0 686f 7720 6172 6520 796f 750a
>> > hi.their:.how are you.
>> >
>> > The following program...
>> >
>> > (in "/home/me/test_fl.txt"
>> >    (until (eof)
>> >       (setq Ln (line T))
>> >       (prinl Ln)))
>> >
>> > results in this....
>> >
>> > hiനeir:ਯw are you
>>
>> OK, as you noticed in your other mail, PicoLisp can handle *only* UTF-8
>> input.
>>
>>
>> > (load "@lib/import.l")
>>
>> This is probably not necessary here.
>>
>>
>> > (in '("bin/utf8" "/home/me/test_fl.txt")
>>
>> Good, that's the right way!
>>
>>
>> > bin/utf8: Can't exec
>>
>> Try this:
>>
>>    $ (cd src; make tools)
>>
>> ♪♫ Alex
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>

Reply via email to