From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] shell commands are now run in a child process
Date: Mon, 25 Feb 2008 09:48:19 -0800 [thread overview]
Message-ID: <1203961671-sup-8158@south> (raw)
Reformatted excerpts from Christopher Warrington's message of 2008-02-20:
> I wouldn't right now. I was getting ruby seg. faults with the code I
> submitted and ruby 1.8.6 (ruby bug? I don't know). Changing to code
> that closes open files descriptors until the first invalid file
> descriptor is encountered closes enough that I don't get the crash,
> but also doesn't cause a seg. fault.
Well, this wouldn't be the most cargo-cultish code that's in Sup. (See
previous message about ncurses.)
I'll keep this patch on the back burner, then, until we have a little
more experience. Is anyone else out there using Cygwin?
--
William <wmorgan-sup at masanjin.net>
next reply other threads:[~2008-02-25 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 17:48 William Morgan [this message]
2008-03-01 4:42 ` Christopher Warrington
2008-03-01 20:37 ` William Morgan
-- strict thread matches above, loose matches on Subject: below --
2008-02-03 8:11 Christopher Warrington
2008-02-05 17:34 ` William Morgan
2008-02-05 19:29 ` Christopher Warrington
2008-02-05 20:12 ` William Morgan
2008-02-08 9:40 ` Christopher Warrington
2008-02-19 17:48 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1203961671-sup-8158@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox