[CM] [Snd] Weird inf-snd-comint-line-end behavior...

[Charles Turner]

Charles Turner wrote on 3/13/07 at 12:48 PM

>For Snd-FTH, I've updated the release version of Snd-8 with the CVS
>files for xen.c and inf-snd.el. I modified the variable
>inf-snd-comint-line-end to be 2 newlines: "\n\n"
>
>I get:
>
>>open-file-dialog
>GtkWidget_
>#<undef>
>                   <- Here I hit the "return" key again
>nil
>#<undef>
>
>I went back and restored inf-snd-comint-line-end to its 1 newline
>default ("\n"), and everything works "as expected" (i.e. no prompt
>unless I hit "return") and works the same as Debian Linux using the
>default variable value found in inf-snd.el.

Mike-

Is this one for you?

Trying to learn a bit about the elisp debugger and got this when I set
debug-on-entry to inf-snd-comint-snd-send. The repl input was "7 1 +".

Debugger entered--entering a function:
* processp(#<process Snd-Forth>)
* comint-send-string(#<process Snd-Forth>
                     #("7 1 +\n\n" 0 5 (fontified t) 5 7 nil))
* inf-snd-comint-snd-send(#<process Snd-Forth>
                          #("7 1 +" 0 5 (fontified t)))
  comint-send-input()
  call-interactively(comint-send-input)

I don't know enough about any of this, but shouldn't comint-send-string
have arguments like:

#<process Snd-Forth> #("\n\n" 0 2 (fontified t))

I believe the result ("8") has already been printed to the emacs
snd-forth buffer.

Best and thanks! Charles

 
<vze26m98@optonline.net>