emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help hyperlinks only work when auto-compression-mode is enabled.


From: Alan Mackenzie
Subject: Re: Help hyperlinks only work when auto-compression-mode is enabled.
Date: Fri, 15 Jun 2007 23:35:31 +0100
User-agent: Mutt/1.5.9i

'Evening, Richard!

[ Quick recap of the problem:  Disable auto-compression-mode; do C-h f
  revert-buffer <CR>.  Put point over `file.el' and press <CR>.  The
  source file doesn't appear, because Emacs-22's "make install"
  compresses our source. ]

On Tue, Jun 12, 2007 at 12:00:11PM -0400, Richard Stallman wrote:
>     I don't think so.  Anybody who's knowingly disabled auto-compression-mode
>     will have a good reason for doing so, and will surely know what she's
>     doing.
> 
> Yes.
> 
>           She won't want the find-func functions to find foo.el.gz.
> 
> I am not convinced that follows.
> 
>     However, this user didn't ask for the Emacs-22 sources to be compressed,
>     any more than I did.  It just happened with the "make install".  So we're
>     entitled to see these sources on clicking the hyperlink in C-h f.
> 
> Yes, and the same argument applies to the functions in find-func.

Apologies:  When I wrote my two posts in this thread, I'd convinced
myself that my patch fixed the problem purely for the Emacs sources.
Which is complete and utter nonsense, of course.

The only way to uncompress _only_ the emacs sources is to create some
variable containing "/usr/local/share/emacs/22.1/lisp" and test it.
YUCK!!  I don't think that's the right thing to do.

We either decide that that <CR> will ALWAYS find compressed files in
that context, or we accept the hit with C-h f and disabled a-c-m.  I
don't think the latter is acceptable, since we don't output an error
message which is at all helpful.

I think the best thing is NOT to compress our source files with "make
install".  The compressed lisp directory contains 9.5 Mb of .el.gz
files.  Uncompressed, it's a bit around 38.5 Mb.  This saving of ~30 Mb
doesn't seem worth the hassle it causes.

What do people think?

-- 
Alan Mackenzie (Ittersbach, Germany)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]