Gnus development mailing list
 help / color / mirror / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: ding@gnus.org
Cc: tsdh@gnu.org
Subject: Re: Using gnus with gmail: almost there
Date: Thu, 31 Jul 2014 16:44:06 -0300	[thread overview]
Message-ID: <CAELgYhfJw89tSa3b7HGsseQY5wZiVsQ6eGerfswokbH-5uOnDA@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhc6=0GgDcrf0t=_Ers10JPqeT=4M_XCAVKPnOU8AVYMVw@mail.gmail.com>

Well, this is the best I could come with, considering that emacs
regexps have no negative look-ahead or any fancy stuff:

(setq gnus-parameters
      '(("^[^:]+$"
    (gcc-self . t)
    (gnus-gcc-mark-as-read . t))))

It will work as long as there are no gmail labels including a ':'. If
you know of a better approach, please tell me!

Regards
--
Carlos



On Thu, Jul 31, 2014 at 4:18 PM, Carlos Pita <carlosjosepita@gmail.com> wrote:
> Hi Tassilo,
>
> gcc-self is indeed a great tip, thank you!
>
> As you've become sort of my guru now, I'm asking you further: I'm
> having a hard time trying to match my primary method groups by prefix,
> as in "imap.*"; the problem is that these groups don't show the method
> prefix, only the secondary ones, but I really want to get a similar
> behavior for all my primary select method without having to match on a
> per group basis. Is that possible?
>
> Regards
> --
> Carlos
>
> On Thu, Jul 31, 2014 at 2:56 AM, Tassilo Horn <tsdh@gnu.org> wrote:
>> Carlos <carlosjosepita@gmail.com> writes:
>>
>> Hi Carlos,
>>
>>> 1) I would like to include my sent emails in the threads where they
>>> belong, like in the "conversation" view gmail offers.
>>
>> I do the same.
>>
>>> There is a suggestion somewhere in the net to create a virtual group
>>> merging the inbox and the sent mail groups, but this will only work
>>> for threads in the inbox. Another option is to add a copy of any sent
>>> mail to the current group, i.e. something like:
>>>
>>> (setq gnus-message-archive-group (lambda (g) (concat "nnimap+gmail:" g)))
>>>
>>> But this has some problems: 1.i) I don't know how to do this *only* for the
>>> gmail server. 1.ii) Obviously it doesn't work for emails sent from the
>>> webmail.
>>>
>>> Nevertheless, being able to solve 1.i alone would be very good news for me.
>>
>> Have a look at the `gcc-self' group parameter.
>>
>> ,----[ (info "(gnus)Group Parameters") ]
>> | ‘gcc-self’
>> |      If ‘(gcc-self . t)’ is present in the group parameter list, newly
>> |      composed messages will be ‘Gcc’’d to the current group.  If
>> |      ‘(gcc-self . none)’ is present, no ‘Gcc:’ header will be generated,
>> |      if ‘(gcc-self . "string")’ is present, this string will be inserted
>> |      literally as a ‘gcc’ header.  This parameter takes precedence over
>> |      any default ‘Gcc’ rules as described later (*note Archived
>> |      Messages::), with the exception for messages to resend.
>> |
>> |      *Caveat*: Adding ‘(gcc-self . t)’ to the parameter list of ‘nntp’
>> |      groups (or the like) isn’t valid.  An ‘nntp’ server doesn’t accept
>> |      articles.
>> `----
>>
>> Here's my gcc-self related settings:
>>
>> --8<---------------cut here---------------start------------->8---
>> (setq gnus-parameters
>>       `((,(rx "nnimap+")
>>          (gcc-self . t))
>>         ;; Mailing List exceptions
>>         (,(rx "nnimap+Uni:ml/")
>>          (gcc-self . "nnimap+Uni:Sent"))
>>         (,(rx "nnimap+Fastmail:INBOX.mailinglists.")
>>          (gcc-self . "nnimap+Fastmail:INBOX.Sent Items"))))
>> --8<---------------cut here---------------end--------------->8---
>>
>> So I gcc the current group for all my IMAP accounts, except for mailing
>> list groups, where I gcc the account's sent mail folder.
>>
>> To have that only for your Gmail account, you would change the regex to
>> something like ,(rx "nnimap+Gmail") or whatever you've named your gmail
>> account.
>>
>>> 2) I would like to postpone a message directly to a remote group
>>> (ideally, the gmail drafts folder). Currently I'm able to locally
>>> postpone a message and then move it to the remote group. A way to
>>> automate this is what I can't come with (or, better, to directly store
>>> the draft in the remote group, which I'm afraid is not possible).
>>
>> I think this question pops up here once in a while, but so far nobody
>> seems to have implemented that feature.
>>
>> Bye,
>> Tassilo



  reply	other threads:[~2014-07-31 19:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 13:09 Carlos
2014-07-31  5:56 ` Tassilo Horn
2014-07-31  7:19   ` gcc to remote groups (was: Using gnus with gmail: almost there) Alberto Luaces
2014-07-31  9:05     ` gcc to remote groups Tassilo Horn
2014-07-31  9:27       ` Tassilo Horn
2014-07-31  9:35         ` Alberto Luaces
2014-07-31 19:18   ` Using gnus with gmail: almost there Carlos Pita
2014-07-31 19:44     ` Carlos Pita [this message]
2014-07-31 20:27       ` Carlos Pita
2014-07-31 20:36     ` Adam Sjøgren
2014-08-01  9:01     ` Tassilo Horn
  -- strict thread matches above, loose matches on Subject: below --
2014-07-29  4:00 carlosjosepita

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=CAELgYhfJw89tSa3b7HGsseQY5wZiVsQ6eGerfswokbH-5uOnDA@mail.gmail.com \
    --to=carlosjosepita@gmail.com \
    --cc=ding@gnus.org \
    --cc=tsdh@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).