Re: Libreoffice document can't open by mailcap entry
On Wed, Jan 10, 2018 at 09:55:12AM -0200, Marcelo Laia wrote: > On 10/01/18 at 02:05, David Woodfall wrote: > > > > What does mutt display the mimetype as? > > I found the problem! It was in the file name. > > File named "Assunto 27 - FORMULA.odt" dosen't open, but, file named as > "Assunto27-FORMULA.odt" showed up in libreoffice. > > I hope thies could help someone. > > Thanks. > For file names with spaces, you could try changing nametemplate=%s.odt to nametemplate='%s'.odt (notice quotation marks) in the mailcap entry: application/vnd.oasis.opendocument.text; libreoffice '%s'; edit=libreoffice '%s'; test=test -n "$DISPLAY"; description="OpenDocument Text Document"; nametemplate='%s'.odt -- Jason
Re: Libreoffice document can't open by mailcap entry
On 10/01/18 at 02:05, David Woodfall wrote: > > What does mutt display the mimetype as? I found the problem! It was in the file name. File named "Assunto 27 - FORMULA.odt" dosen't open, but, file named as "Assunto27-FORMULA.odt" showed up in libreoffice. I hope thies could help someone. Thanks. -- Marcelo
Re: Libreoffice document can't open by mailcap entry
Hi, I have the follow entry in mailcap: application/vnd.oasis.opendocument.text; libreoffice '%s'; edit=libreoffice '%s'; test=test -n "$DISPLAY"; description="OpenDocument Text Document"; nametemplate=%s.odt So, I attach a document and select it. I chose enter key to see there content. After a upgrade in my Debian system the file isant showed anymore. Someone could reproduce it and suggest a workaround? Thanks -- Marcelo What does mutt display the mimetype as?
Libreoffice document can't open by mailcap entry
Hi, I have the follow entry in mailcap: application/vnd.oasis.opendocument.text; libreoffice '%s'; edit=libreoffice '%s'; test=test -n "$DISPLAY"; description="OpenDocument Text Document"; nametemplate=%s.odt So, I attach a document and select it. I chose enter key to see there content. After a upgrade in my Debian system the file isant showed anymore. Someone could reproduce it and suggest a workaround? Thanks -- Marcelo