With html parts, I like the w3m-style filtering for the terminal, but sometimes I'd like to view in a browser. When I do that, I prefer to use a dumber browser than my system browser, socksify it, and add the flags that disable scripts/caching/cookies/etc.
Am I overlooking a way to achieve this with the built-ins? If not, would you welcome a patch to add this feature?
ps> Doing this with :pipe, sh, & binds.conf at the moment, but it's kind of awkward. Would also be nice if pipe/exec could expand environment variables (or $HOME at least).
What kind of option did you have in mind?
Basically a riff on [filters], but for opening things. If not specified for a given mime type, revert to present xdg-open-style functionality. I think tempfiles would be better than piping for this particular feature, since a lot of programs don't have a simple way of pulling input from stdin (like browsers). That's some of the awkwardness of what I'm already doing--making a shell script just to snag stdin to a file & clean up afterward.
And having printf-style substitutions available (at least full path to file [single vs. multiple like xdg .desktop spec]) would also be a plus, since with a few strange programs the last parameter isn't necessarily the input.
And of course, carry whatever we do in the config file over to the :open command (probably has to be a new variation of it, since the original :open passed flags) for specifying the opener as well.
This ticket should also concern
:open-link
in some manner.
@q3cpma :open-link is not in my man doc. Is that for opening URLs?
@rjarry: as far as implementation goes, I think something like
.mailcap
, but for openers instead of filters--specifying mime type, command, flags (like %s & %t inman 5 mailcap
). Unspecified mime types revert toxdg-open
. How does that sound?
On Thu Sep 22, 2022 at 3:26 AM CEST, ~bourgeois_bear wrote:
@q3cpma :open-link is not in my man doc. Is that for opening URLs?
@rjarry: as far as implementation goes, I think something like
.mailcap
, but for openers instead of filters--specifying mime type, command, flags (like %s & %t inman 5 mailcap
). Unspecified mime types revert toxdg-open
. How does that sound?-- View on the web: https://todo.sr.ht/~rjarry/aerc/64#event-206643
Yeah, it's missing from the main man page, but aerc-config(5) does mention it.
I may have misunderstood your need but it looks like you should use
:open
https://git.sr.ht/~rjarry/aerc/tree/0.12.0/item/doc/aerc.1.scd#L390
- Scratch that... I had fogotten that you already tried
:open
.
@~q3cpma: re: open-link:
So if I have a
open-overrides
file in my aerc config dir with the following contents:text/html; /path/to/preferred/browser %s
Both
:open
and:open-link
could use that command, while if that file is missing, or exists without atext/html
line, both will revert to xdg-open functionality. I believe in the average case, this would be the most convenient approach, but I'm almost certain someone will want different behavior between:open
and:open-link
, so ultimately, I think overriding the:open-link
provider should be a one-liner in the primary config file, and have myopen-overrides
file only apply to:open
.
And come to think of it, a new command for specifying the opener on an as-needed basis. Something like:
:open-ex firefox %s
If classic
:open
weren't a direct flags pass, we could just add a flag to it for specifying the opener. But doing so at this point might break things for some people, so that's why I'm suggesting a new command.
Robin Jarry referenced this ticket in commit 45bff88.