> Hi Chris!
>
> On Mi, 23 Dez 2009, Chris Jones wrote:
> > On Wed, Dec 23, 2009 at 12:55:03PM EST, Christian Brabandt wrote:
> > This sounds like something where you don't need to interact with the
> > process while it's running. Wouldn't it be a case where it's better
> > to use the usual batch tools such as sed, awk, or even something
> > like ed to achieve the desired result?
>
> Sure, I could probably have used Perl for that, (s)ed/awk have
> unfortunately not that powerful regular expressions.
Or more prosaically, egrep.. -:)
> Secondly I do not have any of these available on Windows and lastly I
> am faster doing the manipulation in vim, than I am writing Perl
> programs. Plus, in Vim it is really easy to try different ways out,
> undo, try again, etc. That really is easier for me that running batch
> jobs and check the resulting file afterwards.
> > Still wouldn't address the issue of the initial loading of something
> > as small as the average linux system's /etc taking about five
> > seconds. Five seconds is not a lot as compared to what you are
> > doing, but then my perception is that it's a trivial task that I
> > perform hundreds of times daily and it response should be
> > instantaneous.
> That sounds seriously wrong. Is this also happening, when you start vim
> using vim -u NONE -N <yourfile>?
I tried it with a fairly large tree called ~/tarballs and it took over a
minute, with Vim flying at 100% CPU. There was a message to the effect
that it was indexing/caching the nodes or something. Now the weird thing
is that in another test, my home directory, which contains the tarballs
tree only took 3-4 seconds - go figure.
Actually I did the same test again with another instance of Vim,
naturally, in order to take a closer look at the message, same tarballs
directory and this time it only took about two seconds.
So it looks as if there are glitches when it takes forever, and normal
circumstances where it takes somwhere between 3-5 seconds to load a
directory, why is too slow to my taste.
I'll try to run tests again when I have more time.
Thanks for your comments,
CJ
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment