I liked mutt, but this seems promising as well.
Himalaya: CLI to Manage Emails
61–70 of 102 posts
Re: Himalaya: CLI to Manage Emails
#62I can go a week now without receiving a single useful email...gmail or fastmail are fine
They are, but I have a cron job that fetches my email every 5 minutes. No need to keep a tab open, or do the auth routine again and again. And I used to put an indicator in my status bar displaying the unread count. There’s a whole world of integration when you just dig a bit deeper.
Re: Himalaya: CLI to Manage Emails
#63Honest question - Why use interfaces like this, but not regular HTML client?
This question shows how far we’ve travelled from the original concepts of sending/receiving/viewing email. I just found it funny that you said “regular HTML client”, as if that was the default interface for email. Originally, it was all text, so this post is in many ways closer to how many thought of a “regular” client. But ever since Hotmail, it’s been a gradual shift away from command line email towards web applications. Desktop GUIs are still (kind of) holding on, but even they are more likely than not to be an Electron app.
To answer your question, these days, I’m not sure. There are so many extra features that email providers (Gmail/Office365) include in their web interfaces, it’s hard to not make the argument that the web interfaces are the better way to use email.
Re: Himalaya: CLI to Manage Emails
#64Is anyone using local LLMs to manage their email? This seems like it could be helpful to hook that up.
Re: Himalaya: CLI to Manage Emails
#65Genuine question - the HN title says "CLI to..." but looking at the GitHub repo I don't see any CLI-centric documentation.
I do see
$ himalaya envelope list --account posteo --folder Archives.FOSS --page 2
I guess my question is: is this different than PINE (or any other terminal-based, interactive email client)?
Re: Himalaya: CLI to Manage Emails
#66Earlier quoted context omitted.
> But it's 2024 now. There are vastly more tools that can deal with HTML email than those that can't. Like, I wouldn't be surprised if it's 4 orders of magnitude. Is it? Whatsapp, Signal, Slack, Notion, ChatGTP, are amongst the apps I use daily - and used by many non-hacker daily, that's pretty much "text only". all support some (subset of) markdown, which is close to "plain text" than to "HTML" in editing and displa…
Slack is far from plain text: https://api.slack.com/block-kit/building
The Slack blocks format is horrendous, and not very powerful.
Re: Himalaya: CLI to Manage Emails
#67How does this compare to old school mblaze tools?
Re: Himalaya: CLI to Manage Emails
#68Neat. I used and loved “mh” in college, but that was before html email became prevalent. It was beautiful to have different commands and treat emails as individual files. Unfortunately mh was grotty old C code and just couldn’t keep up (IMHO) with how we use email today. https://en.m.wikipedia.org/wiki/MH_Message_Handling_System
> I used and loved “mh” in college Same and also `nmh`. Loved how you could combine the various parts to make your own tools.
me too - nmh and MH-E still learning though
Re: Himalaya: CLI to Manage Emails
#69[flagged]
Re: Himalaya: CLI to Manage Emails
#70Genuine question - the HN title says "CLI to..." but looking at the GitHub repo I don't see any CLI-centric documentation. I do see $ himalaya envelope list --account posteo --folder Archives.FOSS --page 2 and a screenshot that looks like PINE. Is that screenshot interactive (like PINE) or does himalaya print that out and then the process exits? I guess my question is: is this different than PINE (or any other termin…
Himalaya is not interactive: while Pine is a TUI, this is a CLI.
Very useful to integrate emails in scripts easily.