Gnus development mailing list
 help / color / mirror / Atom feed
From: hobbes@poukram.net
To: ding@gnus.org
Subject: Re: saving registry is fixed, but gnorb still can't gnorb-org-view
Date: Thu, 02 Apr 2020 15:05:11 +0200	[thread overview]
Message-ID: <87a73uca2g.fsf@sphax> (raw)
In-Reply-To: <87zhbug5l2.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

>> In your case, there's a link that has no message ID part. You could take
>> a look at the Org tree in question and see which it is, and if you know
>> how that link might have been created (or mangled).
>
> Ooh, I might be wrong -- I got bitten by Org's changing link-related
> regular expressions, and fixed some code for the new regexps, and
> apparently wasn't careful enough with the fix. I'm assuming in your
> subtree there's a "plain" link to a Gnus message, ie one that isn't
> wrapped in brackets. Would you eval the function below and see if it
> fixes the problem?
>
> (defun gnorb-scan-links (bound &rest types)
>   (unless (= (point) bound)
>     (let ((alist (mapcar #'list (copy-sequence types))))
>       (while (re-search-forward org-link-any-re bound t)
> 	(pcase-let* ((`(,type ,link) (split-string
> 				      (or
> 				       (match-string-no-properties 2)
> 				       (match-string-no-properties 0))
> 				      ":"))
> 		     (sym (intern-soft type)))
> 	  (when (and sym (memq sym types))
> 	    (push link (alist-get sym alist)))))
>       alist)))

So, after some more experimenting: it's indeed linked to the gnus links
in the org tree.

But all links have brackets, and all have a message id, and I can follow
them. Evaluating the defun didn't help.

If I remove the links, C-c v works like it should, so it's clearly
linked to those links...

Thanks,
-- 
Rémi



  reply	other threads:[~2020-04-02 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 13:32 can't save gnus registry anymore, and gnorb " hobbes
2020-04-01 20:59 ` saving registry is fixed, but gnorb still " Rémi Letot
2020-04-01 22:44   ` Eric Abrahamsen
2020-04-01 23:16     ` Eric Abrahamsen
2020-04-02 13:05       ` hobbes [this message]
2020-04-02 14:55         ` Eric Abrahamsen
2020-04-02 15:03           ` hobbes
2020-04-02 16:28             ` Eric Abrahamsen
2020-04-02 18:15             ` Eric Abrahamsen
2020-04-05 19:18               ` hobbes
2020-04-05 21:32                 ` Eric Abrahamsen

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=87a73uca2g.fsf@sphax \
    --to=hobbes@poukram.net \
    --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).