From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: MON KEY <monkey@sandpframing.com>, 2807@debbugs.gnu.org
Subject: bug#2807: Subject: 23.0.90; etags can't access .el.gz files
Date: Fri, 07 Oct 2011 00:05:58 +0200 [thread overview]
Message-ID: <m3lisxhj21.fsf@stories.gnus.org> (raw)
In-Reply-To: <jwvvcsw5n8z.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 13 Sep 2011 14:09:49 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> I think that the solution should be that etags.el cares about looking
>> for possible compressed versions of file names contained in TAGS file.
>
> Please share the code with info.el which does that for its files.
Are you thinking of this bit?
(defvar Info-suffix-list
;; The MS-DOS list should work both when long file names are
;; supported (Windows 9X), and when only 8+3 file names are available.
(if (eq system-type 'ms-dos)
'( (".gz" . "gunzip")
(".z" . "gunzip")
[...]
'( (".info.Z" . "uncompress")
(".info.Y" . "unyabba")
(".info.gz" . "gunzip")
(".info.z" . "gunzip")
(".info.bz2" . ("bzip2" "-dc"))
(".info.xz" . "unxz")
(".info" . nil)
("-info.Z" . "uncompress")
("-info.Y" . "unyabba")
etc etc etc. Is this even necessary in Info? Doesn't jka-compr know
all about this already?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-10-06 22:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 3:39 bug#2807: Subject: 23.0.90; etags can't access .el.gz files MON KEY
2011-09-11 22:14 ` Lars Magne Ingebrigtsen
2011-09-13 11:51 ` Francesco Potortì
2011-09-13 18:09 ` Stefan Monnier
2011-10-06 22:05 ` Lars Magne Ingebrigtsen [this message]
2011-10-07 1:52 ` Stefan Monnier
2011-10-07 10:25 ` Lars Magne Ingebrigtsen
2011-10-07 13:29 ` Stefan Monnier
2011-10-07 14:38 ` Lars Magne Ingebrigtsen
2011-09-13 18:24 ` Lars Magne Ingebrigtsen
2023-10-12 12:39 ` Mauro Aranda
2023-10-12 12:44 ` bug#44494: " Dmitry Gutov
2023-10-12 12:51 ` Mauro Aranda
2023-10-12 15:47 ` Dmitry Gutov
2023-10-12 12:46 ` bug#44494: " Mauro Aranda
2023-10-12 14:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-12 15:04 ` Mauro Aranda
2023-10-15 4:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lisxhj21.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=2807@debbugs.gnu.org \
--cc=monkey@sandpframing.com \
--cc=monnier@IRO.UMontreal.CA \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).