Thanks again @movq@www.uninformativ.de !! I have figured things out and set up Jenny and Vim completion following your blog post! Cheers!
@movq@www.uninformativ.de yeah, it seems like it. But I don’t mind using neomutt to go through my feed, it feel like a huge upgrade compared to the usual pager 😄
@prologic Haha! I’m still figuring my way around but Thank you!
Welcome @aelaraji@aelaraji.com!
What the heck is going on with the encoding here?! The feed’s Content-Type header does not include any charset, but I’m still relying on the official twtxt client to fetch and parse feeds. Haven’t noticed this with any other feeds. Where in the chain is this messed up? :-? Seems like the “space” is the Unicode line separator U+2028, that we use for newlines.
@lyse@lyse.isobeef.org Thank you! and sorry, I’ve just noticed your twt. About the funky characters, it’s probably something off with my editor, I’ve just ssh-ed from mobile and checked my .txt file, it looked like that when I cat the file but normal on neoutt. I’ll try and see what’s the deal first thing in the morning. (/me wondering if the same thing would happen with this twt)
yep, it did! And it’s definitely something with vim.
OK time to put this to the test, I ended up setting my $VISUAL env
{-here-} variable, so that jenny can launch neovim instead of plain old vi like
{-here-} it is instructed in the code. But as you can see, I still get these
{-here-} wired new lines every ~70th character (marked them with {-here-})
@aelaraji@aelaraji.com Nice, I can confirm it’s now fixed. I reckon the Content-Type: text/plain; charset=utf-8 did the trick. Something in the twtxt client must have incorrectly guessed ISO-8859-1 or something along those lines when there was no charset advertised in the response header.
@lyse@lyse.isobeef.org This ☝️
@lyse@lyse.isobeef.org Awesome! glad to hear that!