GNU bug report logs -
#24041
25.1.50; xwidget + -nw mode gives segfault
Previous Next
Reported by: Shane Hansen <shanemhansen <at> gmail.com>
Date: Wed, 20 Jul 2016 16:08:02 UTC
Severity: normal
Found in version 25.1.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Robert Cochran <robert-emacs <at> cochranmail.com>
> Cc: Robert Cochran <robert-emacs <at> cochranmail.com>, shanemhansen <at> gmail.com, 24041 <at> debbugs.gnu.org
> Date: Sat, 20 Aug 2016 14:33:58 -0700
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> >> From: Robert Cochran <robert-emacs <at> cochranmail.com>
> >> Date: Fri, 19 Aug 2016 11:36:30 -0700
> >> Cc: 24041 <at> debbugs.gnu.org
> >>
> >> Anyways, so the fix here is conceptually pretty simple: have a check in
> >> place to ensure (display-graphic-p) returns non-nil before doing any
> >> xwidgets stuff. Easy enough.
> >
> > display-graphic-p accepts argument, so if a function displays on
> > another frame or display, it should be passed that frame or display.
>
> I guess I don't quite understand what you're trying to say here.
I'm saying that display-graphic-p should be told the frame for which
you are asking the question.
> (Is that even possible? Start a graphical frame from a tty Emacs?)
Of course, it is. emacsclient can do that. Assuming Emacs was built
with GUI support, of course. We have this feature for several years
now.
> > IMO, the check should be on the C level where the xwidget primitives
> > are implemented. One such place is make-xwidget; maybe there are
> > more. (The proper way of testing this on the C level is not by
> > calling display-graphic-p, but rather with check_x_display_info.)
>
> That's what my feeling was too. I'll go ahead and do it on the C level
> then.
Thanks.
This bug report was last modified 5 years and 267 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.