Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: gnus-sync-save fails with "wrong-type-argument number-or-marker-p"
Date: Sat, 10 Dec 2011 15:19:44 +0100	[thread overview]
Message-ID: <87iplofr0f.fsf@dod.no> (raw)
In-Reply-To: <8762hon0re.fsf@lifelogs.com>

>>>>> Ted Zlatanov <tzz@lifelogs.com>:

> The stack trace you sent me was not complete (because of the default
> Emacs behavior, which in this case doesn't help), I need to know your
> data and the full invocation.  Do

> (setq print-level nil
>       print-length nil)

> and then redo that error and send me the full backtrace (it will have
> all your sync data, I think). 

Ok, I will try this and send you the trace in email.  Actually, I
already have.  It still looks like it doesn't print everything.  Lot's
of "..." in the lisp structures printed.

> It seems like gnus-sync.el has allowed some CouchDB parameters to
> creep into the newsrc, which is causing your problem.  A quick fix,
> after you've prepped the backtrace, is to exit Gnus, back up and then
> edit your newsrc.eld to remove the paired cons list that matches the
> error string above.  It will probably look like (deleted_conflicts
> "8-54ce40d61d4b92eda3bffb29c6e0b1c6")

Ok, I will try that.

> I'll try to get this resolved with you quickly but until Tuesday next
> week I'll be travelling; I apologize in advance for the slow
> responses.

Well... er... since I'm using software that others share out of their
good will, I don't expect any support out over what they are prepared to
give at any given time.  So, no apologies needed.  Honest! :-)

My postings comes from that I need to think out loud when I work my way
through issues, and for gnus-sync, the gnus list seems like the right
forum to do so in. :-)





  reply	other threads:[~2011-12-10 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 19:55 Steinar Bang
2011-11-23 20:27 ` Steinar Bang
2011-12-06 21:17   ` Steinar Bang
2011-12-08 14:50     ` Ted Zlatanov
2011-12-08 19:07       ` Steinar Bang
2011-12-10  7:11         ` Steinar Bang
2011-12-10  7:29           ` Steinar Bang
2011-12-10  8:10             ` Backquotes and commas and ",@" (Was: gnus-sync-save fails with "wrong-type-argument number-or-marker-p") Steinar Bang
2011-12-10  9:04               ` Backquotes and commas and ",@" Andreas Schwab
2011-12-10  9:52                 ` Steinar Bang
2011-12-10 10:39               ` Ted Zlatanov
2011-12-10 11:07         ` gnus-sync-save fails with "wrong-type-argument number-or-marker-p" Ted Zlatanov
2011-12-10 14:19           ` Steinar Bang [this message]
2011-12-10 14:45             ` Steinar Bang
2011-12-10 14:49               ` Steinar Bang

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=87iplofr0f.fsf@dod.no \
    --to=sb@dod.no \
    --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).