-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open attachment with a custom command like xdg-open #1494
Comments
Agreed. |
I can add such command but currently opening attachments is done by the "select" command, which allows the use of the same keybinding to perform this action and others. Is it possible to bind the same key a new OpenAttachmentCommand? |
Oh right, I overlooked that this command is not exposed to the alot ui directly.
In fact, we could keep `select` as is and add another command `open` ?
which would use OpenAttachmentCommand directly. Perhaps this can even be done by simply adding a new decorator around that class...
Quoting Notkea (2020-05-08 20:29:05)
… I can add such command but currently opening attachments is done by the
"select" command, which allows the use of the same keybinding to perform
this action and others. Is it possible to bind the same key a new
OpenAttachmentCommand?
—
You are receiving this because you commented.
Reply to this email directly, [1]view it on GitHub, or [2]unsubscribe.
References
Visible links
1. #1494 (comment)
2. https://github.com/notifications/unsubscribe-auth/AAEZNZ33MK554W5JCXQZPJDRQRMQDANCNFSM4MKHZOLQ
|
But it would be weird to have two commands doing the same thing in some cases. |
Nevermind, it actually makes sense to have another command, similar to "pipeto". I'll prepare a patch for this. |
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
This allows the user to open an attachment file with a program of their choice. GitHub: closes pazz#1494
Is your feature request related to a problem? Please describe.
It'd be nice to let xdg-open decide which application should be used when opening some attachment in alot.
Currently, alot only tries to use the
~/.mailcap
mapping, which has to be manually kept in sync with other MIME databases (mimeapps.list, desktop entries, …).Describe the solution you'd like
An option could be added to delegate the application choice to another program, such as xdg-open.
Describe alternatives you've considered
It's not possible to add a global fallback in .mailcap such as
*/*; xdg-open "%s"
because*/*
isn't a valid wildcard as per RFC1524 and isn't accepted by the Python lib.Additional context
Since b1c93c4, having
text/*; xdg-open "%s"
in .mailcap causes all text messages, not only attachments, to be opened externally. It's not possible to keep that entry to open log files attachments for instance.The text was updated successfully, but these errors were encountered: