Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Attachment type doesn't open anymore (Mac/OSX)

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 1 Hecha
  • Mbohovái ipaháva cyberpi

more options

Hello,

Some days ago I set the file type ".java" to always open with Emacs in Thunderbird 91.5.1. Since then, when I double click on a java attachment or try to use the "Open" context menu, absolutely nothing happens. For the other file types it works normally. I can save the attachment and open it from the finder, but that's rather annoying...

My handlers.json looks normal :

{"defaultHandlersVersion":{},"mimeTypes":{"application/pdf":{"action":3,"extensions":["pdf"]},"image/jpeg":{"action":4,"ask":true,"extensions":["jpg","jpeg","jpe","jfif","pjpeg","pjp"]},"application/vnd.openxmlformats-officedocument.wordprocessingml.document":{"action":4,"ask":true,"extensions":["docx"]},"image/png":{"action":4,"ask":true,"extensions":["png"]},"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet":{"action":4,"ask":true,"extensions":["xlsx"]},"text/plain":{"action":2,"handlers":[{"name":"Emacs","path":"/Applications/Emacs.app"}],"extensions":["txt","text","asc"],"ask":true},"text/markdown":{"action":2,"ask":true,"handlers":[{"name":"Firefox","path":"/Applications/Firefox.app"},{"name":"Emacs","path":"/Applications/Emacs.app"}]}},"schemes":{}}

So I suspect the "open action" is hidden elsewhere - but where ?

Thanks !

Hello, Some days ago I set the file type ".java" to always open with Emacs in Thunderbird 91.5.1. Since then, when I double click on a java attachment or try to use the "Open" context menu, absolutely nothing happens. For the other file types it works normally. I can save the attachment and open it from the finder, but that's rather annoying... My handlers.json looks normal : {"defaultHandlersVersion":{},"mimeTypes":{"application/pdf":{"action":3,"extensions":["pdf"]},"image/jpeg":{"action":4,"ask":true,"extensions":["jpg","jpeg","jpe","jfif","pjpeg","pjp"]},"application/vnd.openxmlformats-officedocument.wordprocessingml.document":{"action":4,"ask":true,"extensions":["docx"]},"image/png":{"action":4,"ask":true,"extensions":["png"]},"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet":{"action":4,"ask":true,"extensions":["xlsx"]},"text/plain":{"action":2,"handlers":[{"name":"Emacs","path":"/Applications/Emacs.app"}],"extensions":["txt","text","asc"],"ask":true},"text/markdown":{"action":2,"ask":true,"handlers":[{"name":"Firefox","path":"/Applications/Firefox.app"},{"name":"Emacs","path":"/Applications/Emacs.app"}]}},"schemes":{}} So I suspect the "open action" is hidden elsewhere - but where ? Thanks !

Opaite Mbohovái (2)

more options

I have no idea what my handlers looks like, that is because there is no user editable content in it. So why look at it? There is a user interface to determine what is what in media types.

I am however pretty sure your emacs entry is missing a media type it related to, just comparing it to the Firefox entry before it.

The media types registered with IANA containing Java in their name are. javascript application/javascript [RFC4329] javascript (OBSOLETED in favor of application/javascript) text/javascript [RFC4329] and vnd.jcp.javame.midlet-rms application/vnd.jcp.javame.midlet-rms [Mikhail_Gorshenev]

So I guess to work out what the issue is, perhaps look in the message source (ctrl+U) and identify which of those media types are used to describe the attachment you are trying to open in Emacs.

My personal guess is this is another example of shoddy encoding by a web script/router/IOT Device. Either application/text or application/octet-stream are fairly common incorrect encodings of content. But without knowing what is being used, suggesting a workaround is really not possible.

more options

Hello.

Thank you for your answer.

What I see in the message source is:

Content-Type: text/plain; charset="UTF-8"; name="Test.java" Content-Disposition: attachment; filename="Test.java" Content-Transfer-Encoding: base64

And in my Thunderbird preferences I have the following settings (that come from handlers.json if I understood well).

Any idea ?