5 October 2005 Dear Mike, this morning, I received an email related to my XEmacs problems, which may also be of interest for you. Greetings and best regards Ernst Joachim #-------------------------------------------------------| | PD Dr. Ernst Joachim Weniger | | Institut für Physikalische und Theoretische Chemie | | Universität Regensburg | | D-93040 Regensburg, Germany | | Tel: +49 (0)941-943-4722 | | Fax: +49 (0)941-943-4719 | | Email: Joachim.Weniger(a)chemie.uni-regensburg.de | #-------------------------------------------------------| ---------- Forwarded message ---------- Date: Wed, 5 Oct 2005 00:17:32 -0700 (PDT) From: Matthew Schnaider <matt(a)lasr.cs.ucla.edu&gt; To: joachim.weniger(a)chemie.uni-regensburg.de Subject: Re: Bug Report to KDE about (X_Emacs Hello, I suffer from a similar problem to the xemacs resizing problem you experience. This problem occurs under Gnome for me, however, so it may be unrelated to your problem, but from your description, I believe they are at least related. For me, the resizing problem seems to be related to the custom-set-faces directive in custom.el. (custom-set-faces '(default ((t (:size "12pt" :family "Fixed"))) t)) If I comment it out, I get a window that starts at the correct dimensions and remains so. With the directive in place, my window starts the correct size and then shrinks. I am curious about whether or not the problem persists for you if you comment out your custom-set-faces directive. Also, for additional frames spawned using C-x 5 f, the resizing problem does not occur for subsequent windows. I would like to know if you see this as well. I would be interested to know if you observe the same behavior that I am seeing. (My window changes in height as well as width, but I attribute that to my selecting a font family with a different height than the default, which I believe you are not doing.) Any information you could provide me would be helpful. After much investigation, I don't see how this could be a window manager problem, and I'm still trying to find an explanation. Thanks, Matt Schnaider