Re: [DNG] mutt and html

[Hendrik Boom]

Thanks for all the advice.

On Sat, Oct 30, 2021 at 04:13:31PM -0400, Hendrik Boom wrote:
> Until upgraded from ascii to beowulf, HTML messages were tolerable.
> Either they were obvious crap, in which case I just deeted them,
> or they seemed like they were worth viewing, in which case they were 
> usually html attachments, and I could seen the list of attachments by 
> typeing v and selecting the html version -- in which case it would 
> open for me in the chromium browser.
> 
> This stopped working after the upgrade to beowulf.
> 
> I did manage to reconfigure, telling it to use firefox-esr, but that 
> didn't help much.  I connect to my server, the machine on which I run 
> mutt, using ssh -X.  
> So firefox on the server detects I already have a firefox browser 
> on my laptop and proceeds to give the job of browsing the message to 
> my laptop.
> Makes sense, except that my laptop has no way to access the 
> /tmp/mutt/somethingorother.html on the server. 
> 
> And I have not been able to get mutt to call chromium at all.
> 
> Any ideas?

By tring things that were suggested, and trying to make sense of the 
documentation slightly more informed than random, I managed to get 
firefox to display html contents from the server where the files are.

~/.muttrc:

set mailcap_path="~/.mailcap"
auto_view text/html
bind pager Q exit
subscribe racket-us...@googlegroups.com

~/.mailcap:

#text/html ; chromium %s
text/html ; firefox-esr -no-remote %s ; copiousoutput

Unfortunately it now prefers the .html version to the plaintext version.
I presume I need an alternative_order line.

-- hendrik

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mutt and html

[Hendrik Boom]

On Tue, Nov 02, 2021 at 03:50:07PM -0400, Hendrik Boom wrote:
> On Sat, Oct 30, 2021 at 04:13:31PM -0400, Hendrik Boom wrote:
> > Until upgraded from ascii to beowulf, HTML messages were tolerable.
> > Either they were obvious crap, in which case I just deeted them,
> > or they seemed like they were worth viewing, in which case they were 
> > usually html attachments, and I could seen the list of attachments by 
> > typeing v and selecting the html version -- in which case it would 
> > open for me in the chromium browser.
> > 
> > This stopped working after the upgrade to beowulf.
> > 
> > I did manage to reconfigure, telling it to use firefox-esr, but that 
> > didn't help much.  I connect to my server, the machine on which I run 
> > mutt, using ssh -X.  
> > So firefox on the server detects I already have a firefox browser 
> > on my laptop and proceeds to give the job of browsing the message to 
> > my laptop.
> > Makes sense, except that my laptop has no way to access the 
> > /tmp/mutt/somethingorother.html on the server. 
> > 
> > And I have not been able to get mutt to call chromium at all.
> > 
> > Any ideas?
> > 
> > -- hendrik
> > ___
> > Dng mailing list
> > Dng@lists.dyne.org
> > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 
> As far as I can tell, it's not seeing the information in my ~/.mailcao file.

Correction: it's really called ~/.mailcap, not ~/.mailcao

> When I put in an entry like
> 
> text/html ; echo foo
> 
> it still displays the html content of a an attachment as if it were 
> ordinatry plain text attachment, so i get to see all the html tags.
> 
> -- hendrik
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mutt and html

[Hendrik Boom]

On Sat, Oct 30, 2021 at 04:13:31PM -0400, Hendrik Boom wrote:
> Until upgraded from ascii to beowulf, HTML messages were tolerable.
> Either they were obvious crap, in which case I just deeted them,
> or they seemed like they were worth viewing, in which case they were 
> usually html attachments, and I could seen the list of attachments by 
> typeing v and selecting the html version -- in which case it would 
> open for me in the chromium browser.
> 
> This stopped working after the upgrade to beowulf.
> 
> I did manage to reconfigure, telling it to use firefox-esr, but that 
> didn't help much.  I connect to my server, the machine on which I run 
> mutt, using ssh -X.  
> So firefox on the server detects I already have a firefox browser 
> on my laptop and proceeds to give the job of browsing the message to 
> my laptop.
> Makes sense, except that my laptop has no way to access the 
> /tmp/mutt/somethingorother.html on the server. 
> 
> And I have not been able to get mutt to call chromium at all.
> 
> Any ideas?
> 
> -- hendrik
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

As far as I can tell, it's not seeing the information in my ~/.mailcao file.
When I put in an entry like

text/html ; echo foo

it still displays the html content of a an attachment as if it were 
ordinatry plain text attachment, so i get to see all the html tags.

-- hendrik

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] mutt and html

[Bob Proulx via Dng]

Hendrik Boom wrote:
> Until upgraded from ascii to beowulf, HTML messages were tolerable.
> Either they were obvious crap, in which case I just deeted them,
> or they seemed like they were worth viewing, in which case they were 
> usually html attachments, and I could seen the list of attachments by 
> typeing v and selecting the html version -- in which case it would 
> open for me in the chromium browser.
> 
> This stopped working after the upgrade to beowulf.

Until I read that you are connecting with ssh -X I thought that this
is almost certainly due to changes in /etc/mailcap handlers.  You
might review them on your system anyway.  It is possible they have
changed for you with the upgrade and that is why your html handling
has changed.

[[ Time to advocate for "etckeeper".  If that is installed then one can
look at the changes over time to any particular file in /etc.  This is
the command line way to view the "patches" made to a file.

cd /etc
git log -p mailcap | less

Meanwhile...  I normally just emacs the file, browse the version
history inside the Emacs git blame interface, C-x v g, and navigate
through previous and next versions.  I am sure there are many other
git version history browsers available. ]]

Here is a sampling of html handlers from my system, which will not be
typical since every system will have different ordering based upon the
ordering in which packages were installed and removed.  Packages add
and remove handlers as they are modified.  But useful for the idea.

$ grep html /etc/mailcap
text/html; /usr/bin/sensible-browser %s; description=HTML Text; 
nametemplate=%s.html
text/html; /usr/bin/firefox %s; description=HTML Text; test=test -n 
"$DISPLAY";  nametemplate=%s.html
text/html; /usr/bin/firefox-esr %s; description=HTML Text; test=test -n 
"$DISPLAY";  nametemplate=%s.html
text/html; /usr/local/bin/chromium %s; test=test -n "$DISPLAY"
application/xhtml_xml; /usr/local/bin/chromium %s; test=test -n "$DISPLAY"
text/html; /usr/bin/chromium %s; test=test -n "$DISPLAY"
application/xhtml_xml; /usr/bin/chromium %s; test=test -n "$DISPLAY"
text/html; dwb %s; test=test -n "$DISPLAY"
application/xhtml+xml; dwb %s; test=test -n "$DISPLAY"
text/html; midori --private %s; test=test -n "$DISPLAY"
application/xhtml+xml; midori --private %s; test=test -n "$DISPLAY"
text/html; /usr/bin/elinks -force-html %s; needsterminal; description=HTML 
Text; nametemplate=%s.html
text/html; /usr/bin/links %s; needsterminal; description=HTML Text; 
nametemplate=%s.html
text/html; /usr/bin/w3m -T text/html %s; needsterminal; description=HTML 
Text; nametemplate=%s.html
text/html; /usr/bin/elinks -force-html -dump %s; copiousoutput; 
description=HTML Text; nametemplate=%s.html
text/html; /usr/bin/links -dump %s; copiousoutput; description=HTML Text; 
nametemplate=%s.html
text/html; /usr/bin/lynx -force_html %s; needsterminal; description=HTML 
Text; nametemplate=%s.html
text/html; /usr/bin/w3m -I %{charset} -dump -T text/html %s; copiousoutput; 
description=HTML Text; nametemplate=%s.html
text/html; /usr/bin/html2text %s; copiousoutput; description=HTML Text
text/html; /usr/bin/lynx -dump -force_html %s; copiousoutput; 
description=HTML Text; nametemplate=%s.html

I keep a personalized ~/.mailcap file with most of the selections I
care about.  I then uncomment the one I want to be using at the
moment if I want to do something different and want to force my choice.

# text/html; /usr/bin/firefox %s; description=HTML Text; test=test -n 
"$DISPLAY";  nametemplate=%s.html
# text/html; /usr/bin/elinks -dump -dump-color-mode 3 %s; copiousoutput; 
description=HTML Text; nametemplate=%s.html
# text/html; /usr/bin/elinks -dump %s; copiousoutput; description=HTML 
Text; nametemplate=%s.html
text/html; /usr/bin/links -dump %s; copiousoutput; description=HTML Text; 
nametemplate=%s.html
# text/html; /usr/local/bin/iceweasel '%s'; description=HTML Text; 
test=test -n "$DISPLAY";  nametemplate=%s.html
# text/html; /usr/bin/lynx -force_html %s; needsterminal; description=HTML 
Text; nametemplate=%s.html
# text/html; /usr/bin/lynx -dump -force_html %s; copiousoutput; 
description=HTML Text; nametemplate=%s.html
# text/html; /usr/bin/w3m -no-mouse -T text/html %s; needsterminal; 
description=HTML Text; nametemplate=%s.html

Currently I am forcing "links -dump" rendering as that is doing pretty
well for the types of html mail I am receiving at the moment.  For
most html mail I am receiving the text rendering of the message is
more than sufficient.  There are hard cases of fluff and glitter
though.  If I have a problem I will simply edit that ~/.mailcap file
and change the selection and try one of the others viewers.  Some work
better than others.

If I want to open the attachment in a real graphical browser then I
perform a manual action.  I 'v'iew the MIME parts, 

Re: [DNG] snetaid debs...

[aitor]

Hi,

On 1/11/21 19:48, aitor wrote:


The code of simple-netaid is ready to use:


- libnetaid: the shared library
https://gitea.devuan.dev/aitor_czr/libnetaid/src/branch/gbp-master  

- snetaid: the daemon

https://gitea.devuan.dev/aitor_czr/snetaid/src/branch/gbp-master  

- simple-netaid-cdk: the ncurses interface

https://gitea.devuan.dev/aitor_czr/simple-netaid-cdk/src/branch/gbp-master  

Packages will be available in a few hours...
Sorry for the delay, and thanks for your interest in the project :)
Cheers,
Aitor.


Done:

https://www.gnuinos.org/simple-netaid/  

Packages have been tested in a fresh install of devuan chimaera. The dependency 
on libpstat (Jude Nelson)
might be replaced with pwdx (maybe...) Please, don't forget to configure your 
/etc/network/interfaces properly.
Next packages will consist of a status icon in both Gtk and Qt. I have them 
working.

Shortly i'll test simple-netaid in other distributions. Specially, I look 
forward to build packages for Void Linux,
including also ifupdown -available in github for other distros, de(b|v)uan 
aside.

Feedback is welcome.

Cheers,

Aitor.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng