(etags) Is this expected behavior?

(etags) Is this expected behavior?

[Luca Saiu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello.
After compiling and installing the pretest, included Emacs Lisp source
files, of which some are installed *gzipped* by the `install' Makefile
target, I just regenerated the TAGS file with

etags `find -name \*.el` `find -name \*.el.gz`

from the appropriate directory.

When looking for a symbol with M-. Emacs fails to find the source file
because it tries to open a non-existing *uncompressed* version.
Try with goto-line, for example.

Now, I hadn't noticed whether this also happened previously, but this is
definitely not the behavior one would expect. Should I report it as a bug?
I wrote here first to avoid bothering the emacs-devel people with noise,
just in case.

Thanks,

- --
Luca Saiu
Author of GNU epsilon: http://www.gnu.org/software/epsilon
http://www-lipn.lipn.univ-paris13.fr/~saiu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGMGLIvzOavibF0oYRAoSsAJ42X6MbjCAQtf93A+y+9HrHTkxprgCfbXb+
7Rhu3M4aKmG/DUFeUm1VF94=
=+aUC
-----END PGP SIGNATURE-----

Re: (etags) Is this expected behavior?

[Lennart Borgman (gmail)]

Luca Saiu wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello.
> After compiling and installing the pretest, included Emacs Lisp source
> files, of which some are installed *gzipped* by the `install' Makefile
> target, I just regenerated the TAGS file with
> 
> etags `find -name \*.el` `find -name \*.el.gz`
> 
> from the appropriate directory.
> 
> When looking for a symbol with M-. Emacs fails to find the source file
> because it tries to open a non-existing *uncompressed* version.
> Try with goto-line, for example.
> 
> Now, I hadn't noticed whether this also happened previously, but this is
> definitely not the behavior one would expect. Should I report it as a bug?
> I wrote here first to avoid bothering the emacs-devel people with noise,
> just in case.


Are you using Emacs 22 beta? If not and you want to report this, then 
please try the beta and follow the instructions there for sending bug 
reports.

Re: (etags) Is this expected behavior?

[Luca Saiu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Luca Saiu wrote:
> I wrote here first to avoid bothering the emacs-devel people with noise,
> just in case.

I may have been rude here.

I was just meaning that they look (understandably) very busy with the
release issues, while here the atmosphere seems more relaxed.

No offense to anyone --or any judgment about relative "importance"-- was
intended. If this was not clear please accept my excuses.

- --
Luca Saiu
Author of GNU epsilon: http://www.gnu.org/software/epsilon
http://www-lipn.lipn.univ-paris13.fr/~saiu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGMGqpvzOavibF0oYRAhGtAJ9hyvJgkEE6MCWLz/052smmcrxOyACfbTWi
FTJo/aI9dUxjSbtks0h+Jrk=
=PQ1h
-----END PGP SIGNATURE-----

Re: (etags) Is this expected behavior?

[Luca Saiu]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lennart Borgman (gmail) wrote:
> Are you using Emacs 22 beta? If not and you want to report this, then
> please try the beta and follow the instructions there for sending bug
> reports.

Ok. Thanks,

- --
Luca Saiu
Author of GNU epsilon: http://www.gnu.org/software/epsilon
http://www-lipn.lipn.univ-paris13.fr/~saiu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGMHEKvzOavibF0oYRApEDAJ4jWqfiHRc27tSLnbrxkvVbm0mxawCeKk9a
a5HUXRYaQr4gcQYEOSGRzBo=
=r7e+
-----END PGP SIGNATURE-----