You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue arises from the investigation in mthom/scryer-prolog#2694. There is a comment at the end explaining my conclusions but I will re-word it here below.
I was having issues calling Scryer Prolog from emacs. Scryer Prolog uses rustyline for the repl, and it will print a prompt on the repl (?- ). The emacs package ediprolog expects that prompt for running.
On Linux, the emacs shell eshell is identified by rustyline as an unsupported terminal, as it sets TERM=dumb. There rustylineflushes the prompt to stdout.
I think at least with MSYS2 and others it is becoming more common for Windows applications to use things like TERM=dumb so I guess the check for "unsupported terminals" could be run also on Windows?
The text was updated successfully, but these errors were encountered:
This issue arises from the investigation in mthom/scryer-prolog#2694. There is a comment at the end explaining my conclusions but I will re-word it here below.
I was having issues calling Scryer Prolog from emacs. Scryer Prolog uses rustyline for the repl, and it will print a prompt on the repl (
?-
). The emacs packageediprolog
expects that prompt for running.On Linux, the emacs shell
eshell
is identified by rustyline as an unsupported terminal, as it setsTERM=dumb
. Thererustyline
flushes the prompt to stdout.On Windows, the emacs shell
eshell
also setsTERM=dumb
but this is not checked (it is said that checkingTERM
on Windows is a no-op, not sure why) so it falls into the third case ofreadline_with
which does not flush the prompt.I think at least with MSYS2 and others it is becoming more common for Windows applications to use things like
TERM=dumb
so I guess the check for "unsupported terminals" could be run also on Windows?The text was updated successfully, but these errors were encountered: