>>>> "Ville" == Ville Skytt <Ville>
writes:
Ville> The binary package built with XEmacs 21.4.19 from what's
Ville> currently in unsupported/scop/vc in CVS is available at
Ville>
http://koti.welho.com/vskytta/xemacs/new-vc/vc-0.01-pkg.tar.gz
I have vc-0.03-pkg.tar.gz; I assume this is still causing problems for
you?
Ville> Minimal tarball containing one Subversion controlled file:
Ville>
http://koti.welho.com/vskytta/xemacs/new-vc/svndir.tar.gz
The file foo.txt is supposed to be empty, right?
Ville> Install the above vc package, modify ~/.xemacs/init.el and
Ville> add "(require 'vc-hooks)" there, unpack the svndir tarball
Ville> somewhere.
I have the new vc from CVS, built with 21.5 I think, installed under
/usr/local/lib/xemacs/xemacs-packages. Then I installed the package
from your site under /usr/local/lib/xemacs/site-packages.
For me, both packages have shown some abnormality, I get a "bad byte
code" error sometimes, but not in the last couple of tries.
Unfortunately the backtrace doesn't print the byte code so I haven't
been able to investigate directly yet. Does "bad byte code" sound
familiar?
I do not get a crash, with the locally built vc or with your tarball.
If you run xemacs 21.4 with
-vanilla \
-eval "(progn (require 'vc-hooks) (setq debug-on-error t))" \
/tmp/foo/foo.txt
can you get consistent crashes? (I'm looking for a precise recipe
from the command line, I don't know that does it for me yet..) What
is the exact path to foo.txt on your system (shouldn't matter, but
...)?
Ville> I have discovered that if I remove auto-autoloads.elc from
Ville> the above installed vc package (but leave auto-autoloads.el
Ville> in), XEmacs never crashes. No other ideas :(
I don't see anything obviously evil in auto-autoloads, but the files
have many superficial differences across the packages. ("Superficial"
means that the forms come in a different order but I believe they're
the same.)
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.