unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Al Petrofsky <al@petrofsky.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64121@debbugs.gnu.org
Subject: bug#64121: 28.2; C-SPC not working in term char mode
Date: Sat, 17 Jun 2023 02:26:40 -0400	[thread overview]
Message-ID: <CAPMQwz44zgtpSFiihTtkwOkwvH_JKvdvvbF0+PHORW=siLvv6w@mail.gmail.com> (raw)
In-Reply-To: <83bkhesjli.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On Sat, Jun 17, 2023 at 2:12 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Al Petrofsky <al@petrofsky.org>
> > Date: Fri, 16 Jun 2023 20:06:57 -0400
> >
> >    emacs-28.2 -Q
> >    M-x term RET RET
> >    C-SPC
> >
> > This should send an ASCII NUL (a zero byte) to the pty, but instead it
> > displays "Mark set" in the echo area.
>
> I cannot reproduce this here: I don't see "Mark set" in the echo area.
>
> Maybe this somehow depends on the terminal emulator?  (I use PuTTY.)
>

I should have mentioned this bug won't show up if emacs is running in a
tty. The bug
stems from the subtle difference between C-SPC and C-@ input events on
graphical
terminals.  On a tty, C-SPC and C-@ become the same thing before they get
to emacs.


> How to verify that the null character is sent to the pty?
>

You can start an emacs -nw inside the term. Then pressing C-SPC should
result in a "Mark set" in the inner emacs's echo area.

[-- Attachment #2: Type: text/html, Size: 1693 bytes --]

  reply	other threads:[~2023-06-17  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17  0:06 bug#64121: 28.2; C-SPC not working in term char mode Al Petrofsky
2023-06-17  6:12 ` Eli Zaretskii
2023-06-17  6:26   ` Al Petrofsky [this message]
2023-06-17  6:40     ` Eli Zaretskii
2023-06-17  7:08       ` Gregory Heytings
2023-06-18  6:34         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPMQwz44zgtpSFiihTtkwOkwvH_JKvdvvbF0+PHORW=siLvv6w@mail.gmail.com' \
    --to=al@petrofsky.org \
    --cc=64121@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).