From bfae2529b8aa7b12b19da2ec7ad00ba717941074 Mon Sep 17 00:00:00 2001
From: Eric Andersen
Date: Thu, 17 May 2001 00:14:27 +0000
Subject: It turns out job control in both hush and lash was broken by the
 signal handling in cmdedit.c.  Disabling it makes the shells behave
 themselves again.  hush isn't quite there, but is getting close...  -Erik

---
 cmdedit.c | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'cmdedit.c')

diff --git a/cmdedit.c b/cmdedit.c
index ec99393..cc39e56 100644
--- a/cmdedit.c
+++ b/cmdedit.c
@@ -571,6 +571,7 @@ extern void cmdedit_init(void)
 		atexit(cmdedit_reset_term);	/* be sure to do this only once */
 	}
 
+#if 0
 	if ((handlers_sets & SET_TERM_HANDLERS) == 0) {
 		signal(SIGKILL, clean_up_and_die);
 		signal(SIGINT, clean_up_and_die);
@@ -578,6 +579,7 @@ extern void cmdedit_init(void)
 		signal(SIGTERM, clean_up_and_die);
 		handlers_sets |= SET_TERM_HANDLERS;
 	}
+#endif	
 
 }
 
@@ -1487,6 +1489,7 @@ prepare_to_die:
 extern void cmdedit_terminate(void)
 {
 	cmdedit_reset_term();
+#if 0
 	if ((handlers_sets & SET_TERM_HANDLERS) != 0) {
 		signal(SIGKILL, SIG_DFL);
 		signal(SIGINT, SIG_DFL);
@@ -1495,6 +1498,7 @@ extern void cmdedit_terminate(void)
 		signal(SIGWINCH, SIG_DFL);
 		handlers_sets &= ~SET_TERM_HANDLERS;
 	}
+#endif	
 }
 
 #endif	/* BB_FEATURE_COMMAND_EDITING */
-- 
cgit v1.1