unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Elia Nolz" <gnu-emacs@lycheese.org>
To: "Yuuki Harano" <masm+emacs@masm11.me>
Cc: 48136@debbugs.gnu.org
Subject: bug#48136: 28.0.50; [feature/pgtk] ISO_Level5_Shift broken
Date: Fri, 21 May 2021 10:22:42 +0200	[thread overview]
Message-ID: <38d85b63-e293-465e-a4c8-5b885fd59362@www.fastmail.com> (raw)
In-Reply-To: <20210521.155757.1726693901068500719.masm@luna.pink.masm11.me>

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

On Fri, May 21, 2021, at 08:57, Yuuki Harano wrote:
> > do I need to switch to ddskk or similar?
> 
> Yes.
Ok, I will do that then.

I have documented the configuration needed to get back to Emacs' default behaviour on my side but I have seen quite a few people who use a similar setup to mine struggle with the changes to the behaviour and some drop pgtk altogether.

Will there be a disclaimer or similar when pgtk is merged into master or when that version of Emacs is released? Maybe it would be advisable to make these changes the default since that is how Emacs behaved to date?

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

  reply	other threads:[~2021-05-21  8:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  9:34 bug#48136: 28.0.50; [feature/pgtk] ISO_Level5_Shift broken Elia Nolz
2021-05-08 11:50 ` Elia Nolz
2021-05-09 10:17   ` Yuuki Harano
2021-05-09 10:47     ` Elia Nolz
2021-05-20  9:30       ` Elia Nolz
2021-05-20 11:02         ` Yuuki Harano
2021-05-20 13:28           ` Elia Nolz
2021-05-20 16:02             ` Yuuki Harano
2021-05-20 16:58               ` Elia Nolz
2021-05-21  6:57                 ` Yuuki Harano
2021-05-21  8:22                   ` Elia Nolz [this message]
2021-05-21  9:56                     ` Yuuki Harano
2021-06-09  9:21                       ` Elia Nolz
2021-06-24  8:52                         ` Elia Nolz
2021-06-25 12:05                           ` Yuuki Harano
2021-10-01 15:09                             ` Elia Nolz
2022-07-01 11:13                           ` 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

  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=38d85b63-e293-465e-a4c8-5b885fd59362@www.fastmail.com \
    --to=gnu-emacs@lycheese.org \
    --cc=48136@debbugs.gnu.org \
    --cc=masm+emacs@masm11.me \
    /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).