From: nirva@ishiboo.com (Danny Dulai)
To: zsh-users@sunsite.auc.dk
Subject: Re: zsh and memory
Date: 15 Dec 1999 02:07:30 -0000 [thread overview]
Message-ID: <Liam.945223650.87053.32725.1378431534@fizz> (raw)
In-Reply-To: <991213182445.ZM11778@candle.brasslantern.com>
On 12/13/99, Bart Schaefer said:
>On Dec 13, 6:15am, Danny Dulai wrote:
>} Subject: zsh and memory
>}
>} Any hints on how to make zsh not consume as much memory as it does?
>} I'm not using the zftp or stat modules. Any thing else I can do?
>
>It'd be easier to answer the question if we knew what you ARE doing.
>"Is there any way I can get rid of these lumps on my head? I'm not
>hitting myself with a hammer."
I'm just running zsh, defining like 4 very very small functions, like 25
aliases, like 15 completions using compctl, various options set (but not
ALLEXPORT). I'm using vi keybindings, adding like 5 of my own, and not
using anything like zed or any other modules. Never do I use a
here-documents.
Even running zsh -f with no /etc/zshenv existent, will give me a shell
significantly larger than a bash.
>Various things you should avoid if memory is a problem include:
>
> setopt ALLEXPORT
> use large here-documents
> define lots of shell functions without using autoload
> use "zed" (old) or the mapfile module (new) to edit files
> use the new 3.1.6 shell-function-based completion system
>
>The last one is a bit unfortunate, but just "compinit" (without even
>trying any completions yet) adds half a megabyte to the RSS of zsh on
>my system, and it only goes up from there as functions autload and
>start caching their results in shell variables.
--
___________________________________________________________________________
Danny Dulai Feet. Pumice. Lotion.
http://www.ishiboo.com/~nirva/ nirva@ishiboo.com
prev parent reply other threads:[~1999-12-15 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-13 6:15 Danny Dulai
1999-12-13 18:24 ` Bart Schaefer
1999-12-15 2:07 ` Danny Dulai [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Liam.945223650.87053.32725.1378431534@fizz \
--to=nirva@ishiboo.com \
--cc=zsh-users@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).