https://blah.rako.space/users/rakoo
From Matthieu Rakotojaona to ~lioploum/offpunk-users
Ploum <sourcehut24@ploum.eu> wrote: > Testing is welcome! Awesome ! It works exactly as expected. I love where this is going. Here are a few quirks I came into: - when using an invalid "index", offpunk crashes: ``` ON> open sanothue Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/offpunk.py", line 1052, in do_open
From Matthieu Rakotojaona to ~lioploum/offpunk-users
Hello there, Currently the workflow for images or third-party resources is a bit cumbersome if images are not supported in the terminal: - exit view mode - open image url, which shows nothing - use "open" to open in the handler, or "open url" to open in the browser - use "back" to go back to the page This is because "open" only works on the current page. Is it possible to make it work on a target page, like tour ? Something like `open 3 6-10` to open all the links directly via their url for example.
From Matthieu Rakotojaona to ~lioploum/offpunk-users
Ploum <sourcehut24@ploum.eu> wrote: > If someone is on those platforms, don’t hesitate to tell him about > Offpunk and ask him what is plans are for PWR. I would be very > interested to get in touch. The code is on github, so I guess if you still have an account you can start a discussion there (although I'd love to see the discussion happen in this mailing-list) -- Matthieu Rakotojaona
From Matthieu Rakotojaona to ~lioploum/offpunk-users
Hey there, I just came across this page that describes a terminal web reader that seems to be architectured around the same ideas as offpunk's tour along with its offline mode: https://muxup.com/pwr It looks like offpunk is more "advanced" but I thought it was interesting that other people had the same need. -- Matthieu Rakotojaona
From Matthieu Rakotojaona to ~bitfehler/vomit
Hey :) Conrad Hoffmann <ch@bitfehler.net> wrote: > I'll take a closer look sometime, but for now I have decided that I no > longer want to work with Maildir, and am busy porting all my tooling to > m2dir [1] (full disclosure: which I made up myself). I actually discovered vomit because I stumbled upon m2dir first, and I quite like the idea although the migration path is probably a bit too long for me right now. I'll also keep an eye on that though because it's interesting :) -- Matthieu Rakotojaona
From Matthieu Rakotojaona to ~bitfehler/vomit
Hey there, I stumbled upon your project and am happy to find someone else is fixated on handling mail directly from the terminal. In my different searches I stumbled upon mblaze at https://github.com/leahneukirchen/mblaze. Are you familiar with it ? There seems to be some use cases that overlap. It enabled me to build my own MUA in ~300 lines of different scripting over at https://sr.ht/~rakoo/omail/. The code is probably a mess, but it's a small mess and it's my mess so I can still understand it. In any case I'll happily what you're doing over here :) -- Matthieu Rakotojaona
From Matthieu Rakotojaona to ~migadu/alps-devel
Simon Ser <contact@emersion.fr> wrote: > Yeah, I think so. Maybe there's an opportunity to simplify some code here, > by introducing a function which matches exactly a text/* MIME type without any > fallback logic like: > > func (msg *IMAPMessage) inlineTextPart(subtype string) *IMAPPartNode > > And then using that to implement TextPart and HTMLPart, e.g. > > if part := msg.inlineTextPart("plain"); part != nil { > return part > } > return msg.inlineTextPart("html")
From to ~migadu/alps-devel
> Hm, but with this we'd stop iterating at the first text/html part even > if there is a text/plain part after… > > We probably want to add isTextPlain to the check as well. We need to decide what the heuristic is: is it "first text/plain part, and if none take text/html" ? I receive some mails from a mailing list that roughly have this structure: 1. alternative 1.1 text/plain (content) 1.1 text/html (same content but in html) 2. text/plain (footer of the mailing list)
From Matthieu Rakotojaona to ~migadu/alps-devel
As soon as we have found a "best" part to display, stop recursing into the whole bodystructure --- plugins/base/imap.go | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/plugins/base/imap.go b/plugins/base/imap.go index e9636e3..2e85287 100644 --- a/plugins/base/imap.go +++ b/plugins/base/imap.go @@ -211,6 +211,10 @@ func (msg *IMAPMessage) TextPart() *IMAPPartNode { var best *IMAPPartNode isTextPlain := false msg.BodyStructure.Walk(func(path []int, part imap.BodyStructure) bool { [message trimmed]
From Matthieu Rakotojaona to ~migadu/alps-devel
--- Thanks for alps ! This is the same as 1e069e9, but for the base theme :) plugins/base/public/message.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/plugins/base/public/message.html b/plugins/base/public/message.html index 38b41c5..26fa5b2 100644 --- a/plugins/base/public/message.html +++ b/plugins/base/public/message.html @@ -17,7 +17,7 @@ </h2> [message trimmed]