Git Product home page Git Product logo

Comments (5)

mullen3 avatar mullen3 commented on July 19, 2024

This happens with any size file? I just installed and I'm having no such problems. I have a Macbook Pro, but with similar hardware.

from maximum-awesome.

jaytaylor avatar jaytaylor commented on July 19, 2024

Yes, it did it even for small files. I've been using the default version
of vim which comes with OS-X, and it is certainly an older version.

After I went through and removed things I'd had no use for (e.g. "pastie")
and a bunch of miscellaneous t-pope script packages (e.g. "ragtag", etc..),
the slowness went away.

Overall, I think maximum-awesome has way too much extra scrap that isn't
likely to be useful for most people. It required a non-trivial amount of
purging unnecessary modules before vim felt fast again.

Perhaps I'm just more of a minimalist.

On Tue, Sep 3, 2013 at 10:22 AM, Connor Mullen [email protected]:

This happens with any size file? I just installed and I'm having no such
problems. I have a Macbook Pro, but with similar hardware.


Reply to this email directly or view it on GitHubhttps://github.com//issues/68#issuecomment-23730564
.

from maximum-awesome.

mullen3 avatar mullen3 commented on July 19, 2024

Interesting... opinions on the extra plugins aside, the vanilla install should not be slow to insert. It was not for me. Could you have been hitting swap space?

from maximum-awesome.

jaytaylor avatar jaytaylor commented on July 19, 2024

That seems highly unlikely- this is a fresh OS install, and one of the very
first things I went to go setup.

On Tue, Sep 3, 2013 at 11:32 AM, Connor Mullen [email protected]:

Interesting... opinions on the extra plugins aside, the vanilla install
should not be slow to insert. It was not for me. Could you have been
hitting swap space?


Reply to this email directly or view it on GitHubhttps://github.com//issues/68#issuecomment-23735988
.

from maximum-awesome.

eventualbuddha avatar eventualbuddha commented on July 19, 2024

My guess is that the keyboard shortcut you are using is actually a prefix of another keyboard shortcut and vim is simply waiting to ensure the shorter one is the one you meant. This is similar to the issue we had with <leader>a taking forever because <leader>a<something else> was also defined. Check your mappings to see what else might be interfering.

from maximum-awesome.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.