Skip to content
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

Feature: Add a tree view for the mime parts of a message #862

Closed
lucc opened this issue Apr 6, 2016 · 1 comment
Closed

Feature: Add a tree view for the mime parts of a message #862

lucc opened this issue Apr 6, 2016 · 1 comment

Comments

@lucc
Copy link
Collaborator

lucc commented Apr 6, 2016

This is a feature request (or discussion) for a new alternative way to display a message in thread buffers. It could be accessible with a new command for thread buffers togglemimetree which should be used similar to togglesource or toggleheaders.

If activated the mime tree of the message should be displayed below the currently displayed header lines (so this command should work independently of toggleheaders). Each line should correspond to one mime part and the lines should be indented like the messages in thread view to indicate the tree structure.

Some commands are of interest when viewing the mime tree:

  • something like select to display a rendered version of the current mime part (either inside the tree or in a new buffer)
  • something like select currently works on attachments to open mime parts with external tools
  • something like pipeto to pipe only this mime part to an external shell command
  • something like save to save only this mime part to a file
  • others?

This feature is inspired by the view-attachments of mutt. In mutt it looks like this:
view-attachments

@lucc lucc changed the title Fearure: Add a tree view for the mime parts of a message Feature: Add a tree view for the mime parts of a message Apr 6, 2016
ryneeverett added a commit to ryneeverett/alot that referenced this issue Mar 13, 2020
It is suggested in pazz#862:

> something like select to display a rendered version of the current mime part
> (either inside the tree or in a new buffer)

I played around with these options before arriving at the current
behavior. Adding the mime part content to the mimetree seemed made for a
very busy/over-nested screen and didn't seem all that useful. Likewise
opening in another buffer doesn't seem useful and might need a new
Buffer subclass in order to be well labeled.

The `select` behavior I ended up going with was to change the mime part
chosen by default in the Message itself. This should make implementing
other commands (e.g. pipeto) on the mime parts trivial.

I took `select` a step further by also having it conveniently togglemimetree
off. I can't think of any use case for remaining in the mimetree view after
making a selection.
ryneeverett added a commit to ryneeverett/alot that referenced this issue Mar 13, 2020
It is suggested in pazz#862:

> something like select to display a rendered version of the current mime part
> (either inside the tree or in a new buffer)

I played around with these options before arriving at the current
behavior. Adding the mime part content to the mimetree seemed made for a
very busy/over-nested screen and didn't seem all that useful. Likewise
opening in another buffer doesn't seem useful and might need a new
Buffer subclass in order to be well labeled.

The `select` behavior I ended up going with was to change the mime part
chosen by default in the Message itself. This should make implementing
other commands (e.g. pipeto) on the mime parts trivial.

I took `select` a step further by also having it conveniently togglemimetree
off. I can't think of any use case for remaining in the mimetree view after
making a selection.
ryneeverett added a commit to ryneeverett/alot that referenced this issue Mar 13, 2020
It is suggested in pazz#862:

> something like select to display a rendered version of the current mime part
> (either inside the tree or in a new buffer)

I played around with these options before arriving at the current
behavior. Adding the mime part content to the mimetree seemed made for a
very busy/over-nested screen and didn't seem all that useful. Likewise
opening in another buffer doesn't seem useful and might need a new
Buffer subclass in order to be well labeled.

The `select` behavior I ended up going with was to change the mime part
chosen by default in the Message itself. This should make implementing
other commands (e.g. pipeto) on the mime parts trivial.

I took `select` a step further by also having it conveniently togglemimetree
off. I can't think of any use case for remaining in the mimetree view after
making a selection.
ryneeverett added a commit to ryneeverett/alot that referenced this issue Mar 23, 2020
It is suggested in pazz#862:

> something like select to display a rendered version of the current mime part
> (either inside the tree or in a new buffer)

I played around with these options before arriving at the current
behavior. Adding the mime part content to the mimetree seemed made for a
very busy/over-nested screen and didn't seem all that useful. Likewise
opening in another buffer doesn't seem useful and might need a new
Buffer subclass in order to be well labeled.

The `select` behavior I ended up going with was to change the mime part
chosen by default in the Message itself. This should make implementing
other commands (e.g. pipeto) on the mime parts trivial.

I took `select` a step further by also having it conveniently togglemimetree
off. I can't think of any use case for remaining in the mimetree view after
making a selection.
pazz pushed a commit that referenced this issue May 6, 2020
It is suggested in #862:

> something like select to display a rendered version of the current mime part
> (either inside the tree or in a new buffer)

I played around with these options before arriving at the current
behavior. Adding the mime part content to the mimetree seemed made for a
very busy/over-nested screen and didn't seem all that useful. Likewise
opening in another buffer doesn't seem useful and might need a new
Buffer subclass in order to be well labeled.

The `select` behavior I ended up going with was to change the mime part
chosen by default in the Message itself. This should make implementing
other commands (e.g. pipeto) on the mime parts trivial.

I took `select` a step further by also having it conveniently togglemimetree
off. I can't think of any use case for remaining in the mimetree view after
making a selection.
@meskio
Copy link
Contributor

meskio commented Jun 1, 2020

I belive this issue has being solved by #1480. Isn't it? Or is there still some parts still missing?

@lucc lucc closed this as completed Jun 1, 2020
GuillaumeSeren pushed a commit to GuillaumeSeren/alot that referenced this issue Oct 3, 2021
It is suggested in pazz#862:

> something like select to display a rendered version of the current mime part
> (either inside the tree or in a new buffer)

I played around with these options before arriving at the current
behavior. Adding the mime part content to the mimetree seemed made for a
very busy/over-nested screen and didn't seem all that useful. Likewise
opening in another buffer doesn't seem useful and might need a new
Buffer subclass in order to be well labeled.

The `select` behavior I ended up going with was to change the mime part
chosen by default in the Message itself. This should make implementing
other commands (e.g. pipeto) on the mime parts trivial.

I took `select` a step further by also having it conveniently togglemimetree
off. I can't think of any use case for remaining in the mimetree view after
making a selection.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants