unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: t@fullmeta.me
To: help-guix@gnu.org
Subject: Ctrl-g inside `guix shell --container emacs` broken
Date: Tue, 04 Jan 2022 15:30:58 +0000	[thread overview]
Message-ID: <877dbfjy7t.fsf@fastmail.com> (raw)


Hi Guix.

This one is both subtle and deadly given mussle memory we all 
develop with Emacs key bindings.

Tested with both Emacs 27 and 28:

$ guix shell --container --no-cwd --preserve='^TERM$' emacs -- 
emacs -nw -q -Q
or
$ guix shell --container --no-cwd --preserve='^TERM$' emacs-next 
-- emacs -nw -q -Q

Starts terminal Emacs fine. Now Ctrl-g or M-x followed by Ctrl-g 
which typically would send `keyboard-quit` and also 
abort-recursive-edit. You get kicked out of Emacs and shell ends 
up in a weird state, with Ctrl-D being the only way to kill 
it. Replicated in xterm and gnome-terminal.

This is specific to --container! The following works just fine:

$ guix shell --preserve='^TERM$' emacs -- emacs -nw -q -Q

For completness I also tried:

$ guix shell --container --no-cwd --preserve='^TERM$' emacs bash 
-- bash -c 'emacs -nw -q -Q'

Any idea where and why --container could be breaking things? Note 
that `abort-recursive-edit` works perfectly fine. How exactly 
--container starts those processes? Could it be running some weird 
"shell" version that treats C-g specially somehow? How do I make 
it stop?

$ guix describe
Generation 10	Dec 27 2021 15:36:01	(current)
  guix 9e9489f
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: 9e9489fb11ac73e51abe293235738d70365affa9

Thanks


                 reply	other threads:[~2022-01-04 16:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=877dbfjy7t.fsf@fastmail.com \
    --to=t@fullmeta.me \
    --cc=help-guix@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.
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).