Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Himalaya: CLI to Manage Emails

github.com

Post reply on HN
Print view View original

91–100 of 102 posts

Re: Himalaya: CLI to Manage Emails

#91

Post by goku12 »

dmd wrote: post #23
smartmic wrote: post #18

Earlier quoted context omitted.

There are many choices for email client interfaces. HTML for email does not have a good reputation among hackers. After all, email can be considered an ancient technology and is historically based on plain text - HTML breaks not only the philosophy but also many of the tools developed around email. I have found a sweet spot for an email client between a pure CLI and a full-featured (HTML) GUI client - I use Emacs Gnu…

> HTML breaks not only the philosophy but also many of the tools developed around email I was one of these die-hard-text-only people, back in the mid to late 90s. It was true. People were sending HTML/rich text emails, and it broke everything, and it was awful to read with. Not to mention the kilobytes of bandwidth wasted! But it's 2024 now. There are vastly more tools that can deal with HTML email than those that ca…

As someone who started using plaintext emails recently, HTML emails are still awful in 2024. Besides being a ugly hack on top of an originally text-only protocol, it encourages bad practices like top-posting, bad alignment etc. What's really intolerable though, is the external and dynamic content in email. I expect email to be a long-term record, not something that changes after I receive it. They should find another tool for that. Besides, most GUI clients just block external content due to security risks anyway.

Re: Himalaya: CLI to Manage Emails

#92

Post by ninjin »

choilive wrote: post #26
dmd wrote: post #23

Earlier quoted context omitted.

> HTML breaks not only the philosophy but also many of the tools developed around email I was one of these die-hard-text-only people, back in the mid to late 90s. It was true. People were sending HTML/rich text emails, and it broke everything, and it was awful to read with. Not to mention the kilobytes of bandwidth wasted! But it's 2024 now. There are vastly more tools that can deal with HTML email than those that ca…

Perhaps LLMs can solve this somewhat? Not for email summarization - but to intelligently strip away all the HTML fluff and return a plain text version of the contents.

It is a solved problem. Here is a solution that requires something of the order of 1,000,000th of the resources of your proposed idea, no subscription, and runs so fast that you would not even notice it on a machine from 20 years ago:

    > grep text/html ~/.mailcap
    text/html; lynx -width 72 -assume_charset=%{charset} -display_charset=utf-8 -dump %s | sed 's|^   ||'; nametemplate=%s.html; copiousoutput
If you want something more modern:

    text/html; webdump -dli

Re: Himalaya: CLI to Manage Emails

#93

Post by snthpy »

rubicks wrote: post #56
cfiggers wrote: post #55

This is cool. I like the ongoing trend of TUIs getting more attention and use. A little while ago I wrote my own little TUI tool using Textual that interfaces with Outlook using pywin32. I really only needed (need) one specific feature above and beyond what Outlook already does. And that is, I wanted a Vim-like UX for assigning categories to emails and archiving/deleting them. What I have now works surprisingly well…

I have been looking for something like this. Got a link to your project?

I've also been looking for something like this. Was going to post on the Textual discord actuality to ask around.

Most of the email tools like notmuch tend to be GPL which limits adoption IMHO.

Re: Himalaya: CLI to Manage Emails

#94

Post by pabs3 »

ninjin wrote: post #92
choilive wrote: post #26

Earlier quoted context omitted.

Perhaps LLMs can solve this somewhat? Not for email summarization - but to intelligently strip away all the HTML fluff and return a plain text version of the contents.

It is a solved problem. Here is a solution that requires something of the order of 1,000,000th of the resources of your proposed idea, no subscription, and runs so fast that you would not even notice it on a machine from 20 years ago: > grep text/html ~/.mailcap text/html; lynx -width 72 -assume_charset=%{charset} -display_charset=utf-8 -dump %s | sed 's|^ ||'; nametemplate=%s.html; copiousoutput If you want somethin…

Whats webdump?

Re: Himalaya: CLI to Manage Emails

#95

Post by ninjin »

pabs3 wrote: post #94
ninjin wrote: post #92

Earlier quoted context omitted.

It is a solved problem. Here is a solution that requires something of the order of 1,000,000th of the resources of your proposed idea, no subscription, and runs so fast that you would not even notice it on a machine from 20 years ago: > grep text/html ~/.mailcap text/html; lynx -width 72 -assume_charset=%{charset} -display_charset=utf-8 -dump %s | sed 's|^ ||'; nametemplate=%s.html; copiousoutput If you want somethin…

Whats webdump?

https://codemadness.org/git/webdump

Re: Himalaya: CLI to Manage Emails

#98

Post by 0fflineuser »

e12e wrote: post #88
0fflineuser wrote: post #22

Earlier quoted context omitted.

Personnaly, I use https://gitlab.com/shackra/goimapnotify , you can add a `~/.config/imapnotify/{{ youremailaddresshere }}.yaml` config file for each of your email addresses and enable and start it as a systemd service with `systemctl --user enable ---now goimapnotify@{{ youremailaddresshere }}.service` Here is and example of a config file for a gmail address : ``` host: imap.gmail.com port: 993 tls: true tlsOptions:…

> tlsOptions: > rejectUnauthorized: false Means trust any cert?

Yes, thanks for pointing it out, it should be true.

I took it from my config which I did a long time ago and I guess I didn't pay attention enough when doing it, my bad !

Re: Himalaya: CLI to Manage Emails

#99

Post by faitswulff »

xyst wrote: post #60

I feel like this has been here before, glad it's kept up with updates. Will have to give this a shot soon. From strictly reading the docs, I love these features: * oauth2 * json output But do I need to run the "himalaya ..." command every so often to get fresh e-mails? Or can I leave TUI open and it will refresh in the background? When composing messages, does anybody know if the "From" header can be re-written like…

It's designed to be a CLI tool as opposed to a TUI so that it's more composable with other CLI tools. So you can use it as a building block to create a TUI, but it's not one by default.
Post reply on HN