* Wording in safe local variables message
@ 2006-04-04 18:05 Ralf Angeli
2006-04-04 20:24 ` Stefan Monnier
0 siblings, 1 reply; 2+ messages in thread
From: Ralf Angeli @ 2006-04-04 18:05 UTC (permalink / raw)
It seems that many people are having a hard time understanding how to
mark file-local variables permanently as safe. Maybe improving the
respective instructions in the pop-up message could help. Currently
it says
! -- to apply the local variables list, and mark these values (*) as
safe (in the future, they can be set automatically.)
How about the following?
! -- to apply the local variables list, and permanently mark these
values (*) as safe (in the future, they will be set automatically.)
--
Ralf
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Wording in safe local variables message
2006-04-04 18:05 Wording in safe local variables message Ralf Angeli
@ 2006-04-04 20:24 ` Stefan Monnier
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2006-04-04 20:24 UTC (permalink / raw)
Cc: emacs-devel
> It seems that many people are having a hard time understanding how to
> mark file-local variables permanently as safe. Maybe improving the
> respective instructions in the pop-up message could help. Currently
> it says
> ! -- to apply the local variables list, and mark these values (*) as
> safe (in the future, they can be set automatically.)
> How about the following?
> ! -- to apply the local variables list, and permanently mark these
> values (*) as safe (in the future, they will be set automatically.)
That sounds indeed much better,
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-04-04 20:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-04 18:05 Wording in safe local variables message Ralf Angeli
2006-04-04 20:24 ` Stefan Monnier
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).