Yeah, people recommend iTerm2. But there's no brokenness with Terminal.app, so no reason to replace it.
iTerm has brokenness wrt the system clipboard, while Terminal.app just works.
Thanks for updating the keyboard support, it works much better now. ^_^
Hello Marc,
Thank you for your feedback.
I am using a Mac too, but I run qemacs in iTerm2, which I recommend as a terminal application on macOS.
The escape sequences for Home and End were bogus, I fixed them and added support for the Control, Shift and Alt prefixes for the cursor movement keys.
Let me know if is works fine on your system
Regarding F1, the terminal indeed sends ESC O P, which is recognised as the key `f1` and bound to the command help-for-help, which is somewhat different from the emacs binding where `f1` is a prefix key equivalent to C-h.
It is surprising that `f1` seems to invoke goto-tag, which is bound to `C-x ,` and `M-f1` which for some
obscure reason is not produced by the keyboard when hitting Alt Fn F1, but can be obtained with ESC F1.
The key decoding has been substantially improved and unrecognised sequences are reported.
You can also use C-h d to invoke toggle-trace-mode that displays the *trace* buffer with information
about the bytes received from the terminal, the key conversions, the commands invoked, the bytes
sent to the shell process and the escape sequences received from the process. This is quite useful
to debug keyboard and VT100 emulation issues.
Best regard
Chqrlie
The key bindings available via C-h b shows
beginning-of-line : C-a, home
But Home does not go to beginning-of-line. It instead acts as backward-word.
It also shows
beginning-of-buffer : M-<, C-home
And C-home is again backward-word.
Also, what is qemacs looking for that signifies F1? In macOS Terminal.app, F1 is ESC-O-P, hitting F1 qemacs produces the message “No tag”. Can that “Press F1 for help message be customized or disabled? It looks like canned text in qe.c.
Thanks.