Skip to content


Subversion checkout URL

You can clone with
Download ZIP
branch: master
Commits on Nov 15, 2014
  1. @jszakmeister

    lustyjuggler: preserve the "<script>" tag when restoring a mapping

    jszakmeister authored
    This is a true fix for #20.  The `maparg()` function still does not
    report back enough information to know whether or not the "<script>" tag
    was specified for the mapping.  So, let's take another approach and
    parse the output of the map command.  The presence of an "&" appears to
    be a good indicator that you need the "<script>" tag.  Let's key off
    that and use that information when generating the command to restore the
Commits on May 23, 2014
  1. Tweak README

  2. Update contributors.

  3. Update README

  4. Only set colorcolumn in versions of Vim that have it

    Fixes a minor bug in some Vim installations.
  5. @rosslagerwall

    Use vim's autoload feature to reduce startup time

    rosslagerwall authored
    Without this, loading both lusty-explorer and lusty-juggler took 55ms
    on my machine (see vim --startuptime), most likely due to loading the
    Ruby interpreter.  With this, the combined loading time is less than
Commits on Apr 7, 2014
Commits on Apr 6, 2014
  1. Merge branch 'implement-unload-buffer' of…

    …usty into alovak-implement-unload-buffer
    Also, remove unload_selected_buffer stuff from explorer.rb since it's
    now in buffer-explorer.rb.
  2. @alovak
Commits on Apr 2, 2014
  1. @alovak
  2. @alovak

    unload buffer on c-d

    alovak authored
  3. @alovak

    add key mapping for c-d

    alovak authored
Commits on Dec 26, 2013
  1. Merge pull request #97 from ggustafsson/master

    setlocal colorcolumn=0
Commits on Dec 23, 2013
  1. @ggustafsson

    setlocal colorcolumn=0

    ggustafsson authored
  2. @ggustafsson

    setlocal colorcolumn=0

    ggustafsson authored
Commits on Sep 4, 2013
  1. Change titles of explorer windows to fix odd behavior in Vim 7.3

    From e.g. "[LustyExplorer-Files]" to "LustyExplorer--Files".  This is
    because internally we call something like `:split [LustyExplorer-Files]`
    in order to create the explorer window.  The argument to :split is the
    name of the file to edit (or, if it doesn't exist, a new buffer with
    that name).  However, :split does some wildcard expansion on its
    argument, and can interpret [LustyExplorer-Files] as a regex-ish range.
    In most versions of Vim, this :split call may emit a warning, but Vim
    will go ahead and create the new buffer named [LustyExplorer-Files] in a
    new window.  In some versions of Vim 7.3, however, it will emit the
    warning (stifled by `!silent` in lusty-explorer.vim) and not create the
    new buffer or the new window.
    I could probably work around this by escaping the square bracket
    characters, but I'm not sure how that will affect Windows, in which the
    escape character '\' is also a directory separator.  So, I'll do the
    easier thing and use more innocuous names for the explorer windows.
Commits on Mar 26, 2013
  1. @lmeijvogel

    Simplify determining cancel keys by subtracting alpha_buffer_keys fro…

    Lennaert Meijvogel authored lmeijvogel committed
    …m default cancel keys.
    I hope this change will make the keyboard mappings more robust since it
    can no longer miss unmapping keys.
  2. @lmeijvogel

    Add some more cancel keys.

    Lennaert Meijvogel authored lmeijvogel committed
    Any keys that would make vim enter insert/replace mode will break
    LustyJuggler. These are now mapped as 'cancel keys'.
Commits on Feb 4, 2013
  1. Merge pull request #87 from emergion/master

    Lusty Juggler crashing on OS X Vim 73
  2. @pmyjavec
  3. Merge pull request #86 from emergion/master

    Lusty Juggler crashing on OS X Vim 73
  4. @pmyjavec

    this was breaking on os x

    pmyjavec authored
Commits on Sep 2, 2012
Commits on Jul 8, 2012
  1. Remove explicit email address

Commits on Jun 29, 2012
  1. Merge branch 'pygatea-master'

Commits on Jun 25, 2012
  1. fix indentation

  2. use script-local variable

  3. @dlobraico
Something went wrong with that request. Please try again.