emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@zoho.com>
To: briangpowell <briangpowellms@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: ODT export --> opening in Okular?
Date: Mon, 10 Dec 2018 09:45:35 +0800	[thread overview]
Message-ID: <16795ca7e62.123019e8323779.2065181443559693375@zoho.com> (raw)
In-Reply-To: <CAFm0skHy3TVpkiunAGJ7Tfz7HxQ+4cVN5fFZ5YvyDeSeiQzF6Q@mail.gmail.com>

---- On Mon, 10 Dec 2018 07:25:13 +0800 briangpowell <briangpowellms@gmail.com> 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 you but by your chosen operating system package manager

Nope.

$ libreoffice --help
The program 'libreoffice' is currently not installed.

(I installed libreoffice by downloading from their website, not using Ubuntu packages -- because I had some issues with it a while back and the advice from their user community is always, don't use system-bundled packages because they are out of date.)

In any case, it doesn't make a difference: org still insists on issuing the command for okular.

I also tried the full path to the binary /usr/bin/libreoffice6.0 -- still exports to Okular.

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.

org-open-file seems to be a rather complex function. I can't make heads or tails of it. If I had to guess, I would suppose that it has some fallback position that doesn't depend on org configuration variables.

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).

hjh

  reply	other threads:[~2018-12-10  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2018-12-10  2:20     ` Ken Mankoff
2018-12-10 16:08       ` Eric S Fraga
2018-12-10 16:41     ` Nick Dokos
     [not found] <mailman.79.1544461215.14495.emacs-orgmode@gnu.org>
2018-12-12  0:41 ` James Harkins

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=16795ca7e62.123019e8323779.2065181443559693375@zoho.com \
    --to=jamshark70@zoho.com \
    --cc=briangpowellms@gmail.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).