Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kevin Brubeck Unhammer <unhammer@fsfe.org>
To: info-gnus-english@gnu.org
Subject: Re: gnus-calendar / gnus-icalendar in Emacs24?
Date: Thu, 22 Jan 2015 12:16:55 +0100	[thread overview]
Message-ID: <87a91bhxp4.fsf@fsfe.org> (raw)
In-Reply-To: <1421911311.2976.20.camel@atmarama.net>


[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]

Gour <gour@atmarama.net> writes:

> On Sri, 2015-01-21 at 22:07 +0100, Rasmus wrote:
>
>> BBDB3 is nice.  You may be able to setup sync between BBDB and owncloud
>> using AsynK.
>
> It sounds good, but I wonder about this statement (from org group):"I found
> AsynK screwed up my contacts." ?

ASynK does make backups on each sync, though you should probably make
your own backups as well (1000 bbdb contacts takes 0.5M so there's no
reason not to keep lots of backups).

I've used ASynK for maybe a year or more to sync my owncloud with bbdb3.
I use http://dmfs.org/carddav/ on my phone. There was a problem at one
point when both owncloud upgraded to 7 and ASynK had some change to its
db format I think, where I had to do a full clean re-sync to make it
work again, but mostly it's just been doing its thing without trouble.

I don't use very advanced contact field stuff though, just names, emails
and phone numbers, though you can setup rewrite rules for field names
http://karra-asynk.appspot.com/doc/asynk/asynk_5.html#Customization


-- 
Kevin Brubeck Unhammer

GPG: 0x766AC60C

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]



  reply	other threads:[~2015-01-22 11:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 13:38 Loris Bennett
2014-12-15 15:25 ` Emanuel Berg
2014-12-15 15:54 ` Adam Sjøgren
2014-12-15 16:03 ` Charles Philip Chan
     [not found] ` <mailman.16138.1418659474.1147.info-gnus-english@gnu.org>
2014-12-15 23:35   ` Emanuel Berg
2014-12-16  1:24     ` Charles Philip Chan
     [not found]     ` <mailman.16155.1418693129.1147.info-gnus-english@gnu.org>
2014-12-16 22:41       ` Emanuel Berg
2014-12-16 22:49         ` David Engster
2014-12-16 22:52         ` Adam Sjøgren
     [not found]         ` <mailman.16239.1418770400.1147.info-gnus-english@gnu.org>
2014-12-16 23:15           ` Emanuel Berg
2014-12-17  7:36           ` Loris Bennett
2014-12-17 11:41             ` Rasmus
2015-01-21  7:53               ` Gour
2015-01-21 21:07                 ` Rasmus
2015-01-22  7:21                   ` Gour
2015-01-22 11:16                     ` Kevin Brubeck Unhammer [this message]
2015-01-22 22:17                       ` Rasmus
     [not found]             ` <mailman.16286.1418816719.1147.info-gnus-english@gnu.org>
2014-12-17 11:50               ` Loris Bennett
2014-12-17 13:47             ` Adam Sjøgren
     [not found] ` <mailman.16136.1418658867.1147.info-gnus-english@gnu.org>
2014-12-16 10:33   ` Gijs Hillenius
2014-12-16 10:39     ` Gijs Hillenius
2014-12-16 11:41       ` Adam Sjøgren
2014-12-17 13:26         ` Adam Sjøgren
     [not found]         ` <mailman.16288.1418822799.1147.info-gnus-english@gnu.org>
2015-01-13 10:07           ` Gijs Hillenius
2014-12-16 14:41     ` Gijs Hillenius
2014-12-18 16:50   ` Gijs Hillenius
2014-12-19  0:50     ` Emanuel Berg
2014-12-19  8:04       ` Gijs Hillenius

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=87a91bhxp4.fsf@fsfe.org \
    --to=unhammer@fsfe.org \
    --cc=info-gnus-english@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.
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).