From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Sebastian Kaps <seb@toyland.sauerland.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: line spacing too big
Date: Fri, 7 Sep 2007 12:37:31 +0200 [thread overview]
Message-ID: <52B353CE-BE41-4585-9B34-CE84F1511971@Web.DE> (raw)
In-Reply-To: <87hcm74tbn.fsf@toyland.sauerland.de>
Am 06.09.2007 um 19:06 schrieb Sebastian Kaps:
> // Peter Dyballa writes:
>
>> One more try (I can't imagine more right now): run 'xrdb -remove'
>> which
>> should delete all recently set X resources (you can reload them
>> afterwards via 'xrdb -load ~/.Xdefaults' or such). When you now
>> launch
>> GNU Emacs with -Q it should launch quite pure and undisturbed ...
>
> Sorry, that also had no effect. I even tried launched a minimal X
> session (with just "xterm" in ~/.xinitrc) as another user and the
> problem still persisted :-(
>
This minimal session does not mean that no X resources are existing
or are set for this session. Besides making the output of 'xrdb -q'
empty there are still files with default X resources an X client can
find and read and apply ...
An option would be to activate Kubuntu (KDE instead of GNOME) or
Xubuntu (Xfce as Window Manager in a still GTK based environment but
less resources hungry). The ldd utility should list which dynamic
libraries GNU Emacs actually uses to check whether it's really not
depending on/using GTK.
Finally you can launch GNU Emacs on a different host and make it
display on your local machine. And vice versa. The first test will
make *some* GNU Emacs become the client of your local X server, so it
should behave (look) like your own GNU Emacs. (If not, then it's due
to binding to libraries and different X resources in files.) In the
second case, displaying your Ubuntu Emacsen remotely, they should
show up like *some* GNU Emacs of that remote machine on that remote
machine. If not, then again it's based on libraries and X resources
used.
You should provide the same fonts on both computers or some X font
server. This one might be another cause ...
The family of *trace programmes offers the ability to record all
files a binary programme opens.
--
Mit evolutionären Grüßen
Pete
"Evolution" o __o _o _
°\___o /0~ -\<, ^\___ /=\\_/-%
oo~_______ /\ /\______/ \_________O/ O_______________o===>-->O--o____
next prev parent reply other threads:[~2007-09-07 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 13:44 line spacing too big Sebastian Kaps
2007-09-05 21:32 ` Peter Dyballa
[not found] ` <mailman.384.1189027940.18990.help-gnu-emacs@gnu.org>
2007-09-05 22:18 ` Sebastian Kaps
2007-09-05 23:05 ` Peter Dyballa
[not found] ` <mailman.389.1189033552.18990.help-gnu-emacs@gnu.org>
2007-09-06 7:00 ` Sebastian Kaps
2007-09-06 9:38 ` Peter Dyballa
[not found] ` <mailman.410.1189071526.18990.help-gnu-emacs@gnu.org>
2007-09-06 10:28 ` Sebastian Kaps
2007-09-06 11:10 ` Peter Dyballa
[not found] ` <mailman.415.1189077010.18990.help-gnu-emacs@gnu.org>
2007-09-06 17:06 ` Sebastian Kaps
2007-09-07 10:37 ` Peter Dyballa [this message]
2007-09-07 15:37 ` Emacs stuck when error occurs in ange ftp brianjiang
[not found] ` <mailman.449.1189161567.18990.help-gnu-emacs@gnu.org>
2007-09-10 20:43 ` line spacing too big Sebastian Kaps
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=52B353CE-BE41-4585-9B34-CE84F1511971@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=seb@toyland.sauerland.de \
/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).