unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Tom Davey <tom@tomdavey.com>, Emanuel Berg <incal@dataswamp.org>,
	"emacs-tangents@gnu.org" <emacs-tangents@gnu.org>
Subject: Re: 2022-06-06 Emacs news
Date: Thu, 9 Jun 2022 10:21:41 +0300	[thread overview]
Message-ID: <YqGfhFhAl2cS/hKE@protected.localdomain> (raw)
In-Reply-To: <87o7z2s9w8.fsf@mbork.pl>

* Marcin Borkowski <mbork@mbork.pl> [2022-06-09 08:06]:
> 
> On 2022-06-08, at 21:19, Jean Louis <bugs@gnu.support> wrote:
> 
> > On June 8, 2022 4:03:23 PM UTC, Marcin Borkowski <mbork@mbork.pl> wrote:
> >
> > Instead, you can use filtering and create email folder just for
> > single mailing list. It will not bother you unless you look into
> > the folder.
> >
> > And I use sorting by thread in Mutt email client, with single key I can delete whole of the thread.
> >
> > With few email settings, reading becomes joy.
> 
> OTOH, I use mu4e, which means that (a) I store my emails locally, and
> disk space is _not_ infinite, (b) I don't even use "folders" (mu4e is
> search-based; of course, I _could_ filter out emacs-devel), and, most
> importantly (c) I don't have time to study emacs-devel anyway, so why
> should I nourish a hoarding disorder?

There are various ways how people use email. Me I do not download
Emacs development emails to my local computer. I read them on IMAP
server by using Mutt client. Thus only headers are read, I can see
subjects and decide if I wish to read specific email. I can mark
threads of emails without downloading them and remove them, and focus
on just few of my interest.

Regarding mu4e, that is good to find emails, of course, especially
when there is mailing list in question.

In my work I deal mostly with people rather than with mailing lists,
and in this case most important for me is our previous conversation,
between various people and myself. Thus I am so much often first
searching for conversation with person (list of related emails), and
then maybe for some specific email.

Thus I do use local Maildir folders. 

Each conversation is very easy to find, and I usually have it within a
second and by single key press in Emacs.

To ensure that conversation is easily found, when sending emails and
receiving emails, they are all recorded in specific folder for that
email address. That configuration serves as foundation to quickly
finding all previous emails related to specific contact.

For example, conversation for mbork@example.com would be saved in
Maildir folder ~/Maildir/mbork@example.com and by searching for
"borkowski" or by email address, I find your name, then I press "l"
which is in vi world "left arrow", and stands on my side for "action"
or "go right".

Email conversation or list of emails is opened by using Mutt client
(sometimes within vterm), though it could be possible in Emacs too,
there is Maildir package.

Then within the conversation I may look for particular terms or query
it various ways.

The above setup spares me of using mu tools to index emails and also
tedious mu4e 

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2022-06-09  7:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  4:49 2022-06-06 Emacs news Sacha Chua
2022-06-07  4:55 ` Emanuel Berg
2022-06-07 11:13   ` Jean Louis
2022-06-07 13:20     ` Emanuel Berg
2022-06-07 13:47       ` How to send links for Emacs News " Sacha Chua
2022-06-07 14:58         ` Emanuel Berg
2022-06-07 15:29       ` Jean Louis
2022-06-07 15:48         ` Tom Davey
2022-06-07 16:04           ` Sunil Patel
2022-06-07 16:21           ` Emanuel Berg
2022-06-07 16:25           ` Sacha Chua
2022-06-07 16:36             ` Emanuel Berg
2022-06-07 20:32             ` Jean Louis
2022-06-07 23:55               ` Emanuel Berg
2022-06-08  4:40                 ` Jean Louis
2022-06-08  5:30                   ` Emanuel Berg
2022-06-08  3:37               ` Sacha Chua
2022-06-08  4:00                 ` Emanuel Berg
2022-06-08 16:03           ` Marcin Borkowski
2022-06-08 19:19             ` Jean Louis
2022-06-09  0:57               ` Emanuel Berg
2022-06-09  5:06               ` Marcin Borkowski
2022-06-09  5:22                 ` Emanuel Berg
2022-06-09  7:21                 ` Jean Louis [this message]
2022-06-09  8:01                   ` Emanuel Berg
2022-06-09  0:55             ` Emanuel Berg
2022-06-07 16:44         ` Emanuel Berg

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=YqGfhFhAl2cS/hKE@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=incal@dataswamp.org \
    --cc=mbork@mbork.pl \
    --cc=tom@tomdavey.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).