[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: trusted-content in *scratch*
From: |
Stefan Kangas |
Subject: |
Re: trusted-content in *scratch* |
Date: |
Mon, 24 Feb 2025 16:55:12 +0000 |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ulrich Müller <ulm@gentoo.org>
>> Date: Mon, 24 Feb 2025 11:29:05 +0100
>>
>> In the *scratch* buffer, the trusted-content variable has an initial
>> value of nil. However, if I kill *scratch* and recreate it, it then has
>> a buffer-local value of :all.
>>
>> Feature or bug?
>
> Hard to say, because the use cases for recreating *scratch* are not
> really clear. I think we should wait and see if this causes real
> problems, otherwise why not leave it as it is?
FWIW, it seems like a bug to me. It's the same problem as before, just
exposed in a way that we failed to anticipate.
- trusted-content in *scratch*, Ulrich Müller, 2025/02/24
- Re: trusted-content in *scratch*, Eli Zaretskii, 2025/02/24
- Re: trusted-content in *scratch*,
Stefan Kangas <=
- Re: trusted-content in *scratch*, Eli Zaretskii, 2025/02/24
- Re: trusted-content in *scratch*, Ulrich Müller, 2025/02/28
- Re: trusted-content in *scratch*, Eli Zaretskii, 2025/02/28
- Re: trusted-content in *scratch*, david, 2025/02/28
- Re: trusted-content in *scratch*, Eli Zaretskii, 2025/02/28
- Re: trusted-content in *scratch*, david, 2025/02/28