From: Henrik Enberg <henrik+news@enberg.org>
Subject: Re: [Gnus-FAQ] Draft 2
Date: Thu, 09 Jan 2003 20:16:55 +0100 [thread overview]
Message-ID: <87r8bmm8uw.fsf@enberg.org> (raw)
In-Reply-To: <4r8iurg9.fsf@hschmi22.userfqdn.rz-online.de>
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> Henrik Enberg <henrik+news@enberg.org> writes:
>
>> Might be a good idea to tell the user to set proper read permissions
>> (chmod 600 ~/.authinfo) for the file if he's on a multi-user machine.
>> The same might go for ~/.gnus if there's passwords in it.
>
> Can we tell Emacs to set the right permissions while writing the file?
> Something like M-x write-with-permissions RET 600 RET? If there's a
> function which does this, please yell.
Not that I know of. I think Emacs uses the umask setting on systems
that support it (*nixes).
next prev parent reply other threads:[~2003-01-09 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65szqjz6.fsf@hschmi22.userfqdn.rz-online.de>
2003-01-09 2:08 ` Frank Haun
[not found] ` <87fzs3nprw.fsf@enberg.org>
[not found] ` <4r8iurg9.fsf@hschmi22.userfqdn.rz-online.de>
2003-01-09 19:16 ` Henrik Enberg [this message]
2003-01-09 20:48 ` GHERdO
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r8bmm8uw.fsf@enberg.org \
--to=henrik+news@enberg.org \
/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.
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 NNTP newsgroup(s).