Bug#293235: [Pkg-octave-devel] Bug#293235: octave2.1-emacsen: hangs Emacs

John W. Eaton "John W. Eaton" <jwe@bevo.che.wisc.edu>, 293235@bugs.debian.org
Tue, 15 Feb 2005 13:40:52 -0500


On 15-Feb-2005, Francesco Potorti` <Potorti@isti.cnr.it> wrote:

| >If you change the prompt for Octave, you'll need to modify the Emacs
| >variable inferior-octave-prompt.  
| 
| I see.  I should have realized that before...
| 
| >				   The default definition is:
| >
| >  (defcustom inferior-octave-prompt
| >    "\\(^octave\\(-[.0-9]+\\)?\\(:[0-9]+\\)?\\|^debug\\|^\\)>+ "
| >    "*Regexp to match prompts for the inferior Octave process."
| >    :type 'regexp
| >    :group 'octave-inferior)
| 
| Hmm.  Why not simply "^[^>]+>+ "?

That would probably be OK for most cases, though I'm sure some people
reset the prompt to things that don't end with >.

| >Or perhaps we should arrange for the prompt to be set when the
| >Octave process is started by Emacs?  
| 
| Anyway, setting PS1 inside .octaverc is useless with run-octave, because
| PS1 is then reset to "octave> ".  Mh.  inferior-octave-startup does it.
| Why?

I'd guess the goal was to ensure that we could match the prompt.  But
I'm no longer sure how all this is supposed to work.

| >				      But that still would solve the
| >problem of people changing the prompt during a session.

I think I meant "would not solve"

| In principle, the inferior octave mode could detect this and adjust
| comint-prompt-regexp accordingly.

How would you detect the change?

| Or just ignore this problem (as it currently does).

Certainly seems simpler.  :-/

jwe