Permalink
Commits on Mar 16, 2013
  1. Try to fix issue #297.

    At least it doesn't crash anymore for me. It seems to be an off by one.
    Strangely enough, TranslationUnit.reparse and
    TranslationUnit.from_source are not affected, and when adding the "+ 1",
    they do not behave correctly. Maybe it's a bug in libclang?
    committed Mar 16, 2013
Commits on Mar 11, 2013
  1. Introduce a new snippets API.

    The snippets plugins are now fully written in python.
    
    Total completion time went from 0.220s to 0.160s.
    committed Mar 6, 2013
Commits on Mar 9, 2013
  1. Fix a nasty typo.

    committed Mar 9, 2013
Commits on Mar 6, 2013
  1. Update the doc.

    committed Mar 4, 2013
  2. Remove support for snipmate.

    committed Mar 4, 2013
Commits on Mar 4, 2013
  1. Remove unnecessary assignment

    Only print abbr, if no snippets are enabled.
    
    Conflicts:
    	plugin/clang_complete.vim
    tobig committed with Jan 20, 2013
  2. Merge branch 'kill-clang'

    committed Mar 4, 2013
  3. Last fix.

    committed Mar 4, 2013
  4. More cleanup.

    committed Mar 4, 2013
  5. Merge pull request #287 from pcc/resolve-paths

    Have getCompilationDBParams resolve paths relative to command's working directory
    committed Mar 4, 2013
Commits on Mar 3, 2013
Commits on Feb 20, 2013
  1. Ensure to not expose the last_query cache

    Ensure we do not give out a reference to the internal argument cache of
    the compilation database. Instead explicitly copy the internal cache.
    The problem with just giving out a reference is that later passes may
    modify the argument list. This does not only add unrelated content to
    the internal cache, but it also may lead to random crashes in case we
    use the argument list from different threads.
    tobig committed Feb 20, 2013
Commits on Feb 19, 2013
  1. More cleanup.

    committed Feb 19, 2013
  2. Bye clang binary.

    committed Feb 19, 2013
Commits on Feb 17, 2013
  1. Merge branch 'issue264'

    committed Feb 17, 2013
  2. Revert "If the path to libclang contains space, the plugin will spit …

    …errors."
    
    This reverts commit 76975ae.
    committed Feb 17, 2013
  3. Merge branch 'update-kinds'

    committed Feb 17, 2013
Commits on Feb 15, 2013
  1. Merge branch 'issue264'

    committed Feb 15, 2013
  2. Merge branch 'add_builtin_directories' of git://github.com/tobig/clan…

    …g_complete into builtin-dirs
    committed Feb 15, 2013
Commits on Feb 9, 2013
  1. Update plugin/clang_complete.vim

    simple fix for #264 after 3 hours of struggling..
    gokcehan committed Feb 9, 2013
Commits on Feb 5, 2013
  1. Remove misleading suggestion

    tobig committed Feb 5, 2013
  2. Add another system path

    tobig committed Feb 5, 2013
Commits on Feb 3, 2013
  1. Document the behaviour of getCompilationDBParams when a file is not f…

    …ound in the compilation database
    Arnaud-de-Grandmaison committed Feb 3, 2013
  2. Remember the last compilationDatabase query, and return it when the f…

    …ile is not found
    
    This is a very common case : it happens for all headers. In practice, this heuristics gives good results.
    Arnaud-de-Grandmaison committed Jan 18, 2013
Commits on Jan 31, 2013
  1. Fix initialisation of the compilation database.

    If g:clang_use_library wasn't set in the .vimrc, the use of compilation
    database would generate an error.
    committed Jan 31, 2013
Commits on Jan 30, 2013
  1. Fix indent.

    committed Jan 30, 2013
  2. Use the 'with' syntax with the libclangLock.

    This removes the .acquire() and .release(), and avoid potential lockups
    if the code wasn't guarded by try catch.
    committed Jan 30, 2013
Commits on Jan 29, 2013
  1. Replace call to vim.eval/command to vim python API.

    This is easier to read, and may be a bit faster.
    committed Jan 29, 2013