unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 40733@debbugs.gnu.org, Will Bush <will.g.bush@gmail.com>
Subject: bug#40733: 28.0.50; Emacs locks up on paste (yank) of unicode characters
Date: Mon, 20 Apr 2020 21:20:34 +0100	[thread overview]
Message-ID: <20200420202034.GB75434@breton.holly.idiocy.org> (raw)
In-Reply-To: <m27dyaxihp.fsf@gmail.com>

On Mon, Apr 20, 2020 at 05:52:02PM +0200, Robert Pluim wrote:
> >>>>> On Mon, 20 Apr 2020 06:05:58 -0500, Will Bush <will.g.bush@gmail.com> said:
> 
>     Will> In GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.14,
>     Will> cairo version 1.16.0)
> 
> Iʼm confused, this is GNU/Linux, but:
> 
>     Will> Configured using:
>     Will>  'configure
>     Will>  --prefix=/nix/store/2142cl219v49czkkrrddh3jy3415nax0-emacs-git-20200420.0
>     Will>  --disable-build-details --with-modules --with-x-toolkit=gtk3 --with-xft
>     Will>  CFLAGS=-DMAC_OS_X_VERSION_MAX_ALLOWED=101200'
> 
> macOS defines?

I’d hazard a guess that Nix uses the same build script no matter what
platform it’s on and that CFLAGS setting has just been hard‐coded.
-- 
Alan Third





  parent reply	other threads:[~2020-04-20 20:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 11:05 bug#40733: 28.0.50; Emacs locks up on paste (yank) of unicode characters Will Bush
2020-04-20 15:52 ` Robert Pluim
2020-04-20 16:13   ` Eli Zaretskii
2020-04-20 21:27     ` Will Bush
2020-04-20 20:20   ` Alan Third [this message]
2020-04-20 22:48 ` Basil L. Contovounesios
2020-04-21 10:01   ` Robert Pluim
2020-04-21 12:19     ` Will Bush
2020-04-21 13:19       ` Robert Pluim
2020-04-21 19:35         ` James Cloos
2020-04-22  7:35           ` Robert Pluim
2020-04-25 10:34             ` Will Bush
     [not found]               ` <CA+aYz4RNB1-g5uUz-M-XuJEhZPGpA4X6n8NSiTCUdOMkpReFng@mail.gmail.com>
2020-04-25 13:34                 ` bug#40733: Fwd: " Will Bush
2020-04-25 13:50               ` Eli Zaretskii
2020-04-29 11:59                 ` Will Bush
2020-04-29 12:16                   ` Eli Zaretskii
2020-04-29 12:42                     ` Will Bush
2020-04-29 12:50                       ` Robert Pluim
2020-04-29 14:30                       ` Eli Zaretskii
2020-06-01 11:19                         ` Will Bush
2020-06-01 11:44                           ` Pip Cet
2020-06-01 15:15                             ` Eli Zaretskii
2020-06-01 15:50                               ` Pip Cet
2022-04-24 14:20                           ` Lars Ingebrigtsen
2022-05-18  3:39                             ` Will Bush
2022-05-18 11:18                               ` Eli Zaretskii
2022-06-15 12:40                               ` Lars Ingebrigtsen
2022-06-19 21:05                                 ` Will Bush
2022-06-19 22:25                                   ` Lars Ingebrigtsen
2020-04-21 14:29       ` 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=20200420202034.GB75434@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=40733@debbugs.gnu.org \
    --cc=rpluim@gmail.com \
    --cc=will.g.bush@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 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).