Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: paul poulsen <physiculus@gmail.com>
To: info-gnus-english@gnu.org, eric@ericabrahamsen.net
Subject: Re: splitting Gmail account just copy not move :-(
Date: Fri, 2 Aug 2019 10:11:31 +0200	[thread overview]
Message-ID: <CAEK1CZFg_N9ez-BEqHFY4n1YxFS9Bg_=+nckjf9qabobaEruGw@mail.gmail.com> (raw)
In-Reply-To: <87y30cehx4.fsf@ericabrahamsen.net>


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

Eric Abrahamsen <eric@ericabrahamsen.net> schrieb am Do., 1. Aug. 2019,
22:43:

> physiculus <physiculus@gmail.com> writes:
>
> > Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> >
> >>
> >> Is that the only label it shows? What else is in the assoc list?
> > It depends on the folder in Gmail.
> > Sometimes it shows ((X-GM-LABELS . "(\\Important \\Inbox)")) or
> > ((X-GM-LABELS . "(\\Inbox \\Sent \\Starred)"))
>
> And you're sure that you're opening a message that has some specific
> label defined on it?
>
Yes, because gmail show them and the code from Eric A. show them also.

I've also seen some indication that you might need to tell Gmail to
> specifically export your custom labels as flags (or folders?), do you
> see anything like that here:
>
> https://mail.google.com/mail/#settings/labels

Oh i cannot see any option to export there?

Otherwise, I'm fresh out of ideas! Sorry...
>
> >> And if you open the message and hit "t" (to toggle displaying all
> >> headers), what does the X-GM-LABELS header look like in the article
> >> buffer?
> >>
> > It didn't see this header...
>
> Oh I see, it's not an actual header, just something you can request from
> Gmail.
>
I don't understand this, because the code from Eric A. show them from
inside gnus.... Could you please explain?

Regards
Poul


>
> _______________________________________________
> info-gnus-english mailing list
> info-gnus-english@gnu.org
> https://lists.gnu.org/mailman/listinfo/info-gnus-english
>

[-- Attachment #1.2: Type: text/html, Size: 3490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 162 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2019-08-02  8:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 17:52 physiculus
2019-07-29  9:19 ` Lars-Johan Liman
2019-07-29 15:51   ` Eric Abrahamsen
2019-07-29 16:38     ` physiculus
2019-07-29 17:06       ` Eric Abrahamsen
2019-07-29 17:13         ` physiculus
2019-07-29 17:28           ` Eric Abrahamsen
2019-07-29 16:41   ` physiculus
2019-07-29 17:18     ` Eric Abrahamsen
2019-07-30  6:01       ` physiculus
2019-07-30  6:16       ` physiculus
2019-07-30 17:49         ` Eric Abrahamsen
2019-07-31 15:09           ` physiculus
2019-07-31 17:24             ` Eric Abrahamsen
2019-08-01  8:23               ` physiculus
2019-08-01 20:42                 ` Eric Abrahamsen
2019-08-02  8:11                   ` paul poulsen [this message]
2019-08-02 16:14                     ` 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='CAEK1CZFg_N9ez-BEqHFY4n1YxFS9Bg_=+nckjf9qabobaEruGw@mail.gmail.com' \
    --to=physiculus@gmail.com \
    --cc=eric@ericabrahamsen.net \
    --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).