[bug #68112] Pager no longer working under Windows
Philip Nienhuis <[email protected]>
| Newsgroups | gmane.comp.gnu.octave.bugs |
|---|---|
| Message-ID | <[email protected]> |
Please use the bug tracker to post updates to a bug report. The mailing list is intended as a read-only notification stream. Info posted to this mailing list address won't appear in the tracker database where it is most useful.
Update of bug #68112 (group octave):
Status: None => Confirmed
_______________________________________________________
Follow-up Comment #1:
Can confirm here w. dev Octave (12) and an older Windows 11 dev version from
late December, on Windows 10 Pro (ESU).
And with 11.1.0 on another Win0 box.
Killing 'less' in Task Manager makes Octave listen again.
After a second attempt to reproduce the bug it took a bit of fiddling in Task
manager to get the Octave processes visible again (to be able to kill 'less');
also seems a bit weird.
Note:
Last time I tried / used the pager must have been years ago so I didn't hit
this (but it's good to know about this issue, e.g., for testing release
candidates. Completely overlooked to try the pager).
TBH I never paid attention to the terminal settings, I even had the "legacy
terminal" setting active since several years, didn't note any issues with
Octave on Win10.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68112>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaaVaGAAKCRCqLAuaBUf3 TnyJAP9hhXauJEvUVDpkyWnFpPYqVjfgRb4yUPp9nxvOshZE/QEAoBrwXMDyBRKI Lv7LQB8gasmDNxpsBAdjeA8DbwixfQI= =e5hu -----END PGP SIGNATURE-----