From: Lars Ingebrigtsen <larsi@gnus.org>
To: Wenocur <awenocur@gmail.com>
Cc: 29920@debbugs.gnu.org
Subject: bug#29920: 25.3; term-mode f-keys
Date: Mon, 30 Nov 2020 11:39:07 +0100 [thread overview]
Message-ID: <87wny3ceno.fsf@gnus.org> (raw)
In-Reply-To: <sv5sv6mv1yg182.fsf@3c0754310e53.i-did-not-set--mail-host-address--so-tickle-me> (Wenocur's message of "Sun, 31 Dec 2017 14:13:17 -0500")
Wenocur <awenocur@gmail.com> writes:
> To trigger the problem:
>
> Start term-mode with a visual text-mode application that requires f-keys
> to function. In my case, I was using aws-shell.
>
> Leave the terminal in char mode.
>
> Attempt to use f-keys to operate the application.
>
> Symptom:
> The f-keys operate as they would in any other mode.
(This bug report unfortunately got no response at the time.)
I don't have aws-shell here, but if I understand you correctly, you're
pointing out that
emacs -Q
M-x term RET RET
gives you a mode where the function keys have their default bindings
(i.e., <f3> is `kmacro-start-macro-or-insert-counter') instead of
sending the function keys to the program running in the sub-process?
This does seem rather odd -- term-mode is rather aggressive about
rebinding just about anything, but leaves the function keys alone. Does
anybody know whether this is on purpose, or is it just because few
terminal programs use the function keys?
I think it would make conceptual sense for term-mode to pass the
function keys along to the running program. Does anybody object to
making such a change?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-30 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 19:13 bug#29920: 25.3; term-mode f-keys Wenocur
2020-11-30 10:39 ` Lars Ingebrigtsen [this message]
2022-05-08 13:04 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wny3ceno.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=29920@debbugs.gnu.org \
--cc=awenocur@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.