Hi Olwe,
Just as a note, probably many people have told you this already, but Fedora
is not your best bet for a newbie. Redhat is focused very firmly on the
server/enterprise market, and has said that they don't really care all that
much about the desktop. Meaning, of course, that their deskt
Kevin Ryde wrote:
Dan McMahill <[EMAIL PROTECTED]> writes:
ERROR: In procedure write_all:
ERROR: Broken pipe
Yes, that's right, you get a scheme-level error instead of sigpipe
terminating the whole process. (See `catch' in the guile manual for
trapping that error, or perhaps false-if-except
Hi all,
I just had a random idea, and thought I'd run it by y'all. What if you
could compose modules from the REPL, and then write them to a file?
Something like:
(define mod (make-module (my modulename)))
(define f1 (lambda () (display "f1")))
(define value 7)
(add-export mod f1 value)
(write-m
Dan McMahill <[EMAIL PROTECTED]> writes:
>
> ERROR: In procedure write_all:
> ERROR: Broken pipe
Yes, that's right, you get a scheme-level error instead of sigpipe
terminating the whole process. (See `catch' in the guile manual for
trapping that error, or perhaps false-if-exception to ignore it.)
Kevin Ryde wrote:
Dan McMahill <[EMAIL PROTECTED]> writes:
So is there an easy way to detect when the pipe was terminated so I
can avoid crashing?
You can set the SIGPIPE signal to avoid terminating on a broken pipe.
Usually setting it to SIG_IGN is the cleanest, with that a write
throws an
Dan McMahill <[EMAIL PROTECTED]> writes:
>
> So is there an easy way to detect when the pipe was terminated so I
> can avoid crashing?
You can set the SIGPIPE signal to avoid terminating on a broken pipe.
Usually setting it to SIG_IGN is the cleanest, with that a write
throws an EPIPE error. (Rea
