Gnus development mailing list
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org, hobbes@poukram.net,
	Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: gnorb can't find moved messages
Date: Fri, 28 Sep 2018 13:36:02 -1000	[thread overview]
Message-ID: <s6jefddkxel.fsf@bobnewell.net> (raw)
In-Reply-To: <87d0syoo88.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 27 Sep 2018 10:16:07 -0700")

This problem also arose for me when I very first started to
use Gnorb, and also surprised me as I thought the registry
would act as a sort of invariant pointer. However, it didn't.

It came up because I use gmail as my primary service and use
gnus to access with IMAP (with no local storage). Gmail has a
funny sort of structure where everything appears in the "All
Mail" folder as well as possibly in one or more individual
folders (really tags, but it works like folders).

Generally what I do is "archive" my "inbox" mail when I'm done
with it. All that does is remove the "inbox" tag, leaving the
"All Mail" tag in place. But if I had marked the mail for
tracking with Gnorb while in the inbox, which seems the normal
way to do things (act on the mail before archiving), the
org-mode link would be set to "inbox". After archiving, the
link would be broken.

So, I, um "solved" this by writing advice that would catch any
attempt to create a Gmail inbox link and change it to a Gmail
All Mail link. Then the mail is always found and the link is
always valid.

Talk about crude and brute force! But it's actually a fairly
general solution. I think I may have actually had the chutzpah
to post the code on my website, but I'm hoping I'm wrong about
that.

Aloha from Hawai`i nei,

-- 
Bob Newell
Honolulu, Hawai`i
* Via Gnus/BBDB/Org/Emacs/Linux *



  reply	other threads:[~2018-09-28 23:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27 12:15 Rémi Letot
2018-09-27 17:16 ` Eric Abrahamsen
2018-09-28 23:36   ` Bob Newell [this message]
2018-09-29 17:47     ` Eric Abrahamsen
2018-09-29 19:54       ` Eric Abrahamsen
2018-09-30 18:12         ` Rémi Letot
2018-10-01  3:41           ` 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=s6jefddkxel.fsf@bobnewell.net \
    --to=bobnewell@bobnewell.net \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    --cc=hobbes@poukram.net \
    /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).