Re: Window size specification ignored

[August Karlstrom]

Peter Dyballa wrote:
> I wanted to make you try
>
>     /usr/bin/emacs -q

OK

   $ /usr/bin/emacs -q -g <w>x<h>

works as expected. Without the geometry option Emacs starts maximized.

> and
>
>     /usr/bin/emacs -Q

If I do this Emacs starts (maximized) with the message 'Unknown option 
-Q' in the mode line. If I invoke

   $ /usr/bin/emacs -q --no-site-file -g <w>x<h>

the geometry specification works as expected. Without it Emacs starts 
maximized. In all cases I use my minimal ~/.emacs file

   (setq default-frame-alist
         '((width . 80)
           (height . 24)
           (foreground-color . "wheat")
           (background-color . "darkslategrey")))

> The latter method should launch GNU Emacs without loading *any* local 
> Ubuntu customisation. If they launch differently, then you have a clue 
> that some Ubuntu customisation file is causing the too big appearence. 
> If they appear in both cases the same then there can be an X resource 
> causing this. 

Yes, I get the same behavior with `-q' and `-q --no-site-file'.

> Check files like .xinitrc and .Xdefaults, 

I have no such files:

   $ locate .xinitrc
   $ locate .Xdefaults

> and check the 
> output of 'xrdb -query' too! 

And what should I look for?

   $ xrdb -query | grep -i emacs
   Emacs*Background:       #ffffff
   Emacs*Dialog*background:        #efebe7
   Emacs*Dialog*foreground:        #101010
   Emacs*Foreground:       #000000
   Emacs*XlwScrollBar.Background:  #efebe7
   Emacs*XlwScrollBar.Foreground:  #101010
   Emacs*backgroundToolBarColor:   #efebe7
   Emacs*bottomToolBarShadowColor: #efebe7
   Emacs*menubar*background:       #efebe7
   Emacs*menubar*foreground:       #101010
   Emacs*popup*Background: #efebe7
   Emacs*popup*Foreground: #101010
   Emacs*toolBarShadowThickness:   0
   Emacs*topToolBarShadowColor:    #efebe7
   Emacs.default.attributeBackground:      #ffffff
   Emacs.default.attributeForeground:      #000000

> Comment out lines in .xinitrc, the file 
> that launches X11, which have to do with xrdb, log off, and log in 
> again. Now you should have less X resources set.

As mentioned, I have no such file.

> It's good use to launch an application by its path name -- but what when 
> this path name is a script that launches the final application? It's not 
> likely, but ps would reveal this.

   $ ls -l /usr/bin/emacs
   lrwxrwxrwx  1 root root 23 2005-09-08 23:36 /usr/bin/emacs ->
   /etc/alternatives/emacs
   $ ls -l /etc/alternatives/emacs
   lrwxrwxrwx  1 root root 18 2005-09-08 23:36 /etc/alternatives/emacs
   -> /usr/bin/emacs21-x
   $ ls -l /usr/bin/emacs21-x
   -rwxr-xr-x  1 root root 4359220 2005-03-05 02:43 /usr/bin/emacs21-x

The file /usr/bin/emacs21-x is a binary file.

> I have in Mac OS X these two aliases to check this:
>
>     for csh family: alias PS        "ps -lwwgx   | egrep UID\|\!:1 | 
> grep -v grep"
>     for  sh family: PS    () { ps -lwwgx  | egrep UID\|${1} | grep -v 
> grep ; }
>
> In a shell you simply type 'PS emacs' and you get something like:
>
> pete 161 /\ PS emacs
>   UID   PID  PPID CPU PRI NI      VSZ    RSS WCHAN  STAT  TT       TIME 
> COMMAND
>   501  4107  4094   0  31  0    53288  17432 -      S     ??    7:10.04 
> /usr/local/bin/emacs-22.0.50 -geometry 85x45+18+240
>   501 26465     1   0  31  0    22728    536 -      S     ??    0:00.01 
> -bin/tcsh -i -c /usr/local/bin/emacs-23.0.0 --debug-init -geometry  
> 100x57+666+44
>   501 26470 26465   0  31  0    75008  39136 -      R     ??    3:41.96 
> /usr/local/bin/emacs-23.0.0 --debug-init -geometry 100x57+666+44

I tried

   $ ps -lwwgx | egrep UID\|emacs | grep -v grep;
   Warning: bad ps syntax, perhaps a bogus '-'? See
   http://procps.sf.net/faq.html
   F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME
   COMMAND

Am I missing something?


Regards,

August