From: (Chris Beggy ) news@kippona.com
Subject: Re: any tips for how to tune Gnus/emacs for low memory usage?
Date: Thu, 29 Nov 2001 09:30:20 -0500 [thread overview]
Message-ID: <87r8qhfy4j.fsf@lackawana.kippona.com> (raw)
In-Reply-To: <vafbshmt1rh.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> On the Ion list, some patches have been circulating which allow you
I compiled, installed, evaluated and took a look at the
output of ls -l and size for some of the small window managers:
size name comment
--------------------------------------------------------------------
17232 aewm* simple, few knobs, plug-ins for menus
1293351 blackbox* not really small, coffemaker
187976 fvwm2* supports mouseless
119812 fvwm95* supports mouseless
18968 heliwm* couldn't get it to launch an xterm, my bad
66496 larswm* tiling, good mouseless, documentation
23668 lwm* simple
57819 ratpoison* max screen use, emacs-like, good mouseless
127332 twm* classic
29436 w9wm* virtual screens, not mouseless
165757 wm2* excellent aesthetics, not mouseless
672256 wmx* wm2 aesthetics, virtuals, good mouseless
text data bss dec hex filename
------------------------------------------------
14241 572 132 14945 3a61 aewm
160897 26996 336 188229 2df45 blackbox
178635 4456 12096 195187 2fa73 fvwm2
112149 3024 2916 118089 1cd49 fvwm95
16187 584 436 17207 4337 heliwm
62936 736 11844 75516 126fc larswm
20160 832 152 21144 5298 lwm
33919 1216 448 35583 8aff ratpoison
118911 5080 82484 206475 3268b twm
24615 2304 348 27267 6a83 w9wm
61977 13068 432 75477 126d5 wm2
92111 14720 188 107019 1a20b wmx
I don't understand why wm2 is so large, given that its feature
set is similar to aewm or lwm.
I'm interested in making best use of a small laptop screen,
mouseless navigation, freeing up resources for emacs :-)
Chris
next prev parent reply other threads:[~2001-11-29 14:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 19:55 Steinar Bang
2001-11-26 4:21 ` Stainless Steel Rat
2001-11-26 21:57 ` Steinar Bang
2001-11-26 22:45 ` Karl Kleinpaste
2001-11-27 3:29 ` Stainless Steel Rat
2001-11-27 12:38 ` Daniel Pittman
2001-11-27 14:11 ` news
2001-11-27 14:27 ` luis fernandes
2001-11-27 16:24 ` news
2001-11-27 16:56 ` Kai Großjohann
2001-11-27 20:28 ` news
2001-11-27 19:13 ` Stainless Steel Rat
2001-11-27 19:30 ` luis fernandes
2001-11-27 19:37 ` Robin S. Socha
2001-11-27 20:06 ` luis fernandes
2001-11-27 21:50 ` news
2001-11-28 23:02 ` Steinar Bang
2001-11-29 8:33 ` Kai Großjohann
2001-11-29 14:30 ` news [this message]
2001-12-01 9:59 ` Steinar Bang
2001-11-27 19:40 ` Paul Jarc
2001-11-30 23:19 ` Kevin Ryde
2001-11-30 13:51 ` news
2001-11-30 16:58 ` Stainless Steel Rat
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r8qhfy4j.fsf@lackawana.kippona.com \
--to=news@kippona.com \
--cc=chrisb@lackawana.kippona.com \
/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 NNTP newsgroup(s).