From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Window size specification ignored
Date: Mon, 12 Sep 2005 10:57:59 +0200 [thread overview]
Message-ID: <ba968ec8ad7ba057b4b3b557c8d9a001@Web.DE> (raw)
In-Reply-To: <cp4Ve.146106$dP1.502554@newsc.telia.net>
Am 12.09.2005 um 02:58 schrieb August Karlstrom:
> Am I missing something?
>
At least the correct Ubuntu ps syntax ... I am using a BSD style ps.
'man ps', inside Emacs as 'M-x manual-entry ps' or F1 F2, should be
your friend. And it's worth doing the experiments inside GNU Emacs in
its shell buffer.
Ubuntu's setup with so many sym-links reminds of Fink for Mac OS X: I
never knew exactly which file now was executing, and even worse: the
Fink folks messed up the site specific things with a lot of
intermediate and extra files that loaded each others for unknown
reasons (it is similiar to some so-called Carbon Emacsen). Do you have
an idea how much longer it takes to launch Fink's GNU Emacs 21.3.50
with -Q then without -Q? Minutes. Really.
Beside this I have the feeling that Ubuntu is using a pretty old Emacs.
Have you checked its version? This could explain that it does not
understand -Q. Apple's gift of GNU Emacs 21.2, for use inside a
terminal emulation only, does not understand -Q too.
Are you able to 'trace' a programme's execution, i.e. follow it opening
and closing files, doing system calls, receiving signals etc? This way
you would find which Ubuntu specific Elisp files were executed at
start-up ... but it's much easier to get GNU Emacs 22.0.50 from CVS and
compile it yourself. A (much better then) nice'd 'make bootstrap' in
the background will take one or two hours while you're having
breakfast, lunch, or dinner, or going shopping -- it should be more
satisfactory in the end! To do this you'll need many Ubuntu dev
packages, containing C header files needed for 'dev-elopment', i.e.
compiling a software.
--
Greetings
Pete
Without vi there is only GNU Emacs
prev parent reply other threads:[~2005-09-12 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 15:14 Window size specification ignored August Karlstrom
2005-09-11 16:40 ` Peter Dyballa
[not found] ` <mailman.6586.1126458402.20277.help-gnu-emacs@gnu.org>
2005-09-11 17:52 ` August Karlstrom
2005-09-11 21:54 ` Peter Dyballa
[not found] ` <mailman.6621.1126476194.20277.help-gnu-emacs@gnu.org>
2005-09-11 22:48 ` August Karlstrom
2005-09-11 23:35 ` Peter Dyballa
[not found] ` <mailman.6627.1126481765.20277.help-gnu-emacs@gnu.org>
2005-09-12 0:58 ` August Karlstrom
2005-09-12 8:57 ` Peter Dyballa [this message]
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=ba968ec8ad7ba057b4b3b557c8d9a001@Web.DE \
--to=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).