Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: michael.zombok@googlemail.com
Cc: ding@gnus.org
Subject: Re: Ways of selectively accessing only certain mail accounts? (Profiles?)
Date: Tue, 04 Feb 2014 08:41:42 +0100	[thread overview]
Message-ID: <87vbwv5npl.fsf@gnu.org> (raw)
In-Reply-To: <soua9e773dm.fsf@gmx.de> (michael zombok's message of "Tue, 04 Feb 2014 08:17:57 +0100")

michael.zombok@googlemail.com writes:

>     Lars> michael.zombok@googlemail.com writes:
>     >> One thing I was not able to manage with Gnus so far is to
>     >> selectively access only certain mail accounts. The background is
>     >> that I would like to split my private and work related mails,
>     >> hence having something like two seperate Gnus 'profiles' each
>     >> with its own accounts, mails, settings, etc.
>
>     Lars> I think what most people do is just split the mail into
>     Lars> appropriate work/private groups...
>
> yeah, I am already doing this. But I even don't want to see the groups
> (and new mails getting into these groups at the weekend :)

You could use topics to separate Work & Private groups.  And it should
be easy to add some elisp to `gnus-topic-mode-hook' that collapses the
Work topic on weekends automatically (see `gnus-topic-hide-topic').  Of
course, you can still expand it easily again and start working on
weekends...

Bye,
Tassilo



      reply	other threads:[~2014-02-04  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 18:05 michael.zombok
2014-02-03 21:59 ` Lars Ingebrigtsen
2014-02-03 22:57   ` Mark Simpson
2014-02-04  2:57     ` Dave Goldberg
2014-02-04  7:20       ` michael.zombok
2014-02-04  7:17   ` michael.zombok
2014-02-04  7:41     ` Tassilo Horn [this message]

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=87vbwv5npl.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    --cc=michael.zombok@googlemail.com \
    /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).