Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
Subject: How to do you manage Threads, your inbox, your sent folder, your archive
Date: Tue, 21 Dec 2021 00:58:31 +0100	[thread overview]
Message-ID: <> (raw)


I was reading :

I come from mu4e. With mu4e I never had to worry about threads, I could
enable or disable their display with a keybinding and that's was
it. Simpler times without sieve and dovecot.

With gnus, I am a bit confuse.

We have the variable `gnus-message-archive-method' and
`gnus-message-archive-group' to archive sent mails.

We have also `gnus-posting-styles' to fill headers when composing a
mail, to eg, CC, BCC or GCC (what does exactly means GCC?), eventually
to myself or one of my folders.

Then we can set `gnus-parameters' to `gcc-self' for some groups (but
here I am lost).

In top of that if you use, as another secondary method than you
imap/pop mail server, you eventually have to tweak
`gnus-refer-thread-use-search' to t and `gnus-refer-article-method' to
(something ?) to be able to retrieve your threads between back-ends.

Is it possible to archive the whole threads of whom I initiate/reply ?

What do you do with all theses variables ?

For reference in my excursion in gnus, I read the dotfiles of jao and
jwiegley, if you'are kind enough to share yours, thank's you.

             reply	other threads:[~2021-12-20 23:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 23:58 dal-blazej [this message]
2021-12-21  0:18 ` Emanuel Berg via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2022-03-03 16:44   ` dal-blazej
2022-03-03 18:09     ` Emanuel Berg via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2021-12-22 23:04 ` Eric Abrahamsen
2021-12-25 10:03 ` 황병희

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).