> Cygwin also generates NUL:
Thanks for checking! NULs were used as fill characters to throttle down the
line speeds, and were supposed to be ignored
in both hardware and software... I guess with the software terminal emulators
(such as MinTTY/Windows console/and such), that depends
on setting
Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
I then see "C-@" echoed in the minibuffer, and the resulting *Help* buffer says
WFIW, in the DEC VT terminals (from where most of ANSI controls stem from),
Ctrl-Space used to
generate a NUL character (ASCII '\0'), and so maybe it is seen as
> I then see "C-@" echoed in the minibuffer, and the resulting *Help* buffer
> says
WFIW, in the DEC VT terminals (from where most of ANSI controls stem from),
Ctrl-Space used to
generate a NUL character (ASCII '\0'), and so maybe it is seen as a fill
character by the OP's
terminal and, therefo
On 9/2/2022 9:33 PM, Ricardo Urbina wrote:
Hi, I'm trying out Cygwin's Zsh within Windows Terminal because WT
integrates better with WSL, but Cygwin beats it for working on the Windows
side.
However, I launched emacs and eventually noticed that Ctrl+Space doesn't
work when running under Windows
Hi, I'm trying out Cygwin's Zsh within Windows Terminal because WT
integrates better with WSL, but Cygwin beats it for working on the Windows
side.
However, I launched emacs and eventually noticed that Ctrl+Space doesn't
work when running under Windows Terminal. It doesn't work on jmacs, and
using
5 matches
Mail list logo
