Date: Thu, 3 Jun 2010 17:54:52 -0600 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: Strying off topic, but Re: text editor Message-ID: <20100603235452.GB15773@guilt.hydra> In-Reply-To: <AANLkTinam4VvfIbf_2zdT87ez8HB3Lpz4hl9y95Cfmu8@mail.gmail.com> References: <AANLkTinam4VvfIbf_2zdT87ez8HB3Lpz4hl9y95Cfmu8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--WhfpMioaduB5tiZL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 03, 2010 at 10:14:19AM -0400, illoai@gmail.com wrote: >=20 > I don't know much, but the source tarball is slightly > over 7m. I suspect a lot of that is documentation. One thing Vim definitely has going for it is the breadth and depth of user documentation that comes with it. >=20 > In any case, the executable size is only loosely > related to the actual running size. True. On the other hand, to offer a comparison that actually came up in "real life", a co-worker once needed to edit a file. She tried using emacs to do so, but emacs couldn't open the file because it was so friggin' large that trying to open it with emacs exhausted system resources. She asked me how to achieve the same thing in Vim that she had intended to do with emacs because she discovered that it opened just fine in Vim. Obviously, this was very much an edge-case. The file was *huge*, measured in the gigabytes. It's not a problem you're likely to encounter in general usage. It does give me a little faith in the ability of Vim to avoid abusing system resources (and of vi in general). --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --WhfpMioaduB5tiZL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwIQMwACgkQ9mn/Pj01uKXAwQCg0GsoAax4acHGSYCiHrJZtdti rlUAoJ04DuRSnC5JtoQl5IrQTPvXVsA6 =rB3Z -----END PGP SIGNATURE----- --WhfpMioaduB5tiZL--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100603235452.GB15773>