Custom Query (1630 matches)

See patch provided by Jörg Wittenberger.

stty segfaults when the current-input-port is not a terminal.

Example:

(use stty)

(with-stty (not 'echo)
           (print (read-line)))

This results in:

echo foo |./t 
foo

Error: segmentation violation

        Call history:

        t.scm:4: print    
        t.scm:3: stty#with-stty   
        stty.scm:440: get-terminal-attributes     
        stty.scm:195: make-term-attrs     
        stty.scm:196: port?       
        stty.scm:196: port->fileno        
        stty.scm:200: free-term-attrs     
        stty.scm:441: dynamic-wind        
        stty.scm:443: stty        
        stty.scm:373: port?       
        stty.scm:376: get-terminal-attributes     
        stty.scm:195: make-term-attrs     
        stty.scm:196: port?       
        stty.scm:196: port->fileno        
        stty.scm:200: free-term-attrs     
        stty.scm:377: term-attrs-iflag          <--

A patch is attached, where stty does nothing if get-terminal-attributes fails at the beginning and with-stty does only execute its thunk.

Maybe raising an explicit error is a better way to handle this than silently ignoring the issue.

I got "500 Internal Server Error" from ​http://wiki.call-cc.org/ when trying to add a new page (​http://wiki.call-cc.org/mailing-lists). The page appeared to be created anyway but subsequent requests for the "history" link resulted in the same error.

Peter removed the file and noted that it was unversioned.

It was postulated that the error was triggered through previewing the new page before submitting it for creation.