From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60730@debbugs.gnu.org, stefankangas@gmail.com, "J.P." <jp@neverwas.me>
Subject: bug#60730: 29.0.60; Free variable with :buffer keyword in ert-with-temp-file
Date: Sun, 29 Jan 2023 10:56:08 +0100 [thread overview]
Message-ID: <87o7qhoe9z.fsf@linux-m68k.org> (raw)
In-Reply-To: <83pmax97me.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Jan 2023 08:28:57 +0200")
On Jan 29 2023, Eli Zaretskii wrote:
>> From: "J.P." <jp@neverwas.me>
>> Cc: 60730@debbugs.gnu.org, stefankangas@gmail.com
>> Date: Sat, 28 Jan 2023 18:00:40 -0800
>>
>> When the value of `coding-system-for-write' is non-nil, only quoting it
>> twice survives expansion:
>>
>> (setq coding-system-for-write ''raw-text)
>> (ert-with-temp-file myfile)
>>
>> -> (let* ((coding-system-for-write 'raw-text) ...)
>>
>> Otherwise, we get a free variable:
>>
>> (setq coding-system-for-write 'raw-text)
>> (ert-with-temp-file myfile)
>>
>> -> (let* ((coding-system-for-write raw-text) ...)
>
> OK, in that case we should indeed solve this in the code by something
> like the patch you proposed.
I am surprised that the commit worked for you when you installed it. Do
you perhaps have defined a global variable undecided-unix in your Emacs
instance?
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-01-29 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 13:50 bug#60730: 29.0.60; Free variable with :buffer keyword in ert-with-temp-file J.P.
2023-01-13 1:56 ` Stefan Kangas
2023-01-28 14:13 ` J.P.
2023-01-28 15:03 ` Eli Zaretskii
2023-01-28 15:56 ` J.P.
2023-01-28 16:13 ` Eli Zaretskii
2023-01-29 2:00 ` J.P.
2023-01-29 4:35 ` J.P.
2023-01-29 6:38 ` Eli Zaretskii
2023-01-29 14:08 ` J.P.
2023-01-29 15:10 ` Eli Zaretskii
2023-01-29 16:18 ` J.P.
2023-01-29 6:28 ` Eli Zaretskii
2023-01-29 9:56 ` Andreas Schwab [this message]
2023-01-29 10:29 ` Eli Zaretskii
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=87o7qhoe9z.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=60730@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jp@neverwas.me \
--cc=stefankangas@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).