Closed larryhynes closed 8 years ago
With 'stock' heirloom vi you maybe refering to the latest release 050325. But repo here is using the very latest commit from gunnar, which he did nearly two years later on 2/25/2007. Already in this commit (which contains only changes done by Gunnar) tags don't work.
I did use tags long ago, now I simply use grep -r
or git grep
. Not superior--just a personal preference to get the work done in time. So I didn't test tags for Gunnar's vi--sorry. (... I did test tags for the original vi ports--there it works.)
So I thank you very much for reporting the issue--I'll have a look and try to fix it ASAP.
GitHub closes an issue if the issue number appears in the commit message--sorry. Please test and reopen if it still fails.
Working so far - thank you! I'll let you know if there are any issues once I've used it for a while.
Hi Larry,
I don't intent to do development to Gunnars vi (except for good reason), this repo is just for fixing bugs. Since you've found a substantial bug it is worth to generate a new release (even if the code change is less than insignificant...). Have you found further issues? If not I prepare the release next weeks (or start of next year, there's no hurry).
That's great - thanks for your work. I haven't had any further issues with tags, and nothing else comes to mind at the moment. If I do find anything at any stage I'll report it here.
Hi
I've compiled this fine on my local (OSX) machine, but I can't get it to work with tags.
Running
:ta Mex
, for instance, invi
givesMex: Bad tags file entry
. Running:ta foo
, wherefoo
is any of the tags in thetags
file in the current dir returns the same error,foo: Bad tags file entry
.As a very minimal example, if I run
vi
with onlyset tags=tags
in.exrc
, and make a simpletags
file with just the following in itthen running
:ta exrc
returns the same error.I can use tag files and tags no problem with a 'stock' heirloom ex-vi (
Version 4.0 (gritter) 3/25/05
), but not with the one I build from this repo (Version 4.1.2 (gritter) 9/5/16
).What am I missing?