GNU bug report logs - #20906
25.0.50; Pasting unicode from external applications with mouse wheel on Unix

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mike FABIAN <mfabian <at> redhat.com>
Cc: 20906 <at> debbugs.gnu.org
Subject: bug#20906: 25.0.50;
Date: Mon, 05 Oct 2015 13:29:51 +0300

> From: Mike FABIAN <mfabian <at> redhat.com>
> Cc: 20906 <at> debbugs.gnu.org
> Date: Mon, 05 Oct 2015 12:07:19 +0200
> 
> In xselect.c near line 1473, there is:
> 
>     static Lisp_Object
>     x_get_window_property_as_lisp_data (struct x_display_info *dpyinfo,
>                                         Window window, Atom property,
>                                         Lisp_Object target_type,
>                                         Atom selection_atom)
>     {
>       Atom actual_type;
>       int actual_format;
>       unsigned long actual_size;
>       unsigned char *data = 0;
>       ptrdiff_t bytes = 0;
>       Lisp_Object val;
>       Display *display = dpyinfo->display;
> 
>       TRACE0 ("Reading selection data");
> 
>       x_get_window_property (display, window, property, &data, &bytes,
>                              &actual_type, &actual_format, &actual_size);
> 
> And here I see that “data” contains something like this:
> 
>     (gdb) p	data
>     $1 = (unsigned char *) 0x1a98cb0 "\\u5b8c\\u4e86"
> 
> I.e. it seems to be wrong in in that function in “data” already.

That was my guess.  What is the value of 'property', btw?

> Is this the right way to debugging this? Continue like this?

Could it be that some agent unrelated to Emacs produces these strings?
Maybe the selection owner itself (Firefox, right?)?

Do other X programs work OK with pasting from the primary selection
via the mouse?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.