From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: cpitclaudel@gmail.com, arthur.miller@live.com, emacs-devel@gnu.org
Subject: Re: Easy configuration of a site-lisp directory
Date: Tue, 10 Aug 2021 17:01:31 +0300 [thread overview]
Message-ID: <83o8a5flfo.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8XfmVgDSgTYNqmx9DpLzKw8uGj8TTdNp_O8cjESMryQtQ@mail.gmail.com> (message from Yuri Khan on Tue, 10 Aug 2021 20:43:30 +0700)
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Tue, 10 Aug 2021 20:43:30 +0700
> Cc: Arthur Miller <arthur.miller@live.com>, Clément Pit-Claudel <cpitclaudel@gmail.com>,
> Emacs developers <emacs-devel@gnu.org>
>
> On Tue, 10 Aug 2021 at 19:08, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > What is your problem with compressed *.el files? When Emacs visits
> > such a file, it uncompresses it, so you see the original source. And
> > yet people keep mentioning the .gz extension as if it were a huge
> > problem. What am I missing?
>
> I have an unconfirmed guess that some people want not only to see the
> code but also hack it. In this use case, it is desirable for M-. to
> take them to the actual hackable code so that any changes persist
> across Emacs restarts and are seen by version control.
But the .el.gz files that Emacs displays _are_ "hackable", in the
sense that you can modify it and then save the results. Right?
next prev parent reply other threads:[~2021-08-10 14:01 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 15:40 Easy configuration of a site-lisp directory Philip Kaludercic
2021-08-08 18:18 ` Stefan Monnier
2021-08-08 18:53 ` Philip Kaludercic
2021-08-08 20:03 ` Stefan Monnier
2021-08-08 22:43 ` dick
2021-08-08 23:16 ` Stefan Monnier
2021-08-09 0:43 ` dick
2021-08-09 3:13 ` Clément Pit-Claudel
2021-08-09 16:59 ` Eli Zaretskii
2021-08-09 18:33 ` Clément Pit-Claudel
2021-08-09 18:49 ` dick
2021-08-09 22:11 ` Clément Pit-Claudel
2021-08-10 8:24 ` Arthur Miller
2021-08-10 8:31 ` Arthur Miller
2021-08-09 18:52 ` Eli Zaretskii
2021-08-09 22:14 ` Clément Pit-Claudel
2021-08-10 11:55 ` Eli Zaretskii
2021-08-10 8:10 ` Arthur Miller
2021-08-10 12:06 ` Eli Zaretskii
2021-08-10 13:43 ` Yuri Khan
2021-08-10 14:01 ` Eli Zaretskii [this message]
2021-08-10 15:10 ` Yuri Khan
2021-08-10 15:39 ` dick
2021-08-10 15:49 ` Stefan Monnier
2021-08-10 17:31 ` Arthur Miller
2021-08-10 15:44 ` Eli Zaretskii
2021-08-10 17:25 ` Clément Pit-Claudel
2021-08-10 17:50 ` Eli Zaretskii
2021-08-10 18:06 ` Clément Pit-Claudel
2021-08-10 18:23 ` Eli Zaretskii
2021-08-10 20:51 ` Stefan Monnier
2021-08-11 2:23 ` Eli Zaretskii
2021-08-11 5:31 ` Stefan Monnier
2021-08-11 13:42 ` Basil L. Contovounesios
2021-08-11 16:34 ` Eli Zaretskii
2021-08-11 18:21 ` Basil L. Contovounesios
2021-08-12 5:48 ` Eli Zaretskii
2021-08-10 17:35 ` Clément Pit-Claudel
2021-08-10 17:24 ` Arthur Miller
2021-08-10 17:22 ` Arthur Miller
2021-08-10 17:45 ` Eli Zaretskii
2021-08-09 6:52 ` Arthur Miller
2021-08-09 11:50 ` dick
2021-08-09 15:27 ` Arthur Miller
2021-08-19 9:25 ` Philip Kaludercic
2021-08-19 20:24 ` Arthur Miller
2021-08-19 21:43 ` Arthur Miller
2021-08-19 21:47 ` Arthur Miller
2021-08-19 21:59 ` Philip Kaludercic
2021-08-20 0:21 ` Arthur Miller
2021-08-20 21:36 ` Arthur Miller
2021-08-21 1:56 ` Stefan Monnier
2021-08-21 2:46 ` Arthur Miller
2021-08-21 3:12 ` Arthur Miller
2021-08-21 6:39 ` Eli Zaretskii
2021-08-21 6:48 ` tomas
2021-08-21 7:00 ` Eli Zaretskii
2021-08-21 7:19 ` symlinks and W32 [was: Easy configuration of a site-lisp directory] tomas
2021-08-21 14:15 ` Arthur Miller
2021-08-21 14:20 ` Eli Zaretskii
2021-08-21 19:12 ` Arthur Miller
2021-08-21 14:34 ` Easy configuration of a site-lisp directory Arthur Miller
2021-08-21 14:42 ` Eli Zaretskii
2021-08-21 19:10 ` Arthur Miller
2021-08-21 19:18 ` Eli Zaretskii
2021-08-21 20:25 ` Arthur Miller
2021-08-22 6:03 ` Eli Zaretskii
2021-08-25 10:47 ` Philip Kaludercic
2021-08-25 22:13 ` Arthur Miller
2021-08-26 9:42 ` Philip Kaludercic
2021-08-26 15:58 ` Arthur Miller
2021-08-20 10:23 ` Augusto Stoffel
2021-08-20 12:47 ` Arthur Miller
2021-08-23 9:14 ` Max Brieiev
2021-08-24 21:35 ` Stefan Monnier
2021-08-25 11:13 ` Philip Kaludercic
2021-08-25 14:37 ` Stefan Monnier
2021-08-25 14:55 ` Philip Kaludercic
2021-08-25 17:27 ` Stefan Monnier
2021-08-26 0:16 ` Arthur Miller
2021-08-26 4:10 ` Stefan Monnier
2021-08-26 15:38 ` Arthur Miller
2021-08-26 18:03 ` Stefan Monnier
2021-08-26 21:40 ` Arthur Miller
2021-08-25 22:29 ` Arthur Miller
-- strict thread matches above, loose matches on Subject: below --
2021-08-12 2:44 No Wayman
2021-08-12 12:41 ` dick
2021-08-12 14:48 ` No Wayman
2021-08-12 16:24 ` dick
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=83o8a5flfo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arthur.miller@live.com \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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).