From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus-sync-save fails with "wrong-type-argument number-or-marker-p"
Date: Sat, 10 Dec 2011 06:07:17 -0500 [thread overview]
Message-ID: <8762hon0re.fsf@lifelogs.com> (raw)
In-Reply-To: <87aa72lw5p.fsf@dod.no>
On Thu, 08 Dec 2011 20:07:30 +0100 Steinar Bang <sb@dod.no> wrote:
>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
>> I'm at a conference so I can't do the code fix properly, but I think
>> if you try the attached patch it will fix the issue.
SB> Unfortunately it didn't. I still get
SB> Wrong type argument: number-or-marker-p, "8-54ce40d61d4b92eda3bffb29c6e0b1c6"
SB> on `gnus-sync-save'.
SB> Here's what I did:
SB> 1. Save the attachment to /tmp/sync-junk.patch
SB> 2. Apply the patch:
#+begin_src sh
cd git/gnus
git apply /tmp/sync-junk.patch
#+end_src
SB> 3. Rebuild gnus:
#+begin_src sh
(cd ~/git/gnus; make clean; make; cd lisp; make tags)
#+end_src
SB> 4. Start a new Emacs with a new Gnus
SB> 5. Run `gnus-sync-read', followed by `g'
SB> 6. Visit a gmane group to make things dirty
SB> 7. Run `gnus-sync-save'. and the issue occurs:
#+begin_example
Wrong type argument: number-or-marker-p, "8-54ce40d61d4b92eda3bffb29c6e0b1c6"
#+end_example
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). 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")
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.
Thanks
Ted
next prev parent reply other threads:[~2011-12-10 11:07 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 ` Ted Zlatanov [this message]
2011-12-10 14:19 ` gnus-sync-save fails with "wrong-type-argument number-or-marker-p" Steinar Bang
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=8762hon0re.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).