From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: gfp <gfp@posteo.at>
Cc: Joel Reicher <joel.reicher@gmail.com>,
Christopher Howard <christopher@librehacker.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: E-mail package
Date: Sun, 29 Dec 2024 02:49:16 +0200 [thread overview]
Message-ID: <18789.9100173794$1735433408@news.gmane.org> (raw)
In-Reply-To: <5fd0a231-55cb-4711-ae08-a3652dcede15@posteo.at> (gfp@posteo.at's message of "Thu, 26 Dec 2024 20:37:06 +0000")
gfp <gfp@posteo.at> writes:
>> What do you mean by "graphical"?
>
> I mean to have an overview about all folders.
> Folders of unread messages and also of read messages.
> Somehow everything at once. In my opinion I can assess better what´s
> going on, from whom I got a new email, and from whom I didn´t get one.
> But that´s my view at the moment. I am not used seeing only new emails.
> May be I can adjust to it at some stage.
>
You could try it out for a time, to see it's benefits. It allows you to
filter out the things you don't need a time.
You can always view all groups by pressing A u in the group buffer, you can also rebind that
to another key such as o.
However you can customize also customize gnus-permanently-visible-groups
to have all the groups you want to have always visible. I my self for example have
set this to always have the INBOX visible.
You can set can customize the variable to a wild card to always view all
groups.
PS: Please don't top-post if you can.
next prev parent reply other threads:[~2024-12-29 0:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 17:27 E-mail package Christopher Howard
2024-12-23 18:50 ` gfp
2024-12-24 16:48 ` Christopher Howard
2024-12-25 9:22 ` gfp
2024-12-26 6:27 ` Joel Reicher
2024-12-26 20:37 ` gfp
2024-12-26 21:39 ` tpeplt
2024-12-28 3:38 ` divya
2024-12-28 4:10 ` Bob Newell
2024-12-28 7:13 ` Joel Reicher
2024-12-28 17:39 ` tpeplt
2024-12-28 18:13 ` Jean Louis
2024-12-30 17:56 ` Christopher Howard
2024-12-29 0:49 ` Björn Bidar [this message]
[not found] ` <87frm9ugpg.fsf@gmail.com>
2024-12-30 10:58 ` gfp
2024-12-30 11:16 ` tomas
2024-12-30 11:43 ` gfp
2024-12-30 12:18 ` tomas
2024-12-26 16:28 ` Christopher Howard
2024-12-27 15:47 ` Eric S Fraga
[not found] ` <877c7mdk70.fsf@gmail.com>
2024-12-29 20:49 ` gfp
2024-12-30 4:27 ` Björn Bidar
[not found] ` <87zfkdyevq.fsf@>
2024-12-30 12:04 ` gfp
2024-12-30 13:49 ` gfp
2025-01-01 1:52 ` Björn Bidar
[not found] ` <871pxnxpv8.fsf@>
2025-01-01 13:19 ` gfp
2024-12-27 15:45 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2024-10-19 14:15 gfp
2024-10-19 15:21 ` Jude DaShiell
2024-10-20 3:19 ` W. Greenhouse
2024-10-21 8:47 ` Eric S Fraga
2024-12-06 22:11 ` Jean Louis
2024-12-21 11:50 ` Joel Reicher
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='18789.9100173794$1735433408@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=christopher@librehacker.com \
--cc=gfp@posteo.at \
--cc=help-gnu-emacs@gnu.org \
--cc=joel.reicher@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).