* bug#13112: 24.2.90; The cygw32 build should disable X11 @ 2012-12-07 13:04 Ken Brown 2012-12-07 14:45 ` Ken Brown ` (2 more replies) 0 siblings, 3 replies; 23+ messages in thread From: Ken Brown @ 2012-12-07 13:04 UTC (permalink / raw) To: 13112 The cygw32 build of emacs tries to use many X11 features if the builder has the appropriate development packages installed. For example, HAVE_GSETTINGS and HAVE_GCONF will be defined. This causes serious problems, as detailed starting at http://cygwin.com/ml/cygwin/2012-12/msg00070.html In GNU Emacs 24.2.90.1 (i686-pc-cygwin) of 2012-11-27 on desktop-new Windowing system distributor `Microsoft Corp.', version 0.0.0 Configured using: `configure '--srcdir=/home/kbrown/src/cygemacs/emacs-24.2.90-1/src/emacs-24.2.90' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--libexecdir=/usr/lib' '--datadir=/usr/share' '--localstatedir=/var' '--sysconfdir=/etc' '--datarootdir=/usr/share' '--docdir=/usr/share/doc/emacs' '-C' '--with-w32' 'CC=gcc' 'CFLAGS=-ggdb -O2 -pipe -fdebug-prefix-map=/home/kbrown/src/cygemacs/emacs-24.2.90-1/build=/usr/src/debug/emacs-24.2.90-1 -fdebug-prefix-map=/home/kbrown/src/cygemacs/emacs-24.2.90-1/src/emacs-24.2.90=/usr/src/debug/emacs-24.2.90-1' 'LDFLAGS=-L/usr/lib/ncursesw' 'LIBS=' 'CPPFLAGS=-I/usr/include/ncursesw'' Important settings: value of $LANG: en_US.UTF-8 locale-coding-system: utf-8-unix default enable-multibyte-characters: t Major mode: Fundamental Minor modes in effect: show-paren-mode: t display-time-mode: t delete-selection-mode: t tooltip-mode: t mouse-wheel-mode: t tool-bar-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t temp-buffer-resize-mode: t buffer-read-only: t line-number-mode: t transient-mark-mode: t Recent input: M-x r e p o r <tab> <return> Recent messages: Loading /home/kbrown/emacs/.custom-24.el (source)... Loading delsel...done Loading time...done Loading help-at-pt...done Loading paren...done Loading /home/kbrown/emacs/.custom-24.el (source)...done Loading /home/kbrown/emacs/cygwin-init.el (source)...done For information about GNU Emacs and the GNU system, type C-h C-a. Load-path shadows: None found. Features: (shadow gnus-util mail-extr emacsbug message cl-macs gv format-spec rfc822 mml mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils dired edmacro kmacro solar cal-dst planner-diary cl diary-lib diary-loaddefs planner-publish muse-xml planner cal-menu calendar cal-loaddefs sort muse-colors muse-latex muse-html muse-xml-common cus-edit muse-publish muse-project muse-protocols muse-regexps wid-edit derived muse muse-nested-tags muse-mode muse-autoloads info easymenu package preview-latex tex-site auto-loads saveplace uniquify advice help-fns cl-lib advice-preload paren help-at-pt time delsel cus-start cus-load time-date tooltip ediff-hook vc-hooks lisp-float-type mwheel w32-common-fns disp-table w32-win w32-vars tool-bar dnd fontset image regexp-opt fringe tabulated-list newcomment lisp-mode register page menu-bar rfn-eshadow timer select scroll-bar mouse jit-lock font-lock syntax facemenu font-core frame cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean japanese hebrew greek romanian slovak czech european ethiopic indian cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev minibuffer loaddefs button faces cus-face macroexp files text-properties overlay sha1 md5 base64 format env code-pages mule custom widget hashtable-print-readable backquote make-network-process dbusbind w32 multi-tty emacs) *** E-Mail body has been placed on clipboard, please paste it here! *** ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 13:04 bug#13112: 24.2.90; The cygw32 build should disable X11 Ken Brown @ 2012-12-07 14:45 ` Ken Brown 2012-12-07 18:01 ` Glenn Morris 2012-12-11 17:30 ` Achim Gratz 2 siblings, 0 replies; 23+ messages in thread From: Ken Brown @ 2012-12-07 14:45 UTC (permalink / raw) To: 13112 On 12/7/2012 8:04 AM, Ken Brown wrote: > The cygw32 build of emacs tries to use many X11 features if the builder > has the appropriate development packages installed. For example, > HAVE_GSETTINGS and HAVE_GCONF will be defined. This causes serious > problems, as detailed starting at > > http://cygwin.com/ml/cygwin/2012-12/msg00070.html A workaround is to add the configure options --with-x=no and --without-xim, but it shouldn't be hard to modify the configure script so that these options are implied by --with-w32. I don't know enough about autoconf to immediately see how to do that. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 13:04 bug#13112: 24.2.90; The cygw32 build should disable X11 Ken Brown 2012-12-07 14:45 ` Ken Brown @ 2012-12-07 18:01 ` Glenn Morris 2012-12-07 18:24 ` Achim Gratz 2012-12-11 17:30 ` Achim Gratz 2 siblings, 1 reply; 23+ messages in thread From: Glenn Morris @ 2012-12-07 18:01 UTC (permalink / raw) To: Ken Brown; +Cc: 13112 Ken Brown wrote: > The cygw32 build of emacs tries to use many X11 features if the builder > has the appropriate development packages installed. For example, > HAVE_GSETTINGS and HAVE_GCONF will be defined. I don't see how that is possible. configure does: if test "${HAVE_W32}" = "yes"; then window_system=w32 [...] fi [...] HAVE_X11=no case "${window_system}" in x11 ) HAVE_X11=yes [...] w32 ) [...] esac [...] HAVE_GSETTINGS=no if test "${HAVE_X11}" = "yes" && test "${with_gsettings}" = "yes"; then ... fi So I think you need to provide more details. > http://cygwin.com/ml/cygwin/2012-12/msg00070.html This talks about dbus. ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 18:01 ` Glenn Morris @ 2012-12-07 18:24 ` Achim Gratz 2012-12-07 18:40 ` Glenn Morris 0 siblings, 1 reply; 23+ messages in thread From: Achim Gratz @ 2012-12-07 18:24 UTC (permalink / raw) To: 13112 Glenn Morris writes: >> http://cygwin.com/ml/cygwin/2012-12/msg00070.html > > This talks about dbus. Which is involved, but as it turns out not responsible. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 18:24 ` Achim Gratz @ 2012-12-07 18:40 ` Glenn Morris 2012-12-07 19:18 ` Achim Gratz 0 siblings, 1 reply; 23+ messages in thread From: Glenn Morris @ 2012-12-07 18:40 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112 Achim Gratz wrote: > Glenn Morris writes: >>> http://cygwin.com/ml/cygwin/2012-12/msg00070.html >> >> This talks about dbus. > > Which is involved, but as it turns out not responsible. Maybe you could summarize what the actual problem is, then. ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 18:40 ` Glenn Morris @ 2012-12-07 19:18 ` Achim Gratz 2012-12-07 21:23 ` Eli Zaretskii ` (2 more replies) 0 siblings, 3 replies; 23+ messages in thread From: Achim Gratz @ 2012-12-07 19:18 UTC (permalink / raw) To: 13112 Glenn Morris writes: > Maybe you could summarize what the actual problem is, then. The problem, as far as I have been able to determine, is that my init file set a default font that does only exist in X11 but not Windows, so it was illegal for the cygw32 build, but somehow that managed to sneak past Emacs' guards and apparently activated X11 code paths that should not have been in there to begin with. This then made Emacs hang whenever it should display UI dialogs (like the file chooser). Interestingly if dbus was started then somehow everything kept working (I had to manually switch the font from the first in the list, which happened to be Arial, to something fixed-width). If I remove the default font customization in my .emacs or arrange for that font to be a Windows font (or simply start "emacs -Q"), then it does not matter whether or not dbus has been started, so I'd say it is a red herring as far as this bug report is concerned. I'm using the test version that Ken has provided, so I can't answer any questions on how the build has been configured. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 19:18 ` Achim Gratz @ 2012-12-07 21:23 ` Eli Zaretskii 2012-12-07 21:45 ` Ken Brown 2012-12-07 21:32 ` Ken Brown [not found] ` <mailman.14806.1354915487.855.bug-gnu-emacs@gnu.org> 2 siblings, 1 reply; 23+ messages in thread From: Eli Zaretskii @ 2012-12-07 21:23 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112 > From: Achim Gratz <Stromeko@nexgo.de> > Date: Fri, 07 Dec 2012 20:18:12 +0100 > > Glenn Morris writes: > > Maybe you could summarize what the actual problem is, then. > > The problem, as far as I have been able to determine, is that my init > file set a default font that does only exist in X11 but not Windows, so > it was illegal for the cygw32 build, but somehow that managed to sneak > past Emacs' guards and apparently activated X11 code paths that should > not have been in there to begin with. This then made Emacs hang > whenever it should display UI dialogs (like the file chooser). Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a cygw32 Emacs? They shouldn't, AFAIU. ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 21:23 ` Eli Zaretskii @ 2012-12-07 21:45 ` Ken Brown 0 siblings, 0 replies; 23+ messages in thread From: Ken Brown @ 2012-12-07 21:45 UTC (permalink / raw) To: Eli Zaretskii; +Cc: Achim Gratz, 13112 On 12/7/2012 4:23 PM, Eli Zaretskii wrote: >> From: Achim Gratz <Stromeko@nexgo.de> >> Date: Fri, 07 Dec 2012 20:18:12 +0100 >> >> Glenn Morris writes: >>> Maybe you could summarize what the actual problem is, then. >> >> The problem, as far as I have been able to determine, is that my init >> file set a default font that does only exist in X11 but not Windows, so >> it was illegal for the cygw32 build, but somehow that managed to sneak >> past Emacs' guards and apparently activated X11 code paths that should >> not have been in there to begin with. This then made Emacs hang >> whenever it should display UI dialogs (like the file chooser). > > Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a > cygw32 Emacs? They shouldn't, AFAIU. They're not. I've caused some confusion, and we need to start from scratch. See my previous message. Ken Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 19:18 ` Achim Gratz 2012-12-07 21:23 ` Eli Zaretskii @ 2012-12-07 21:32 ` Ken Brown 2012-12-08 11:29 ` Achim Gratz [not found] ` <mailman.14806.1354915487.855.bug-gnu-emacs@gnu.org> 2 siblings, 1 reply; 23+ messages in thread From: Ken Brown @ 2012-12-07 21:32 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112 On 12/7/2012 2:18 PM, Achim Gratz wrote: > Glenn Morris writes: >> Maybe you could summarize what the actual problem is, then. > > The problem, as far as I have been able to determine, is that my init > file set a default font that does only exist in X11 but not Windows, so > it was illegal for the cygw32 build, but somehow that managed to sneak > past Emacs' guards and apparently activated X11 code paths that should > not have been in there to begin with. This then made Emacs hang > whenever it should display UI dialogs (like the file chooser). > > Interestingly if dbus was started then somehow everything kept working > (I had to manually switch the font from the first in the list, which > happened to be Arial, to something fixed-width). If I remove the > default font customization in my .emacs or arrange for that font to be a > Windows font (or simply start "emacs -Q"), then it does not matter > whether or not dbus has been started, so I'd say it is a red herring as > far as this bug report is concerned. > > I'm using the test version that Ken has provided, so I can't answer any > questions on how the build has been configured. The configure options can be seen in my original bug report. It turns out that I must have done something stupid when I claimed that HAVE_GSETTINGS and HAVE_GCONF were defined. I can no longer reproduce that, so Glenn is right. At this point I don't know whether or not there is an emacs bug here. I'm sorry for the confusion I caused. So let's start from scratch. Can you give a detailed, step-by-step procedure for reproducing the problem? I'd like to see if I can reproduce it. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 21:32 ` Ken Brown @ 2012-12-08 11:29 ` Achim Gratz 2012-12-08 12:23 ` Ken Brown 0 siblings, 1 reply; 23+ messages in thread From: Achim Gratz @ 2012-12-08 11:29 UTC (permalink / raw) To: 13112 Ken Brown writes: > So let's start from scratch. Can you give a detailed, step-by-step > procedure for reproducing the problem? I'd like to see if I can > reproduce it. I'm not near any system running Windows, so I can't test it myself, but I hope the following will do: 1. Nix all configuration files, then start emacs-X11 and set the default font to "DejaVu Sans Mono" and "Save Options". Check that it got saved in the "(custom-set-faces" section in the appropriate init file. 2. Do not start X11 or dbus. From a freshly started mintty, start emacs-w32 so that it reads the configuration file with the default font. It should start with whatever font is the first one in your Windows font list instead of the default monospace font it would use when started with "-Q". Now try to select File->Open from the menu bar. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 11:29 ` Achim Gratz @ 2012-12-08 12:23 ` Ken Brown 2012-12-08 12:42 ` Ken Brown 2012-12-08 14:10 ` Achim Gratz 0 siblings, 2 replies; 23+ messages in thread From: Ken Brown @ 2012-12-08 12:23 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112 On 12/8/2012 6:29 AM, Achim Gratz wrote: > Ken Brown writes: >> So let's start from scratch. Can you give a detailed, step-by-step >> procedure for reproducing the problem? I'd like to see if I can >> reproduce it. > > I'm not near any system running Windows, so I can't test it myself, but > I hope the following will do: > > 1. Nix all configuration files, then start emacs-X11 and set the default > font to "DejaVu Sans Mono" and "Save Options". Check that it got saved in > the "(custom-set-faces" section in the appropriate init file. I've done that, and I now have a ~/.emacs with the following contents: (custom-set-variables ;; custom-set-variables was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. ) (custom-set-faces ;; custom-set-faces was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. '(default ((t (:family "DejaVu Sans Mono" :foundry "unknown" :slant normal :weight normal :height 113 :width normal))))) And I've moved ~/.Xdefaults and /usr/share/emacs/site-lisp out of the way. ps shows no processes except mintty and bash. > 2. Do not start X11 or dbus. From a freshly started mintty, start > emacs-w32 so that it reads the configuration file with the default font. > It should start with whatever font is the first one in your Windows font > list instead of the default monospace font it would use when started > with "-Q". Now try to select File->Open from the menu bar. $ emacs-w32 & emacs-w32 opens in a new window. Options -> Set Default Font shows that emacs is using DejaVu Sans Mono-11. File -> Open works fine. I wonder why emacs-w32 finds DejaVu Sans Mono on my system but not on yours? I guess that's not really relevant to this bug, but it does mean that I can't currently reproduce the problem and so I can't debug it. If you can consistently reproduce it, I think you might have to do it under gdb (or attach gdb when emacs hangs) and see if you can figure out what's going on. I did reproduce the hang two nights ago (with different steps), but I was tired and making mistakes, and I don't remember exactly what I did. I know from previous discussions that you use tcsh as your shell. Could there be something in your tcsh configuration files that's interfering? Or is there anything in your environment that could explain this? Maybe you should try this from a bash shell and a clean environment. If you want to send me your cygcheck output off list, I can see if I spot any obvious differences between your system and mine. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 12:23 ` Ken Brown @ 2012-12-08 12:42 ` Ken Brown 2012-12-08 13:08 ` Achim Gratz 2012-12-08 14:10 ` Achim Gratz 1 sibling, 1 reply; 23+ messages in thread From: Ken Brown @ 2012-12-08 12:42 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112 On 12/8/2012 7:23 AM, Ken Brown wrote: > On 12/8/2012 6:29 AM, Achim Gratz wrote: >> Ken Brown writes: >>> So let's start from scratch. Can you give a detailed, step-by-step >>> procedure for reproducing the problem? I'd like to see if I can >>> reproduce it. >> >> I'm not near any system running Windows, so I can't test it myself, but >> I hope the following will do: >> >> 1. Nix all configuration files, then start emacs-X11 and set the default >> font to "DejaVu Sans Mono" and "Save Options". Check that it got >> saved in >> the "(custom-set-faces" section in the appropriate init file. > > I've done that, and I now have a ~/.emacs with the following contents: > > (custom-set-variables > ;; custom-set-variables was added by Custom. > ;; If you edit it by hand, you could mess it up, so be careful. > ;; Your init file should contain only one such instance. > ;; If there is more than one, they won't work right. > ) > (custom-set-faces > ;; custom-set-faces was added by Custom. > ;; If you edit it by hand, you could mess it up, so be careful. > ;; Your init file should contain only one such instance. > ;; If there is more than one, they won't work right. > '(default ((t (:family "DejaVu Sans Mono" :foundry "unknown" :slant > normal :weight normal :height 113 :width normal))))) > > And I've moved ~/.Xdefaults and /usr/share/emacs/site-lisp out of the > way. ps shows no processes except mintty and bash. > >> 2. Do not start X11 or dbus. From a freshly started mintty, start >> emacs-w32 so that it reads the configuration file with the default font. >> It should start with whatever font is the first one in your Windows font >> list instead of the default monospace font it would use when started >> with "-Q". Now try to select File->Open from the menu bar. > > $ emacs-w32 & > > emacs-w32 opens in a new window. Options -> Set Default Font shows that > emacs is using DejaVu Sans Mono-11. File -> Open works fine. > > I wonder why emacs-w32 finds DejaVu Sans Mono on my system but not on > yours? I guess that's not really relevant to this bug, but it does mean > that I can't currently reproduce the problem and so I can't debug it. If > you can consistently reproduce it, I think you might have to do it under > gdb (or attach gdb when emacs hangs) and see if you can figure out > what's going on. > > I did reproduce the hang two nights ago (with different steps), but I > was tired and making mistakes, and I don't remember exactly what I did. > > I know from previous discussions that you use tcsh as your shell. Could > there be something in your tcsh configuration files that's interfering? > Or is there anything in your environment that could explain this? > Maybe you should try this from a bash shell and a clean environment. If > you want to send me your cygcheck output off list, I can see if I spot > any obvious differences between your system and mine. I just repeated the experiment, but this time with Droid instead of DejaVu. This time emacs-w32 didn't find the font and chose Arial. But File->Open still worked. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 12:42 ` Ken Brown @ 2012-12-08 13:08 ` Achim Gratz 2012-12-08 15:57 ` Ken Brown 0 siblings, 1 reply; 23+ messages in thread From: Achim Gratz @ 2012-12-08 13:08 UTC (permalink / raw) To: 13112 Ken Brown writes: > I just repeated the experiment, but this time with Droid instead of > DejaVu. This time emacs-w32 didn't find the font and chose Arial. OK, so that part seems to work the same way. > But File->Open still worked. Did it work after some delay or right away? When I've started dbus and tried this, I've only been getting the dialog after an initial delay of two or three seconds. Subsequent invocations didn't have that delay. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 13:08 ` Achim Gratz @ 2012-12-08 15:57 ` Ken Brown 0 siblings, 0 replies; 23+ messages in thread From: Ken Brown @ 2012-12-08 15:57 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112 On 12/8/2012 8:08 AM, Achim Gratz wrote: > Ken Brown writes: >> I just repeated the experiment, but this time with Droid instead of >> DejaVu. This time emacs-w32 didn't find the font and chose Arial. > > OK, so that part seems to work the same way. > >> But File->Open still worked. > > Did it work after some delay or right away? When I've started dbus and > tried this, I've only been getting the dialog after an initial delay of > two or three seconds. Subsequent invocations didn't have that delay. It worked right away. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 12:23 ` Ken Brown 2012-12-08 12:42 ` Ken Brown @ 2012-12-08 14:10 ` Achim Gratz 1 sibling, 0 replies; 23+ messages in thread From: Achim Gratz @ 2012-12-08 14:10 UTC (permalink / raw) To: 13112 Ken Brown writes: > I wonder why emacs-w32 finds DejaVu Sans Mono on my system but not on > yours? It's certainly possible that you've installed it in Windows as well. I'd simply use another font (or even a wholLy non-existing one). > I guess that's not really relevant to this bug, but it does > mean that I can't currently reproduce the problem and so I can't debug > it. If you can consistently reproduce it, I think you might have to do > it under gdb (or attach gdb when emacs hangs) and see if you can > figure out what's going on. I'll have to sneak it in somehow next week trying to reproduce this on a different machine (running XP for testing) that has a clean Cygwin installation. I've been testing a lot on my own machine for the last few weeks and I don't really trust that installation anymore, but I can't nuke it right now. > I know from previous discussions that you use tcsh as your shell. > Could there be something in your tcsh configuration files that's > interfering? Or is there anything in your environment that could > explain this? Maybe you should try this from a bash shell and a clean > environment. If you want to send me your cygcheck output off list, I > can see if I spot any obvious differences between your system and > mine. I can try it again in bash and I should have nothing non-standard in my .bashrc, but will check again to make sure. I've mentioned tcsh because it is handling job control and some I/O issues differently than other shells and that has been triggering different behaviour in the past. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <mailman.14806.1354915487.855.bug-gnu-emacs@gnu.org>]
* Re: bug#13112: 24.2.90; The cygw32 build should disable X11 [not found] ` <mailman.14806.1354915487.855.bug-gnu-emacs@gnu.org> @ 2012-12-07 22:19 ` Burton Samograd 2012-12-07 22:36 ` Daniel Colascione [not found] ` <mailman.14821.1354919805.855.bug-gnu-emacs@gnu.org> 0 siblings, 2 replies; 23+ messages in thread From: Burton Samograd @ 2012-12-07 22:19 UTC (permalink / raw) To: bug-gnu-emacs Eli Zaretskii <eliz@gnu.org> writes: >> From: Achim Gratz <Stromeko@nexgo.de> >> Date: Fri, 07 Dec 2012 20:18:12 +0100 >> >> Glenn Morris writes: >> > Maybe you could summarize what the actual problem is, then. >> >> The problem, as far as I have been able to determine, is that my init >> file set a default font that does only exist in X11 but not Windows, so >> it was illegal for the cygw32 build, but somehow that managed to sneak >> past Emacs' guards and apparently activated X11 code paths that should >> not have been in there to begin with. This then made Emacs hang >> whenever it should display UI dialogs (like the file chooser). > > Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a > cygw32 Emacs? They shouldn't, AFAIU. They are on my build, but I have the proper X11 headers and libraries installed in my cygwin. I like it that way so I can display my emacs with an x-server. -- Burton Samograd ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 22:19 ` Burton Samograd @ 2012-12-07 22:36 ` Daniel Colascione [not found] ` <mailman.14821.1354919805.855.bug-gnu-emacs@gnu.org> 1 sibling, 0 replies; 23+ messages in thread From: Daniel Colascione @ 2012-12-07 22:36 UTC (permalink / raw) To: Burton Samograd; +Cc: 13112 [-- Attachment #1: Type: text/plain, Size: 1174 bytes --] On 12/7/12 2:19 PM, Burton Samograd wrote: > Eli Zaretskii <eliz@gnu.org> writes: > >>> From: Achim Gratz <Stromeko@nexgo.de> >>> Date: Fri, 07 Dec 2012 20:18:12 +0100 >>> >>> Glenn Morris writes: >>>> Maybe you could summarize what the actual problem is, then. >>> >>> The problem, as far as I have been able to determine, is that my init >>> file set a default font that does only exist in X11 but not Windows, so >>> it was illegal for the cygw32 build, but somehow that managed to sneak >>> past Emacs' guards and apparently activated X11 code paths that should >>> not have been in there to begin with. This then made Emacs hang >>> whenever it should display UI dialogs (like the file chooser). >> >> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a >> cygw32 Emacs? They shouldn't, AFAIU. > > They are on my build, but I have the proper X11 headers and libraries > installed in my cygwin. I like it that way so I can display my emacs > with an x-server. But you didn't build Emacs with --with-w32, did you? As much as I'd like a single Emacs binary to support both X11 and W32, we're a long way away from there. [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 235 bytes --] ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <mailman.14821.1354919805.855.bug-gnu-emacs@gnu.org>]
* Re: bug#13112: 24.2.90; The cygw32 build should disable X11 [not found] ` <mailman.14821.1354919805.855.bug-gnu-emacs@gnu.org> @ 2012-12-08 1:51 ` Burton Samograd 2012-12-08 8:06 ` Eli Zaretskii [not found] ` <mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org> 0 siblings, 2 replies; 23+ messages in thread From: Burton Samograd @ 2012-12-08 1:51 UTC (permalink / raw) To: bug-gnu-emacs Daniel Colascione <dancol@dancol.org> writes: > On 12/7/12 2:19 PM, Burton Samograd wrote: >> Eli Zaretskii <eliz@gnu.org> writes: >> >>>> From: Achim Gratz <Stromeko@nexgo.de> >>>> Date: Fri, 07 Dec 2012 20:18:12 +0100 >>>> >>>> Glenn Morris writes: >>>>> Maybe you could summarize what the actual problem is, then. >>>> >>>> The problem, as far as I have been able to determine, is that my init >>>> file set a default font that does only exist in X11 but not Windows, so >>>> it was illegal for the cygw32 build, but somehow that managed to sneak >>>> past Emacs' guards and apparently activated X11 code paths that should >>>> not have been in there to begin with. This then made Emacs hang >>>> whenever it should display UI dialogs (like the file chooser). >>> >>> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a >>> cygw32 Emacs? They shouldn't, AFAIU. >> >> They are on my build, but I have the proper X11 headers and libraries >> installed in my cygwin. I like it that way so I can display my emacs >> with an x-server. > > But you didn't build Emacs with --with-w32, did you? As much as I'd > like a single Emacs binary to support both X11 and W32, we're a long > way away from there. No, I don't use --with-w32. I just wanted to make sure a feature I use didn't get removed from the build :) -- Burton Samograd ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 1:51 ` Burton Samograd @ 2012-12-08 8:06 ` Eli Zaretskii [not found] ` <mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org> 1 sibling, 0 replies; 23+ messages in thread From: Eli Zaretskii @ 2012-12-08 8:06 UTC (permalink / raw) To: Burton Samograd; +Cc: 13112 > From: Burton Samograd <burton@samograd.ca> > Date: Fri, 07 Dec 2012 18:51:59 -0700 > > >>> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a > >>> cygw32 Emacs? They shouldn't, AFAIU. > >> > >> They are on my build, but I have the proper X11 headers and libraries > >> installed in my cygwin. I like it that way so I can display my emacs > >> with an x-server. > > > > But you didn't build Emacs with --with-w32, did you? As much as I'd > > like a single Emacs binary to support both X11 and W32, we're a long > > way away from there. > > No, I don't use --with-w32. Then yours is not the cygw32 build, and I was asking only about that. > I just wanted to make sure a feature I use didn't get removed from > the build :) How can you seriously think we would consider removing X11 support from Emacs? ^ permalink raw reply [flat|nested] 23+ messages in thread
[parent not found: <mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org>]
* Re: bug#13112: 24.2.90; The cygw32 build should disable X11 [not found] ` <mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org> @ 2012-12-08 18:37 ` Burton Samograd 2012-12-09 0:09 ` Ken Brown 0 siblings, 1 reply; 23+ messages in thread From: Burton Samograd @ 2012-12-08 18:37 UTC (permalink / raw) To: bug-gnu-emacs Eli Zaretskii <eliz@gnu.org> writes: >> From: Burton Samograd <burton@samograd.ca> >> Date: Fri, 07 Dec 2012 18:51:59 -0700 >> >> >>> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a >> >>> cygw32 Emacs? They shouldn't, AFAIU. >> >> >> >> They are on my build, but I have the proper X11 headers and libraries >> >> installed in my cygwin. I like it that way so I can display my emacs >> >> with an x-server. >> > >> > But you didn't build Emacs with --with-w32, did you? As much as I'd >> > like a single Emacs binary to support both X11 and W32, we're a long >> > way away from there. >> >> No, I don't use --with-w32. > > Then yours is not the cygw32 build, and I was asking only about that. > >> I just wanted to make sure a feature I use didn't get removed from >> the build :) > > How can you seriously think we would consider removing X11 support > from Emacs? I thought you were discussing removing X11 support from the windows builds: >> >>> Are you saying that xterm.c, xfns.c, and xmenu.c are compiled into a >> >>> cygw32 Emacs? They shouldn't, AFAIU. I didn't realize that cygw32 meant that you use the --with-w32 options. Cygw32 was something I had never heard of and I thought it just meant the regular cygwin builds. I don't think that use of emacs through X11 on windows is a hugely common occurance, but I use it so I thought I would use my voice. Just some confusion about what you were actually talking about, so my mistake. -- Burton Samograd ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-08 18:37 ` Burton Samograd @ 2012-12-09 0:09 ` Ken Brown 0 siblings, 0 replies; 23+ messages in thread From: Ken Brown @ 2012-12-09 0:09 UTC (permalink / raw) To: Burton Samograd; +Cc: 13112 On 12/8/2012 1:37 PM, Burton Samograd wrote: > I didn't realize that cygw32 meant that you use the --with-w32 options. > Cygw32 was something I had never heard of and I thought it just meant > the regular cygwin builds. > > I don't think that use of emacs through X11 on windows is a hugely > common occurance If you build emacs on any POSIXish system, it uses X11 (and GTK+) by default, provided the builder has the necessary libraries installed. Cygwin is no exception. You have to specify a configure option to make it do something different. For example, --with-x=no creates a non-GUI version of emacs, and --with-w32 creates a version that uses the native Windows GUI for display instead of X11. It's this build that has been referred to as the cygw32 build on the emacs-devel mailing list. In the Cygwin distribution, this build produces what's called the emacs-w32 package, as of about a week ago. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-07 13:04 bug#13112: 24.2.90; The cygw32 build should disable X11 Ken Brown 2012-12-07 14:45 ` Ken Brown 2012-12-07 18:01 ` Glenn Morris @ 2012-12-11 17:30 ` Achim Gratz 2012-12-11 18:29 ` Ken Brown 2 siblings, 1 reply; 23+ messages in thread From: Achim Gratz @ 2012-12-11 17:30 UTC (permalink / raw) To: 13112 Ken Brown writes: > The cygw32 build of emacs tries to use many X11 features if the builder > has the appropriate development packages installed. For example, > HAVE_GSETTINGS and HAVE_GCONF will be defined. This causes serious > problems, as detailed starting at Hi Ken, sorry it took so long, but I've first updated my Cygwin installation to the latest and greatest and since the rebase map was starting to look wierd I also did a full rebase of everything. Result: I cannot reproduce the hang-ups anymore for the cygw32 build and the Gtk dialogs come up noticeably faster as well. I'll have to assume BLODA at this point since none of the updates (except libtasn1) was even remotely related to Emacs. If I find another way to reproduce the error again, I'll try to get a backtrace of all threads (I have all debuginfo packages installed now). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html ^ permalink raw reply [flat|nested] 23+ messages in thread
* bug#13112: 24.2.90; The cygw32 build should disable X11 2012-12-11 17:30 ` Achim Gratz @ 2012-12-11 18:29 ` Ken Brown 0 siblings, 0 replies; 23+ messages in thread From: Ken Brown @ 2012-12-11 18:29 UTC (permalink / raw) To: Achim Gratz; +Cc: 13112-done > wierd I also did a full rebase of everything. Result: I cannot > reproduce the hang-ups anymore for the cygw32 build and the Gtk dialogs > come up noticeably faster as well. I'll have to assume BLODA at this > point since none of the updates (except libtasn1) was even remotely > related to Emacs. If I find another way to reproduce the error again, > I'll try to get a backtrace of all threads (I have all debuginfo > packages installed now). OK, thanks. I'm closing the bug for now, but it can be re-opened if you're able to reproduce it again. Ken ^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2012-12-11 18:29 UTC | newest] Thread overview: 23+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-12-07 13:04 bug#13112: 24.2.90; The cygw32 build should disable X11 Ken Brown 2012-12-07 14:45 ` Ken Brown 2012-12-07 18:01 ` Glenn Morris 2012-12-07 18:24 ` Achim Gratz 2012-12-07 18:40 ` Glenn Morris 2012-12-07 19:18 ` Achim Gratz 2012-12-07 21:23 ` Eli Zaretskii 2012-12-07 21:45 ` Ken Brown 2012-12-07 21:32 ` Ken Brown 2012-12-08 11:29 ` Achim Gratz 2012-12-08 12:23 ` Ken Brown 2012-12-08 12:42 ` Ken Brown 2012-12-08 13:08 ` Achim Gratz 2012-12-08 15:57 ` Ken Brown 2012-12-08 14:10 ` Achim Gratz [not found] ` <mailman.14806.1354915487.855.bug-gnu-emacs@gnu.org> 2012-12-07 22:19 ` Burton Samograd 2012-12-07 22:36 ` Daniel Colascione [not found] ` <mailman.14821.1354919805.855.bug-gnu-emacs@gnu.org> 2012-12-08 1:51 ` Burton Samograd 2012-12-08 8:06 ` Eli Zaretskii [not found] ` <mailman.14838.1354954003.855.bug-gnu-emacs@gnu.org> 2012-12-08 18:37 ` Burton Samograd 2012-12-09 0:09 ` Ken Brown 2012-12-11 17:30 ` Achim Gratz 2012-12-11 18:29 ` Ken Brown
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.