Vin Shelton <acs(a)xemacs.org> writes in xemacs-beta(a)xemacs.org:
In 21.0 and earlier, all that's necessary to get tar-mode
automatically
enabled is:
(autoload 'tar-mode "tar-mode")
This is redundant. If you have tar-mode installed (it's in the
os-utils package) this autoload is already done for you.
If I start xemacs -vanilla and eval that statement, editing a
tarfile, eg.
"db-2.6.4.tar", comes up correctly in tar-mode.
Now in 21.2, that no longer works. If I edit
"db-2.6.4.tar" under
21.2, the buffer comes up in fundamental mode.
Problem reproduced in my environment. I haven't built 21.2.7 yet, but
21.2.6 behaves as you describe and 21.0 comes up in tar mode.
In fact, when I try to run M-x tar-mode, I get "[No
match]".
This has always been the case with the tar-mode.el in XEmacs.
...
See also: variables `tar-update-datestamp' and `tar-anal-blocksize'.
\\{tar-mode-map}"
;; this is not interactive because you shouldn't be turning this
;; mode on and off. You can corrupt things that way.
(make-local-variable 'tar-header-offset)