bug#45338: prolog-mode: cursor jumps into inferior Prolog shell when consulting buffer

bug#45338: prolog-mode: cursor jumps into inferior Prolog shell when consulting buffer

[SB]

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

How to reproduce:
Suppose I have started the inferior Prolog shell using M-x run-prolog. If I
"consult" a Prolog mode buffer using M-x prolog-consult-buffer, the Emacs
cursor ends up in the inferior Prolog shell.

Expected behaviour:
The cursor should remain inside the Prolog mode buffer when consulting the
buffer. The existing behaviour is inconsistent with just about every other
inferior shell for other programming languages (lisp, python, scheme, etc.).

Further details:
I've noticed that the current implementation of "prolog-consult-buffer" calls
"prolog-goto-prolog-process-buffer", which is responsible tor making the
cursor go to inferior Prolog shell.

Questions:
* Feature request: Would the maintainers consider adding an option to
disable this behaviour?
* What should I currently add to my ~/.emacs file as a temporary measure to
make the cursor remain in the Prolog mode buffer instead of jumping into
the inferior Prolog shell?
<https://github.com/emacs-mirror/emacs/blob/emacs-27/lisp/progmodes/prolog.el#L2610-L2614>

[-- Attachment #2: Type: text/html, Size: 1418 bytes --]

bug#45338: cursors jumps can be disabled by a flag

[k3tu0isui]

There is support for the feature you want. Check out the variable "prolog-use-standard-consult-compile-method-flag". Setting this to "nil" enables the behaviour you like.

If the value of this variable is "t", prolog-mode uses prolog-old-process-* functions all of which do the switch. Otherwise, prolog-consult-compile* functions are used that do not have this behaviour.

Since this behavious is expected, it is not a bug. Just do (setq prolog-use-standard-consult-compile-method-flag nil).

bug#45338: prolog-mode: cursor jumps into inferior Prolog shell when consulting buffer

[Lars Ingebrigtsen]

k3tu0isui@gmail.com writes:

> There is support for the feature you want. Check out the variable
> "prolog-use-standard-consult-compile-method-flag". Setting this to
> "nil" enables the behaviour you like.
>
> If the value of this variable is "t", prolog-mode uses
> prolog-old-process-* functions all of which do the switch. Otherwise,
> prolog-consult-compile* functions are used that do not have this
> behaviour.
>
> Since this behavious is expected, it is not a bug. Just do (setq
> prolog-use-standard-consult-compile-method-flag nil).

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Since this doesn't look like it's a bug, I'm closing it now.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no