all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master a3b3130 1/2: Fix cursor movement on the Linux console with certain characters
Date: Mon, 16 Aug 2021 22:14:00 +0300	[thread overview]
Message-ID: <83im056w3r.fsf@gnu.org> (raw)
In-Reply-To: <877dgldxvh.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  16 Aug 2021 20:53:54 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 16 Aug 2021 20:53:54 +0200
> Cc: emacs-devel@gnu.org
> 
> > While disabling composition in `linux` terminals makes sense, the above
> > code disables them in all frames, not just those attached to
> > `linux` terminals.
> 
> (In all frames if you have a frame on a Linux console, I think?  Or did
> I misunderstand how term/* stuff works?)
> 
> We're discussing how to make this work better over at bug#21363.  I'm
> wondering whether altering global-auto-composition-mode to respect a
> predicate function (to only switch it on on the console), but
> `auto-composition-mode' is a per-buffer thing, and you may open the
> buffer on a different frame, then display it on the console, and then
> that won't work either...

We could perhaps introduce a new, non-nil, non-t value of
auto-composition-mode which would internally cause the display code to
test the current terminal?



  reply	other threads:[~2021-08-16 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210816134138.22360.16962@vcs0.savannah.gnu.org>
     [not found] ` <20210816134140.CB4FF20B72@vcs0.savannah.gnu.org>
2021-08-16 14:39   ` master a3b3130 1/2: Fix cursor movement on the Linux console with certain characters Stefan Monnier
2021-08-16 18:53     ` Lars Ingebrigtsen
2021-08-16 19:14       ` Eli Zaretskii [this message]
2021-08-18 14:24         ` Lars Ingebrigtsen
2021-08-16 20:30       ` Stefan Monnier

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=83im056w3r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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.