From: James Harkins <jamshark70@zoho.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: ODT export --> opening in Okular?
Date: Wed, 12 Dec 2018 08:41:35 +0800 [thread overview]
Message-ID: <1679fdc9f6a.102fa0ca058102.5578147846648149352@zoho.com> (raw)
In-Reply-To: <mailman.79.1544461215.14495.emacs-orgmode@gnu.org>
---- On Tue, 11 Dec 2018 01:00:15 +0800 <emacs-orgmode-request@gnu.org> 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. Apparently installing Okular adds this bit of silliness into /etc/mailcap:
application/vnd.oasis.opendocument.text; okular %s --icon okular -caption Okular; test=test -n "$DISPLAY"
... which I find now has also been reported to Debian as a bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857443
I still think it's insane, but at least now it's clear where the insanity lies: with Okular's inflated sense of self-importance :D
But, what I still don't understand is, after adding an ODT entry to org-file-apps, why did org revert to querying mailcap...?
Value: ((auto-mode . emacs)
("\\.mm\\'" . default)
("\\.x?html?\\'" . "/usr/bin/firefox %s")
("\\.odt\\'" . "/usr/bin/libreoffice6.0 %s")
("\\.pdf\\'" . "/usr/bin/okular %s"))
Original value was
((auto-mode . emacs)
("\\.mm\\'" . default)
("\\.x?html?\\'" . default)
("\\.pdf\\'" . default))
... this has exactly zero effect. Org ignores the odt line here, where I would expect an org-specific preference setting to override the system default.
hjh
next parent reply other threads:[~2018-12-12 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.79.1544461215.14495.emacs-orgmode@gnu.org>
2018-12-12 0:41 ` James Harkins [this message]
2018-12-09 7:18 ODT export --> opening in Okular? James Harkins
2018-12-09 23:25 ` briangpowell
2018-12-10 1:45 ` James Harkins
2018-12-10 2:20 ` Ken Mankoff
2018-12-10 16:08 ` Eric S Fraga
2018-12-10 16:41 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1679fdc9f6a.102fa0ca058102.5578147846648149352@zoho.com \
--to=jamshark70@zoho.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).