Re: 'call' function disables echoing input

Hi Alex, Many thanks! Now it works, though it would be much better to have 'call' working correctly. (de shell* (S) # run shell command with interactive input (let Raw (raw) (unless Raw (raw T)) (let Opts '(icrnl icanon iexten echo echoe echok echoctl echoke) #! use (call

Re: 'call' function disables echoing input

Hi Alex, Do shells really? A simple case of the opposite: start vim, kill -9 from another shell, and you have to type stty sane. I think it is more up to the application to save and restore. Although, picolisp does bring surprises, whether you start with dbg.l and *Dbg on or not. But I think

Re: 'call' function disables echoing input

Hi Randall, Do shells really? A simple case of the opposite: start vim, kill -9 from another shell, and you have to type stty sane. I think it is more up to the application to save and restore. That's true. What I meant, however, was the handling of terminal I/O and the 'stop' signal in

Re: Block comment and unescape string

Hi Kriangkrai (what is your short name?). This is a matter of taste, I actually like the func way because that makes it easy for me to differentiate them from system functions. Check out the xhtml.l file for both those functions and the tag function. /Henrik On Fri, May 8, 2009 at 3:24 PM,

Re: Block comment and unescape string

Alright, up to Alex but if it makes the interpreter slower then I'm against= it. The reason I'm using Pico Lisp is because it's faster than the alternatives (Ruby, Python). Maybe it's time then to start with a Maxi Pico Lisp? You could put the Maxi version under Mercurial control, whenever Alex

Re: Block comment and unescape string

Hi Kriangkrai, One problem with 'fill' is that the expressions to fill cannot be anonymous (it must be the result of a variable), e.g. to fill the That's true. That's true if such functions (e.g. div, ul, ...) already exist. Yes, they do, e.g. in lib/xhtml.l. They are a little bit described

Re: Block comment and unescape string

Hi Henrik, You may call me KS. It's NOT my intention to fork Pico Lisp! I just need some features. If I can do them myself, I implement and share them back. If I do not know how, I request them or ask for an alternative solution. It's OK for my contribution to not be included in standard Pico

Re: Block comment and unescape string

Hi Henrik, Alright, up to Alex but if it makes the interpreter slower then I'm against= it. No reason to worry. I'm sure the impact is minimal. Cheers, - Alex -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: 'call' function disables echoing input

Hi Alex, So, something must still be wrong. I just never noticed it because I only called non-interactive processes (except 'vim'). But that is my point - vim goes to a lot of effort to handle the STOP and CONT signals and get the terminal handling right. I have created apps similar to vim -

Re: Block comment and unescape string

Is Kriangkrai acceptable, too? Kriangkrai Soatthiyanont sounds Thai, but maybe I was mistaken, if I wasn't there is a short, usually 3 letter name that is easier to use :-). /Henrik On Fri, May 8, 2009 at 4:43 PM, Alexander Burger a...@software-lab.de wrote: Hi Kriangkrai, You may call me

Re: Block comment and unescape string

Hi Alex and Henrik, Is Kriangkrai acceptable, too? Sure. Kriangkrai is my first name. KS is from K for Kriangkrai (my first name) and S for Soatthiyanont (my surname). Kriangkrai Soatthiyanont sounds Thai Yes, I'm Thai. Sawadee Krub :-) Best regards, KS -- UNSUBSCRIBE:

Questions

Hi Alex, 1. What is the purpose of calling (wait) after (server 8080 ...)? It will wait for what? What is the differences if (wait) is not called? 2. Could you explain how does ht: magic work? : ht:Prin - NIL : (ht:Prin xxx) xxx- T : (ht:abc) ht:abc --