all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Daiki Ueno" <ueno@unixuser.org>
To: "Dan Nicolaescu" <dann@ics.uci.edu>
Cc: Michael Olson <mwolson@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: patch to include EasyPG to Emacs
Date: Tue, 12 Feb 2008 15:04:02 +0900	[thread overview]
Message-ID: <54a15d860802112204k614b1adh357a484eaecb5e69@mail.gmail.com> (raw)
In-Reply-To: <200802120348.m1C3mJ0B016980@sallyv1.ics.uci.edu>

2008/2/12, Dan Nicolaescu <dann@ics.uci.edu>:

> Can't these menus be added unconditionally?  This seems like good
> functionality to have (and it would simplify the code too).
> Why not ask RMS for permission?
>
> Also ask RMS about having .gpg automatically decrypted.  This is analog
> to what we do for compressed files... (This would simplify the code and
> also the documentation).

Thanks for the comments.  I'll ask him and the list, since I have been
still worried about the threshold between intrusive vs. non-intrusive
features...

>     Probably the first step of using EasyPG Assistant is to browse your
>     keyring.  @kbd{M-x epa-list-keys} is corresponding to @samp{gpg
>
> IMHO the first step would be to create the keyring.

The empty keyring is automatically created by epa-list-keys (gpg
--list-keys).  So I think the missing feature is an interactive
key-generation command in epa-key-list-mode.  (The API functions
epg-generate-key-from-* are already there but some work is needed to
implement the command).

Regards,
-- 
Daiki Ueno




  reply	other threads:[~2008-02-12  6:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07  4:58 patch to include EasyPG to Emacs Daiki Ueno
2008-02-07  5:13 ` Dan Nicolaescu
2008-02-07  9:28   ` Daiki Ueno
2008-02-07 16:24     ` Leo
2008-02-08  4:42       ` Daiki Ueno
2008-02-08  7:15     ` Dan Nicolaescu
2008-02-08  4:14 ` Richard Stallman
2008-02-08  7:03 ` Michael Olson
2008-02-10  7:04   ` Daiki Ueno
2008-02-10 15:44     ` Stefan Monnier
2008-02-10 19:15       ` Daiki Ueno
2008-02-10 19:30         ` Daiki Ueno
2008-02-10 20:58           ` Michael Olson
2008-02-10 21:29             ` Daiki Ueno
2008-02-11  0:03               ` Michael Olson
2008-02-10 19:46         ` Stefan Monnier
2008-02-10 22:36         ` Dan Nicolaescu
2008-02-10 23:34           ` Daiki Ueno
2008-02-11  6:30             ` Daiki Ueno
2008-02-12  1:24               ` Michael Olson
2008-02-12  3:48               ` Dan Nicolaescu
2008-02-12  6:04                 ` Daiki Ueno [this message]
2008-02-12 17:45                 ` Richard Stallman
2008-02-13 17:28                   ` Dan Nicolaescu
2008-02-14  4:43                     ` Richard Stallman
2008-02-14 11:26                       ` Daiki Ueno
2008-02-14 15:37                         ` Sascha Wilde
2008-02-14 18:43                           ` Daiki Ueno
2008-02-15 10:07                             ` Sascha Wilde
2008-02-15 17:05                               ` Daiki Ueno
2008-02-15 18:34                                 ` Sascha Wilde
2008-02-16  5:53                               ` Richard Stallman
2008-02-16 10:25                                 ` Jan Djärv
2008-02-16 11:16                                   ` Andreas Schwab
2008-02-16 23:00                                     ` Jeremy Maitin-Shepard
2008-02-17 20:29                                       ` Richard Stallman
2008-02-17 13:23                                   ` Richard Stallman
2008-02-18  6:58                                     ` Jan Djärv
2008-02-18  7:11                                       ` Miles Bader
2008-02-15  0:02                         ` Richard Stallman
2008-02-15  2:20                           ` Daiki Ueno
2008-02-18  8:55                         ` auto-encryption-mode, etc. (Re: " Daiki Ueno
2008-02-18 17:30                           ` Richard Stallman
2008-02-18 19:51                           ` Dan Nicolaescu

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=54a15d860802112204k614b1adh357a484eaecb5e69@mail.gmail.com \
    --to=ueno@unixuser.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=mwolson@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.