Hi,
> I released a new version, with an improved 'ctty'. Now the standard I/O
> channels are better initialized: 'ctty' checks the console parameters,
> and properly clears the buffers, so that reading from standard input
> (both raw or cooked) should work.
This is awesome!
Thank you, now it work
Hi Enrique,
> Is there a way to know whether a script is called inside a pipe or not?
> example: (if (insidePipe?) (yes!) (no!))
If you are on pil64, you may call
(n0 (native "@" "isatty" 'I 0))
Otherwise (pil32 or pil64) you could call 'test'
(call "test" "-t" 0)
♪♫ Alex
--
UNSUBSCRI
>(call "test" "-t" 0)
thanks Alex,
now one can make a pager like the unix 'more' utility in Picolisp. Reading
the text from stdin and reading the keyboard to move around the text.
Enrique.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
On Thu, 17 Jul 2014 09:13:38 +0200
Alexander Burger wrote:
> Hello marmorine,
>
Ummm... Steven. ;)
>
> A few minor notes:
>
No quoting for local transient symbols, the the (use (G N) has also
been corrected. These are small things, but very useful for me.
>
> You may be able to tune that
Hi Enrique,
> now one can make a pager like the unix 'more' utility in Picolisp. Reading
> the text from stdin and reading the keyboard to move around the text.
Yes, but still only in a limited way.
Utilities like 'more' or 'less' keep the standard input stream open
while at the same time readin
