| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This change is related to pull request #83 however that pull request
wasn't merged here (and won't be merged at all) because it was based on
the old/dead `async-cleanup' feature branch (see pull request #49 on
GitHub) instead of the new `async-take-two' feature branch (see pull
request #84 on GitHub). This change set implements the equivalent on the
new feature branch (without introducing another option).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is related to pull request #82 however that pull request
wasn't merged here (and won't be merged at all) because it was based on
the old/dead `async-cleanup' feature branch (see pull request #49 on
GitHub) instead of the new `async-take-two' feature branch (see pull
request #84 on GitHub). This change set implements the equivalent on the
new feature branch.
In addition to Ingo's comments in pull request #82, the asynchronous
message frequently disturbs me while typing a Vim command, which is kind
of annoying. If everything goes well and we can get the async mode to be
stable enough to become the default mode then the status messages will
only be interesting when debugging a problem anyway.
|
|
|
|
|
| |
See also pull request #49 for my previous and failed attempt:
https://github.com/xolox/vim-easytags/pull/49
|
|\ |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> The back reference \g<0> substitutes in the entire substring
> matched by the RE.
> http://docs.python.org/2/library/re.html#re.sub
The documentation does not mention \0 as an alias to it.
Although \1 to \9 works.
I guess this alias (\0 <=> \g<0>) existed in old python version,
but it is not the case any more.
In python 2.7 and 3.3:
> import re; re.compile(r'123').sub(r'@\0@',"ab123cd")
'ab@\x00@cd' # KO
> import re; re.compile(r'123').sub(r'@\g<0>@',"ab123cd")
'ab@123@cd' # OK
|
|
|
|
|
| |
See issue #62 on GitHub:
https://github.com/xolox/vim-easytags/issues/62
|
|\
| |
| |
| |
| | |
See pull request #63 on GitHub:
https://github.com/xolox/vim-easytags/pull/63
|
|/
|
|
|
|
| |
unescaped ++ is invalid regex causing easytag to fall back to the
vimscript highlighting which does not split the regex into small chunks
that vim can handle.
|
| |
|
|\
| |
| |
| |
| | |
See pull request #59 on GitHub:
https://github.com/xolox/vim-easytags/pull/59
|
|/ |
|
|
|
|
|
| |
See also issue #58 on GitHub:
https://github.com/xolox/vim-easytags/issues/58
|
|
|
|
|
|
|
| |
is known
See the comment by @ixti in issue #57 on GitHub:
https://github.com/xolox/vim-easytags/issues/57#issuecomment-19720077
|
|
|
|
|
| |
See also issue #58 on GitHub:
https://github.com/xolox/vim-easytags/issues/58
|
| |
|
|
|
|
|
| |
See issue #57 on GitHub:
https://github.com/xolox/vim-easytags/issues/57
|
|
|
|
|
|
|
|
|
| |
$VIMRUNTIME/syntax/c.vim is a bit of a mess, I can't make heads or tails
of it :-). In my simple #if 0 / #if 1 / #else tests this fixes the issue,
but I'm not sure that there are no corner cases left.
See issue #57 on GitHub:
https://github.com/xolox/vim-easytags/issues/57
|
|
|
|
| |
from now on)
|
|\ |
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Issue #46 on GitHub:
https://github.com/xolox/vim-easytags/issues/46
|
|\| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
* Using a new tool I'm working on: A Python script that scans a Vim
script project for global function definitions and their documentation
comments (in Markdown format) and generates a single Markdown document
that provides an overview of the functions defined in the scripts.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Widegreen)
Original report:
https://github.com/xolox/vim-easytags/pull/48
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Issue #46 on GitHub:
https://github.com/xolox/vim-easytags/issues/46
|
| |
| |
| |
| |
| | |
Issue #47 on GitHub:
https://github.com/xolox/vim-easytags/issues/47
|
| |
| |
| |
| |
| | |
Issue #47 on GitHub:
https://github.com/xolox/vim-easytags/issues/47
|
|\| |
|
| |
| |
| |
| | |
Working towards fixing this issue: xolox/vim-lua-ftplugin#8
|
| |
| |
| |
| |
| |
| |
| | |
Issue #28 on GitHub:
problem with composed file types
https://github.com/xolox/vim-easytags/issues/28
|
| |
| |
| |
| |
| | |
This fixes the problem described here:
https://github.com/xolox/vim-easytags/issues/29
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- xolox#misc#path#absolute() was completely rewritten. It no
longer uses fnamemodify() which doesn't work on non-existing
pathnames. It's now written on top of xolox#misc#path#split()
and xolox#misc#path#join(). It should now properly normalize
directory separators as suggested in this pull request:
xolox/vim-session#29
- xolox#misc#path#split() and xolox#misc#path#join() were
enhanced with proper handling of UNC paths and respect
for the 'shellslash' option on Windows (tested on Windows
XP SP2, the only Windows I have available)
|
|\| |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
A side effect of xolox#easytags#write_tagsfile() is that the entries argument is joined together. This then causes problems in s:cache_tagged_files_in(), where the filename element is addressed via entry[1]. When the entries have been flattened, this accesses a single character, and then the cache is corrupted.
To fix this, move the cache update before the writing of the tags file. This avoids the need to make a copy of the entries before flattening them.
|