From: Ted Zlatanov <tzz@lifelogs.com>
To: bug-gnu-emacs@gnu.org
Subject: Re: bug#7487: 24.0.50; Gnus nnimap broken
Date: Mon, 06 Dec 2010 10:11:07 -0600 [thread overview]
Message-ID: <87aakihof8.fsf@lifelogs.com> (raw)
In-Reply-To: m3ipziupey.fsf@quimbies.gnus.org
On Sun, 28 Nov 2010 03:56:21 +0100 Lars Magne Ingebrigtsen <lmi@gnus.org> wrote:
LMI> Jason Rumney <jasonr@gnu.org> writes:
>> Upon logging in, I am prompted to add my login credentials to
>> ~/.authinfo.gpg. This brings up a confusing buffer asking me to mark
>> a public key, which I have discovered by trial and error only works if
>> I select no public keys so it falls back on symetric encryption.
LMI> Yes, that interface is so confusing it's ridiculous.
I also had trouble with it the first time. Perhaps there should be more
information on that screen.
LMI> Ted is rewriting the way Emacs asks for and stores user credentials.
LMI> It'll support using the Secrets API in addition to the standard Emacs
LMI> .gpg file handling, but the .gpg interface is so wildly user hostile
LMI> that I'm tempted to go back to just storing this data in the plain-text
LMI> ~/.authinfo file until all this has been worked out.
Yeah, OTOH once it's set up, the .gpg file Just Works. So for me the
pain has faded away.
On Sun, 05 Dec 2010 17:49:52 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> This report was handled in a different forum, and debbugs wasn't Cc'd,
LMI> apparently. So I'm just closing this report.
Hey, where do I go to track it?
Thanks
Ted
next prev parent reply other threads:[~2010-12-06 16:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1290791691.11667.bug-gnu-emacs@gnu.org>
2010-11-28 2:56 ` bug#7487: 24.0.50; Gnus nnimap broken Lars Magne Ingebrigtsen
[not found] ` <m3ipziupey.fsf@quimbies.gnus.org>
2010-12-06 16:11 ` Ted Zlatanov [this message]
2010-12-07 23:32 ` Lars Magne Ingebrigtsen
2010-12-08 17:00 ` Jason Rumney
2010-12-09 21:15 ` Lars Magne Ingebrigtsen
2010-12-10 2:55 ` Stefan Monnier
[not found] ` <ids61l$jr6$2@quimby.gnus.org>
2010-12-10 16:18 ` Lars Magne Ingebrigtsen
2010-12-08 17:05 ` Jason Rumney
2010-12-08 23:32 ` Stefan Monnier
2010-12-09 21:10 ` Lars Magne Ingebrigtsen
[not found] ` <mailman.1.1291931529.5417.bug-gnu-emacs@gnu.org>
2010-12-10 18:48 ` Ted Zlatanov
2010-12-10 20:56 ` Stefan Monnier
[not found] ` <mailman.38.1292016144.4804.bug-gnu-emacs@gnu.org>
2010-12-13 3:19 ` Lars Magne Ingebrigtsen
2010-12-13 17:08 ` Ted Zlatanov
2010-12-13 20:11 ` Lars Magne Ingebrigtsen
2010-12-14 1:08 ` Daiki Ueno
2010-12-15 2:06 ` Daiki Ueno
[not found] ` <mailman.3.1292379760.6505.bug-gnu-emacs@gnu.org>
2010-12-15 14:39 ` Ted Zlatanov
2010-12-15 22:05 ` Daiki Ueno
2010-12-15 23:42 ` Daiki Ueno
2010-12-16 2:45 ` Daiki Ueno
[not found] ` <mailman.13.1292467961.28766.bug-gnu-emacs@gnu.org>
2010-12-16 16:00 ` Ted Zlatanov
2010-12-16 19:15 ` Ted Zlatanov
2010-12-16 19:39 ` Lars Magne Ingebrigtsen
2010-12-16 19:44 ` Lars Magne Ingebrigtsen
2010-11-26 17:10 Jason Rumney
2010-12-05 16:49 ` Lars Magne Ingebrigtsen
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=87aakihof8.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=bug-gnu-emacs@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.