Hi Guys!
On 7 December 2011 19:01, arno <a...@renevier.net> wrote:
> […]
> I can reproduce the bug with mozilla tree.
I've got the same problem with the sources that are in my office and
are close to public — sorry.
The very fast cure I've designed is to produce temporary tags file and
the filter the lines not containing tab character.
I used awk '!/\t/{next};{print $0}' for example.
> I investigated more, and I discovered the bug comes probably from vim not
> being able to read long ctag lines (ctags 5.8 now parses javascript objects
> properties, which result in long lines being produced for mozilla tree)
Our sources does contain some JavaScript but the 'broken' lines seemed
to not look like long ones. They seemed to look like a random
fragments from the indexed tree.
Will report tomorrow the version of ctags in our office development
environment. vim was compiled by myself 7.3 and 7.4beta2.
I suppose that there may be a problem with locales.
In our environment it is
LANG=pl_PL.ISO-8859-2
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
and the indexed files are encoded in ISO-8859-2 and UTF8 partially.
Not mixed within one file.
KAcper
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
