On Tue, 11 Dec 2018 01:00:15 +0800 wrote
> Check your ~/.mailcap and/or /etc/mailcap file as well: there are indeed
> many twisty passages through org-open-file, so you may end up calling
> whatever the system has set up (correctly or not).
> Nick
Aha, that was the answer.
James Harkins writes:
> ...
> As a final test, I deleted both the PDF and ODT entries from
> org-file-apps -- so that there is absolutely no reference in any org
> code file or variable to okular -- and it is *still* opening the
> exported ODT in okular! Which strikes me as insane.
>
>
On Sunday, 9 Dec 2018 at 18:20, Ken Mankoff wrote:
> On 2018-12-09 at 17:45 -0800, James Harkins wrote:
>> Anyway, the solution for now, as I'm under some time pressure, is to
>> declare that ODT export is broken on my system until I can scrape
>> together some time to upgrade org. PDF export is
On 2018-12-09 at 17:45 -0800, James Harkins wrote:
> Anyway, the solution for now, as I'm under some time pressure, is to
> declare that ODT export is broken on my system until I can scrape
> together some time to upgrade org. PDF export is actually OK for now
> (and working fine).
But export
On Mon, 10 Dec 2018 07:25:13 +0800 briangpowell
wrote
> * Suggest you try changing this:
>
> ("\\.odt\\'" . "libreoffice6.0 %s"
> * To this instead:
>
> ("\\.odt\\'" . "libreoffice %s"
> --since "libreoffice6.0" is a specific link that is subject to change--not
> only by
* Suggest you try changing this:
("\\.odt\\'" . "libreoffice6.0 %s"
* To this instead:
("\\.odt\\'" . "libreoffice %s"
--since "libreoffice6.0" is a specific link that is subject to change--not
only by you but by your chosen operating system package manager
Unless of course, you
Hi,
I realize I'm running an older version of org-mode (8.3.3), but things are
working for me generally and I'm not in a position to monkey around with my
environment right now.
Anyway, something strange. A few months ago, I was able to export to ODT and
the file would open in LibreOffice.
