Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Inconsequent EKEY values in GForth Date: Wed, 22 Feb 2017 13:46:24 -0800 Organization: A noiseless patient Spider Lines: 8 Message-ID: <87d1e9lwzz.fsf@nightsong.com> References: <59702fa8-dabb-4bb7-bff7-8915faae11a7@googlegroups.com> <87lgsylit9.fsf@nightsong.com> <584c08a6-2297-41f9-bf0f-ede8a9c5c71f@googlegroups.com> <87h93mlibd.fsf@nightsong.com> <8563c0fc-ad50-4b50-9909-7c57f9467797@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="81de832764bfaa8baec00932e485e613"; logging-data="30161"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18FJeKr1nphWp4jbWHCVqTs" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:nNo76p9UAEDOpCTzniyE2tYu+yI= sha1:qjgwVDVjHS0Jg74JUIKTuVF6Fe0= Xref: csiph.com comp.lang.forth:55060 minforth@arcor.de writes: > But in umbilical configurations a compact editor for target-resident > sources makes sense. This editor uses a 0.5MB ram buffer to hold the file being edited. Of course the buffer could be made smaller but it's still not a great approach for a ram limited target.