~sircmpwn/public-inbox

4 2

Re: [PATCH useplaintext.email 2/2] Add neatmail

Details
Message ID
<20211006172431.GB20996@gac.attlocal.net>
DKIM signature
pass
Download raw message
On Wed, 06 Oct 2021 23:44:04 +0330 Ali Gholami Rudi <ali@rudi.ir> wrote:

Hi Ali,

I haven't tried neatmail yet but I'm looking forward to giving it a test drive
soon.

That said, I've had a lot of fun hacking on neatvi so far. Thank you for making
neatvi! It's given me a lot of great ideas.

> Neatmail generates text/plain messages, for both new emails and
> replies.  It does not, however, directly show or edit the emails; an
> external editor must be used for that.

This is the same for bower. I use vis to edit and compose my emails. I use msmtp
to send them and offlineimap to pull them in.

bower is a powerful notmuch client. It relegates other duties to programs better
capable of performing them.

https://git.sr.ht/~martanne/vis

I use fold from coreutils which allows me to wrap lines at an arbitrary column 
position from vis via it's pipe operator:

https://github.com/martanne/vis/wiki/Tips-and-Tricks

I have a wrapper for the command in the tips and tricks to make it shorter to type.

> For Neatmail users, reading text/html is probably very inconvenient,
> because they have to either pipe the message to a text-mode browser
> to convert them to something more editor-friendly or use a browser
> to read the body.  Writing text/html is even more difficult.

This is the same in bower. bower will use an external program to convert the html
email and/or open it in an external program.

bower has some defaults that make this possible out of the box given the dependencies
are installed:

https://github.com/wangp/bower/blob/512b8be936db268d8ea94608cab486725cc2ec60/bower.conf.sample#L50
https://github.com/wangp/bower/blob/512b8be936db268d8ea94608cab486725cc2ec60/src/prog_config.m#L1049

Any arbitrary external program can be configure to do this if it "fits the bill".

bower does not render html emails as far as I know.

By default bower uses lynx to dump HTML emails (configurable):

https://github.com/wangp/bower/blob/512b8be936db268d8ea94608cab486725cc2ec60/src/prog_config.m#L1031

all best,

jgart

Re: [PATCH useplaintext.email 2/2] Add neatmail

Details
Message ID
<CESY2VALOJ96.1WFX4FH2FGALD@taiga>
In-Reply-To
<20211006172431.GB20996@gac.attlocal.net> (view parent)
DKIM signature
pass
Download raw message
Thanks for clarifying! Can you each tell me if your email client has a
recommended or default editor, and if this editor does the right thing?
Vim, for instance, provides a mail authoring mode which properly handles
text wrapping. I can't endorse the cilent unless the default behavior is
to send correctly formatted emails, without additional user
intervention, lest users pick these clients up based on the endorsement,
expecting them to handle formatting their emails for them, just to find
out later they've been a nuisance to the people receiving their emails
because they were not composed right.

Re: [PATCH useplaintext.email 2/2] Add neatmail

Details
Message ID
<20211007095959.GD3412@gac.attlocal.net>
In-Reply-To
<CESY2VALOJ96.1WFX4FH2FGALD@taiga> (view parent)
DKIM signature
pass
Download raw message
On Thu, 07 Oct 2021 08:01:25 +0200 "Drew DeVault" <sir@cmpwn.com> wrote:
> Thanks for clarifying! Can you each tell me if your email client has a
> recommended or default editor, and if this editor does the right thing?
> Vim, for instance, provides a mail authoring mode which properly handles
> text wrapping. I can't endorse the cilent unless the default behavior is
> to send correctly formatted emails, without additional user
> intervention, lest users pick these clients up based on the endorsement,
> expecting them to handle formatting their emails for them, just to find
> out later they've been a nuisance to the people receiving their emails
> because they were not composed right.

For bower, 

# The default is to use $EDITOR, or else "vi".

I took that from here:

https://github.com/wangp/bower/blob/512b8be936db268d8ea94608cab486725cc2ec60/bower.conf.sample#L36

It looks like the default conf recommends:

editor = vim '+set ft=mail'

Re: [PATCH useplaintext.email 2/2] Add neatmail

Details
Message ID
<CET8AJOVPOMD.2EI6FSPUUVK81@taiga>
In-Reply-To
<20211007095959.GD3412@gac.attlocal.net> (view parent)
DKIM signature
pass
Download raw message
On Thu Oct 7, 2021 at 3:59 PM CEST, jgart wrote:
> For bower,
>
> # The default is to use $EDITOR, or else "vi".
>
> I took that from here:
>
> https://github.com/wangp/bower/blob/512b8be936db268d8ea94608cab486725cc2ec60/bower.conf.sample#L36
>
> It looks like the default conf recommends:
>
> editor = vim '+set ft=mail'

Okay, +1 for bower then. Waiting on the answer from neatmail.

Re: [PATCH useplaintext.email 2/2] Add neatmail

Details
Message ID
<20211007102505.GB7951@gac.attlocal.net>
In-Reply-To
<CET8AJOVPOMD.2EI6FSPUUVK81@taiga> (view parent)
DKIM signature
pass
Download raw message
On Thu, 07 Oct 2021 16:01:38 +0200 "Drew DeVault" <sir@cmpwn.com> wrote:
> On Thu Oct 7, 2021 at 3:59 PM CEST, jgart wrote:
> > For bower,
> >
> > # The default is to use $EDITOR, or else "vi".
> >
> > I took that from here:
> >
> > https://github.com/wangp/bower/blob/512b8be936db268d8ea94608cab486725cc2ec60/bower.conf.sample#L36
> >
> > It looks like the default conf recommends:
> >
> > editor = vim '+set ft=mail'
> 
> Okay, +1 for bower then. Waiting on the answer from neatmail.

It sounds like neatmail is completely editor agnostic.

See this tutorial showing a workflow for neatmail:

https://linuxfr.org/users/sygne/journaux/neatmail-un-client-mail-minimaliste

Specifically (translated):

> Neatmail therefore simply performs actions on an mbox file. 
> The basic actions are:
> 
> - mk Generate a list of mails contained in the mbox.
> - ns Generates a list of new mails found in the mbox.
> - pg Displays one of the mails contained in the mbox. 

> We can therefore use it as follows: 

> # Obtient les mails
> pop3
> # liste les mails, triés par fil de discussion
> neatmail mk ‐r ‐st ‐0 18from:48~subject: mbox
> # affiche le 3e mail
> neatmail pg mbox 3
> # prépare une réponse
> neatmail pg ‐r mbox 3 > draft.eml
> vi draft.eml
> # envoie la réponse
> tail ‐n+2 draft.eml | smtp
> # garde une copie de la réponse
> cat draft.eml >> sent
> rm draft.eml

BTW,

Bower was recently added to alpine's repositories:

https://pkgs.alpinelinux.org/packages?name=bower

I'm maintaining the nix and guix packages for bower:

https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/applications/networking/mailreaders/notmuch-bower/default.nix#L33

bower package is in progress for merge in Guix System:

https://issues.guix.gnu.org/50833

all best,

jgart
Reply to thread Export thread (mbox)