From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] org-open-file: ignores browse-url settings
Date: Tue, 01 Sep 2015 17:32:50 +0200 [thread overview]
Message-ID: <87bndm2lzx.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87vbbyp0kr.fsf@gmx.us> (rasmus@gmx.us's message of "Sat, 29 Aug 2015 17:37:56 +0200")
Hello,
Rasmus <rasmus@gmx.us> writes:
> From Emacs-devel:
>
> From: raman@google.com
> Subject: org-open-file: ignores browse-url settings
> Date: the 21st of August 2015 at 20:07
> Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/189056>
>
> Function org-open-file uses customization variable org-file-apps to
> decide how to open a file.
> Unfortunately it's also making it difficult / impossible to set it up
> so that org files exported to HTML open in Emacs using EWW ---
(add-to-list 'org-file-apps '("\\.x?html?\\'" . (eww-open-file file)))
should do the trick.
> -specifically: the customization interface for org-file-apps claims to
> let you provide a custom lisp form which in principle should let one
> specify browse-url -- (admittedly convoluted ) but even that fails to
> work -- mostly because the documentation is somewhat light with
> respect to showing how one gets ones hands on the matched link.
We can improve documentation.
> My personal opinion would be to get rid of org-file-apps. Opening files
> correctly is the job of either Emacs or the OS.
I'm not sure about it.
Org can divert from Emacs when it comes to what to do with files. You
may want to view it from Org but edit it from Emacs. The OS doesn't know
about Lisp.
Note that you can force `org-open-file' to open it with Emacs,
effectively ignoring `org-file-apps' altogether.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2015-09-01 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 15:37 [bug] org-open-file: ignores browse-url settings Rasmus
2015-09-01 15:32 ` Nicolas Goaziou [this message]
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=87bndm2lzx.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).