unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Gaute Amundsen <gaute@div.org>
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Strange font / frame size problem makes emacs unusable.
Date: Sun, 25 Apr 2010 21:43:02 +0200	[thread overview]
Message-ID: <1272224582.9877.259.camel@totiki> (raw)
In-Reply-To: <0DD48519-2441-471E-AF01-6EF5CAA00644@Web.DE>

On Sun, 2010-04-25 at 10:28 +0200, Peter Dyballa wrote:
> Am 24.04.2010 um 22:53 schrieb Gaute Amundsen:
> 
> > Any ideas are appreciated.
> 
> 
> Font switching happens. Possible cause: GNU Emacs has an internal  
> default, X11 has a different X resource, GTK has its own settings. In  
> this sequence, presumingly, one overrides the elder. GTK makes, IMO,  
> things complicated since it customises compound ideas, comprised of  
> simple elements.

Well, it's not just fonts, is it? The buffer starts one line high, even
when the fonts are tiny, and that last screenshot where two lines fills
the screen is supposedly 11pt. fonts.
Come to think of it I should also mention that it looks like that last
shot, briefly during startup. 

I also notice now, that startup seems slower than it ought to be.
Takes around 12 seconds, while -nw is ~1 sec.
Cpu maxes out for some seconds there as well.


Hm.. not my specialty, but playing around with strace...
# strace -c emacs

(emacs:25774): GLib-WARNING **: g_set_prgname() called multiple times
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 42.18    0.004471           1      3660           poll
 39.57    0.004195           1      4724      2022 read
 11.28    0.001196           2       532           getdents64
...

# strace -c emacs -nw
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 66.73    0.000379           2       172           close
 13.56    0.000077           0       946       864 stat64
  6.87    0.000039           0       151           read
...

I figure a lot of those read errors must be from blocks like this.


--- SIGIO (I/O possible) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
read(3, "\1<\377\2L\0\0\0\0\0N\0N\0|\0 \0\341\1\1\0\22\0\0\0N\0N\0|
\0"..., 4096) = 396
read(3, 0x9f10018, 4096)                = -1 EAGAIN (Resource
temporarily unavailable)
read(3, 0x9f10018, 4096)                = -1 EAGAIN (Resource
temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3,
revents=POLLOUT}])
writev(3, [{"2\30\21\0\1\0<\0", 8},
{"-misc-fixed-medium-r-normal--161"..., 60}, {"", 0}], 3) = 68
poll([{fd=3, events=POLLIN}], 1, -1)    = 1 ([{fd=3, revents=POLLIN}])
--- SIGIO (I/O possible) @ 0 (0) ---


Something about fonts..., but I have to work on that..

> Check documentation, and check whether you have forgotten to migrate  
> ~/.Xdefaults and ~/.emacs.d/gtkrc or ~/.gtkrc, whichever gets used...

I have none of the those anywhere on the system.
You don't think I should try to narrow down where the cause might be a
bit more before I start reading docs? Seems to me I could read docs for
a week to cover the possible territory at this point.. :)

tried emacs -QD but no change.

emacs -fn lucidasans-24 looks more sensible during startup, but then
just the same behavior. Hm.. lucida is not an option in the "default
font" dialog, but is one of the hits in xlsfonts | grep -i sans.


Well, some new angles to work on anyway.

Thanks :)

Gaute









  reply	other threads:[~2010-04-25 19:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 20:53 Strange font / frame size problem makes emacs unusable Gaute Amundsen
2010-04-25  8:28 ` Peter Dyballa
2010-04-25 19:43   ` Gaute Amundsen [this message]
2010-04-25 21:49     ` Peter Dyballa
2010-04-26  5:28       ` tomas
2010-04-26  6:59         ` Gaute Amundsen
2010-04-26  9:44           ` Peter Dyballa
2010-04-26 10:05             ` Gaute Amundsen
2010-04-26 15:52               ` Peter Dyballa
2010-04-26 16:56                 ` Gaute Amundsen
2010-04-26  7:18       ` Gaute Amundsen
2010-04-26  9:36         ` Peter Dyballa
2010-04-26  9:58           ` Gaute Amundsen
2010-04-26 15:46             ` Peter Dyballa
2010-04-26 16:56               ` Gaute Amundsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1272224582.9877.259.camel@totiki \
    --to=gaute@div.org \
    --cc=Peter_Dyballa@Web.DE \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).