Custom Query (1630 matches)

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.

According to the discussion in ​http://lists.nongnu.org/archive/html/chicken-users/2016-02/msg00021.html , Alex and Jeremy agreed on renaming the module exported by the kanren egg, to avoid confusion with the one exported by the new egg mini-kanren.

The matchable extension currently cannot be compiled because matchable.scm includes file match.scm which is not present in the repository.