From: Ralf Angeli <angeli@iwi.uni-sb.de>
Subject: Wording in safe local variables message
Date: Tue, 04 Apr 2006 20:05:21 +0200 [thread overview]
Message-ID: <e0ucf9$qmr$1@sea.gmane.org> (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
next reply other threads:[~2006-04-04 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 18:05 Ralf Angeli [this message]
2006-04-04 20:24 ` Wording in safe local variables message Stefan Monnier
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='e0ucf9$qmr$1@sea.gmane.org' \
--to=angeli@iwi.uni-sb.de \
/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).