From: physiculus <physiculus@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: splitting Gmail account just copy not move :-(
Date: Wed, 31 Jul 2019 17:09:48 +0200 [thread overview]
Message-ID: <87k1by9r5v.fsf@googlemail.com> (raw)
In-Reply-To: <87mugvv2dn.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 30 Jul 2019 10:49:40 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> That just means that Gnus has requested the labels header, not
> necessarily that the message has one.
>
> Here's the most certain way I can think of to see if this is working:
>
> 1. Using Gmail's web interface, pick a message and add a label to it.
> 2. Go back to Gnus, refresh new news, and open the group so that there's
> only that one message in the Summary buffer (with M-1 RET or
> something).
> 3. Do M-: (mail-header-extra (car gnus-newsgroup-headers))
> 4. Check if there's a X-GM-LABELS entry in the resulting assoc list.
>
> And let us know what it looks like!
Hello,
first thank you for the support here!
Second unfortunately the situation is confusing.
Your code only shows the standard Google tags (INBOX, IMPORTANT,
STARRED, but not my own created ones (emms, gnus, Teich ...)
The Web-Interface show them in the right place and i can change them
there.
And if i use Chrome to login on my PC the changes are transferred to
google, because i see the changes on my smartphone inside gmail.
Very strange...
Also strange: Your assoc list shows different standard labels than
gmail.
Example:
I labeled a message with "Teich". Gmail shows it and put it in folder
Gmail/Teich.
gnus shows "((X-GM-LABELS . "(\\Important)"))
Message buffer show ((X-GM-LABELS . "(\\Important)")) Specified image bit depth is not supported by XRender
Specified image bit depth is not supported by XRender"
What does it mean?
Regards
Poul
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2019-07-31 15:09 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 [this message]
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
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=87k1by9r5v.fsf@googlemail.com \
--to=physiculus@gmail.com \
--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).