On Tue, Apr 13, 2010 at 14:16, Ken Brown kbr...@cornell.edu wrote:
On 4/12/2010 7:52 PM, Dan Tsafrir wrote:
On Tue, Apr 6, 2010 at 00:39, Jon TURNEYjon.tur...@dronecode.org.uk
wrote:
I've conducted a few repeated measurements and it looks as though
setting LANG to be en_US somewhat reduces
On Tue, Apr 13, 2010 at 17:22, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
The mechanism that loads ~/.Xdefaults into the X server resource database is
nicely obscure, so I'm not sure that -q actually avoids that.
The definitive way to check would be to move ~/.Xdefaults aside, restart the
On Tue, Apr 13, 2010 at 17:55, Markus Hoenicka
markus.hoeni...@mhoenicka.de wrote:
Jon TURNEY jon.tur...@dronecode.org.uk was heard to say:
So far it seems that (1) emacs takes a long time to start up (2) xterm
starts up quickly. Are there other X applications that you use and how do
they
On Wed, Apr 14, 2010 at 10:17, Dan Tsafrir da...@cs.technion.ac.il wrote:
On Tue, Apr 13, 2010 at 17:22, Jon TURNEY jon.tur...@dronecode.org.uk wrote:
[snip]
So far it seems that (1) emacs takes a long time to start up (2) xterm
starts up quickly. Are there other X applications that you use
Dan Tsafrir da...@cs.technion.ac.il was heard to say:
I wasn't able to strace emacs, but I am able to strace xclock (brining
it up, which when strace-ing takes several long minutes on my netbook,
and then immediately killing it).
Neither was I. I always get this error (the error number is
On Wed, 14 Apr 2010, Markus Hoenicka wrote:
This is where I have seen xterm to spend most of its time. In your log, this
block of statements appears to be repeated several times for each font it
checks in /etc/fonts. This would explain why it is related somehow to fonts
in your case.
It's a
On Wed, Apr 14, 2010 at 12:24, Markus Hoenicka
markus.hoeni...@mhoenicka.de wrote:
I've had a look at your strace log. I've noticed the same block of
statements which seems to be repeated over and over again (see my previous
post). Did you watch the strace output on the console in real time
Dan Tsafrir da...@cs.technion.ac.il was heard to say:
The two numbers at the beginning of each strace output line (like the
ones you quoted above) answer this question. I believe the first
number is elapsed microseconds since the previous line and the second
number is elapsed microseconds since
On 4/14/2010 5:24 AM, Markus Hoenicka wrote:
Dan Tsafrir was heard to say:
I wasn't able to strace emacs, but I am able to strace xclock (brining
it up, which when strace-ing takes several long minutes on my netbook,
and then immediately killing it).
Neither was I. I always get this error
Ken Brown writes:
That's because /usr/bin/emacs is a symlink. Try straceing emacs-X11.
Who'd have thunk? Thanks, that's going to make it easier then.
regards,
Markus
--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
10 matches
Mail list logo
