From: Yuri D'Elia <wavexx@thregr.org>
To: emacs-devel@gnu.org
Subject: Re: native-comp write path?
Date: Sat, 12 Feb 2022 15:14:22 +0100 [thread overview]
Message-ID: <87h794jhoh.fsf@wavexx.thregr.org> (raw)
In-Reply-To: 87fsoodx2i.fsf@wavexx.thregr.org
On Sat, Feb 12 2022, Yuri D'Elia wrote:
> Is there a way to customize the place where user's elc-cache is
> _written_ to?
Ha, I've just seen this has been added two days ago :)
Sorry for the noise.
next prev parent reply other threads:[~2022-02-12 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 13:38 native-comp write path? Yuri D'Elia
2022-02-12 14:14 ` Yuri D'Elia [this message]
2022-02-12 17:51 ` Eli Zaretskii
2022-02-12 17:59 ` Stefan Monnier
2022-02-12 19:12 ` Eli Zaretskii
2022-02-12 19:40 ` Stefan Monnier
2022-02-12 21:18 ` Yuri D'Elia
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=87h794jhoh.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=emacs-devel@gnu.org \
/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).