From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Emacs Cloud
Date: Tue, 04 Feb 2014 14:25:17 +0100 [thread overview]
Message-ID: <87zjm7j9he.fsf@randomsample.de> (raw)
In-Reply-To: <87a9e7f39n.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 04 Feb 2014 07:53:08 -0500")
Ted Zlatanov writes:
> On Mon, 03 Feb 2014 15:58:24 +0100 David Engster <deng@randomsample.de> wrote:
>
> DE> Tassilo Horn writes:
>>> David Engster <deng@randomsample.de> writes:
>>>
>>>> Note that you can install GnuPG 1.x alongside GnuPG 2.x with no
>>>> problems, and every recent distribution I know has packages for both.
>>>
>>> As far as I can see, Arch has only the current 2.0.22 version in its
>>> official repository. There's a gnupg1 package with version 1.4.16 in
>>> the user repository, though, but its unlikely that people have that
>>> installed.
>
> DE> Oh well, Arch users run into problems all the time anyway. They are
> DE> usually also not afraid of doing some reading, so they'll have to learn
> DE> about the agent and set it up properly.
>
> It's not always an option. Please don't explain this away as a user
> problem that can be remedied by education and effort. Not everyone
> matches the "single user, single desktop" use case.
I don't agree, but let's leave it at that. I've used the agent for years
under various setups with no problems (and yes, that includes remote
headless servers and the like). Anyone interested can read bug #15553
and gmane.emacs.devel/163708 and make up his own mind.
-David
next prev parent reply other threads:[~2014-02-04 13:25 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 4:55 Lars Ingebrigtsen
2014-02-01 10:11 ` Ted Zlatanov
2014-02-01 12:10 ` Rasmus
2014-02-01 16:49 ` Steinar Bang
2014-02-01 20:23 ` Rasmus
2014-02-01 21:37 ` Ted Zlatanov
2014-02-01 21:50 ` Andreas Schwab
2014-02-02 5:03 ` Ted Zlatanov
2014-02-02 8:23 ` Andreas Schwab
2014-02-04 12:55 ` Ted Zlatanov
2014-02-02 22:17 ` Steinar Bang
2014-02-01 20:48 ` Lars Ingebrigtsen
2014-02-01 21:43 ` Ted Zlatanov
2014-02-01 21:44 ` Lars Ingebrigtsen
2014-02-01 22:32 ` Lars Ingebrigtsen
2014-02-02 5:04 ` Ted Zlatanov
2014-02-02 5:14 ` Lars Ingebrigtsen
2014-02-02 5:21 ` Lars Ingebrigtsen
2014-02-02 17:17 ` Ted Zlatanov
2014-02-02 22:53 ` Lars Ingebrigtsen
2014-02-02 23:20 ` Julien Danjou
2014-02-02 23:22 ` Lars Ingebrigtsen
2014-02-02 23:39 ` Julien Danjou
2014-02-02 23:46 ` Lars Ingebrigtsen
2014-02-03 8:08 ` David Engster
2014-02-03 13:14 ` Tassilo Horn
2014-02-03 14:58 ` David Engster
2014-02-04 12:53 ` Ted Zlatanov
2014-02-04 13:25 ` David Engster [this message]
2014-02-06 0:49 ` Emacs Cloud (coverage and killed groups) Lars Ingebrigtsen
2014-02-07 2:49 ` Lars Ingebrigtsen
2014-02-07 8:56 ` Julien Danjou
2014-02-07 10:40 ` Peter Münster
2014-02-08 2:35 ` Lars Ingebrigtsen
2014-02-07 13:24 ` Ted Zlatanov
2014-02-03 14:53 ` Emacs Cloud Ted Zlatanov
2014-02-03 15:04 ` David Engster
2014-02-03 14:45 ` Ted Zlatanov
2014-02-02 17:20 ` Ted Zlatanov
2014-02-02 22:50 ` Lars Ingebrigtsen
2014-02-02 5:08 ` Ted Zlatanov
2014-02-05 7:46 ` Steinar Bang
2014-02-05 23:05 ` Lars Ingebrigtsen
2014-02-05 23:06 ` Lars Ingebrigtsen
2014-02-07 13:28 ` Ted Zlatanov
2014-02-08 4:13 ` Lars Ingebrigtsen
2014-02-10 8:43 ` Daiki Ueno
2014-02-10 13:32 ` Ted Zlatanov
2014-02-11 12:14 ` Lars Ingebrigtsen
2014-02-11 13:25 ` Daiki Ueno
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=87zjm7j9he.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.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).