From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Crypto problems again
Date: Fri, 13 Feb 2004 11:17:45 +0100 [thread overview]
Message-ID: <87znbnth9y.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <4nbro8aru8.fsf@collins.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
> The problem is that I want the gnus-encrypt package to be supported by
> Gnus, meaning that the user should just load gnus-encrypt and have
> support for gnus-encrypt-file-alist and all the other nice things in
> that package. But I'm not allowed to use most normal facilities in
> order to do this. What can I do?
It seems that the two entry points are *-insert-file-contents and
*-write-file-contents. It looks as if you might be able to make it a
file handler. You could just forego completion and that stuff, or
forward these operations to the normal handlers.
I wonder if crypto regulations require the Emacs maintainers to remove
file-name-handler-alist from the code? That would break Ange-FTP and
Tramp and jka-compr...
Kai
prev parent reply other threads:[~2004-02-13 10:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:02 Lars Magne Ingebrigtsen
2004-02-02 18:54 ` Simon Josefsson
2004-02-02 23:07 ` Wes Hardaker
2004-02-03 9:12 ` Lars Magne Ingebrigtsen
2004-02-05 17:25 ` Lars Magne Ingebrigtsen
2004-02-05 17:45 ` Wes Hardaker
2004-02-05 20:09 ` Ted Zlatanov
2004-02-05 20:53 ` Simon Josefsson
2004-02-05 21:37 ` Wes Hardaker
2004-02-06 0:53 ` Jesper Harder
2004-02-05 21:29 ` Josh Huber
2004-02-05 21:38 ` Wes Hardaker
2004-02-05 22:36 ` Simon Josefsson
2004-02-05 23:09 ` Wes Hardaker
2004-02-02 19:49 ` crypto in netrc.el and gnus-encrypt.el (was: Crypto problems again) Ted Zlatanov
2004-02-02 23:05 ` Crypto problems again Wes Hardaker
2004-02-05 21:22 ` Jesper Harder
2004-02-05 21:39 ` Wes Hardaker
2004-02-05 22:18 ` Jesper Harder
2004-02-05 23:11 ` Wes Hardaker
2004-02-06 0:24 ` Jesper Harder
2004-02-06 1:47 ` Jesper Harder
2004-02-06 15:42 ` Wes Hardaker
2004-02-06 23:58 ` Jesper Harder
2004-02-09 21:03 ` Ted Zlatanov
2004-02-13 10:17 ` Kai Grossjohann [this message]
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=87znbnth9y.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.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.
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).