jeffb@grace.cs.washington.edu (Jeff Bowden) (05/23/89)
I rarely (OK - never) want to split a line when I am sending a command using
cmushell. I got tired of "C-e C-m" everytime I wanted to send some input
so I added a variable to comint.el called `comint-split-lines' which defaults
to t (the behaviour in the original distribution). This only adds five
new lines to comint.el. Here's the diff:
*** comint.el.orig Mon Feb 12 14:19:04 1989
--- comint.el Mon May 22 12:16:30 1989
***************
*** 86,89 ****
--- 86,90 ----
;;;============================================================================
;;; Comint mode buffer local variables:
+ ;;; comint-split-lines - bool nil means send whole lines.
;;; comint-prompt-regexp - string comint-bol uses to match prompt.
;;; comint-last-input-end - marker For comint-kill-output command
***************
*** 109,112 ****
--- 110,116 ----
This is a good thing to set in mode hooks.")
+ (defvar comint-split-lines t
+ "Determines if comint-send-input splits the line at point or send it whole.")
+
(defvar input-ring-size 30
"Size of input history ring.")
***************
*** 507,510 ****
--- 511,515 ----
(interactive)
;; Note that the input string does not include its terminal newline.
+ (if (null comint-split-lines) (end-of-line))
(let ((proc (get-buffer-process (current-buffer))))
(if (not proc) (error "Current buffer has no process")
--
"How well do you really know the back of your hand?"