Message-ID: <399F3B95.585EC230@hotmail.com> From: the Icefalcon Organization: Harumichi Otaku ... doko ni mo! X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: SIGTSTP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 12 Date: Sun, 20 Aug 2000 01:53:22 GMT NNTP-Posting-Host: 12.85.128.30 X-Complaints-To: abuse AT worldnet DOT att DOT net X-Trace: bgtnsc07-news.ops.worldnet.att.net 966736402 12.85.128.30 (Sun, 20 Aug 2000 01:53:22 GMT) NNTP-Posting-Date: Sun, 20 Aug 2000 01:53:22 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com cl/cl_funcs.c uses it in the nvi source. A page describes it as "an interactive stop signal" that can be handled or ignored (unlike SIGSTOP), but in a different place it also says that the SUSP character that usually causes SIGTSTP to be sent is "recognized only if the implementation supports job control". I'm guessing DJGPP doesn't ... ? At least, it's mentioned on delorie.com's GNU pages but not in anything related to DJGPP, and it's not defined in DJGPP's signal.h. For the moment I'm just throwing in a -DSIGTSTP=SIGABRT to the makefile since there's also no SIGSTOP (since no job control) ... This is safe, right? -- -|-E the Icefalcon