* Detlef Steuer [2020-11-26 14:46]:
> Am Thu, 26 Nov 2020 08:31:29 +0300
> schrieb Jean Louis :
>
> > That is not fair choice. It pushes user to finally ! apply and accept
> > it, but does not give chance to permanently ignore it.
> >
> >
> > Do you want to apply it? You can type
> > y -- to
Am Thu, 26 Nov 2020 08:31:29 +0300
schrieb Jean Louis :
> That is not fair choice. It pushes user to finally ! apply and accept
> it, but does not give chance to permanently ignore it.
>
>
> Do you want to apply it? You can type
> y -- to apply the local variables list.
> n -- to ignore the
* Tom Gillespie [2020-11-26 09:19]:
> > As there is the option ! to "apply local variables and permanently
> > mark these values" but there is no option "not to apply local
> > variables and permanently mark these values".
>
> I have a longer reply that I will send tomorrow, but wanted to
* Greg Minshall [2020-11-26 08:34]:
> Tom,
>
> > 2. If mutt is launching Emacs, you can pass --eval "(setq
> >enable-local-eval nil)" on the command line and all file local
> >variables will be ignored and treated as plain text.
>
> maybe that is one thing that could really help here.
Located Eric's message and can confirm the same for mu4e (no query about
setting/evaluating anything upon opening the message).
cm
Eric S Fraga writes:
> On Wednesday, 25 Nov 2020 at 15:38, Jean Louis wrote:
>> I have not configured anything. In fact I have opened the email and I
>> was
> As there is the option ! to "apply local variables and permanently
> mark these values" but there is no option "not to apply local
> variables and permanently mark these values".
I have a longer reply that I will send tomorrow, but wanted to respond
to this.
Yes exactly! I have the equivalent
Additionally, as a good example of faulty design, user is coerced to
ACCEPT local variables rather than is given fair choice.
As there is the option ! to "apply local variables and permanently
mark these values" but there is no option "not to apply local
variables and permanently mark these
Tom,
> 2. If mutt is launching Emacs, you can pass --eval "(setq
>enable-local-eval nil)" on the command line and all file local
>variables will be ignored and treated as plain text.
maybe that is one thing that could really help here. possibly mutt and
other emacs-based mail readers,
* Tom Gillespie [2020-11-26 05:07]:
> Hi Jean,
>
> Some points in summary before a long email.
> 1. Having an accepting default behavior as a user (i.e., saying yes to
>all prompts) is bad security practice. The only thing that systems
>can do is prompt as infrequently as possible in
Hi Jean,
Some points in summary before a long email.
1. Having an accepting default behavior as a user (i.e., saying yes to
all prompts) is bad security practice. The only thing that systems
can do is prompt as infrequently as possible in hopes that people
don't get prompt fatigue. Emacs
* Tim Cross [2020-11-25 23:54]:
> I guess this is probably the main point where we disagree.
>
> Emacs is first and foremost a programmers editor. It was never designed
> as a general purpose editor, but rather specifically as an editor for
> programmers.
Yes. And when I was born as baby I was
Jean Louis writes:
> * Eric S Fraga [2020-11-25 16:58]:
>> On Wednesday, 25 Nov 2020 at 16:13, Jean Louis wrote:
>> > I use Mutt.
>> > The message is opened in Emacs in mail-mode
>>
>> Ah, so mutt saves content in a file which is then opened by
>> Emacs. Okay, that makes sense. Gnus does
* Eric S Fraga [2020-11-25 16:58]:
> On Wednesday, 25 Nov 2020 at 16:13, Jean Louis wrote:
> > I use Mutt.
> > The message is opened in Emacs in mail-mode
>
> Ah, so mutt saves content in a file which is then opened by
> Emacs. Okay, that makes sense. Gnus does things the other way around:
>
On Wednesday, 25 Nov 2020 at 16:13, Jean Louis wrote:
> I use Mutt.
> The message is opened in Emacs in mail-mode
Ah, so mutt saves content in a file which is then opened by
Emacs. Okay, that makes sense. Gnus does things the other way around:
opens the buffer (associated with a file in the
* Eric S Fraga [2020-11-25 16:06]:
> On Wednesday, 25 Nov 2020 at 15:38, Jean Louis wrote:
> > I have not configured anything. In fact I have opened the email and I
> > was surprised that I am getting those dialogues to execute local
> > variables.
>
> Very strange. It was my email that
On Wednesday, 25 Nov 2020 at 15:38, Jean Louis wrote:
> I have not configured anything. In fact I have opened the email and I
> was surprised that I am getting those dialogues to execute local
> variables.
Very strange. It was my email that instigated this part of the
thread. I can view my
* Tim Cross [2020-11-25 09:41]:
> >> Why is it a security issue? The variables do need to be close to the end
> >> — 3000 characters is only about 50 lines.
> >
> > Emacs users, Org users on our mailing lists are not so private. Their
> > names and email addresses are in the public database.
17 matches
Mail list logo
