From: Ihor Radchenko <email@example.com>
To: Max Nikulin <firstname.lastname@example.org>
Subject: Re: [PATCH] org.el: Fix percent substitutions in `org-open-file'
Date: Sat, 03 Sep 2022 16:26:37 +0800 [thread overview]
Message-ID: <87o7vw983m.fsf@localhost> (raw)
Max Nikulin <email@example.com> writes:
>>> + (\"\\\\.pdf::\\\\(.+\\\\)\\\\\\='\" . \"okular file://%s\\\\\\\\#%1\")
>>> + ;; No location within the file, optionally followed by \"::\",
>>> + ;; e.g. <file:///usr/share/doc/bash/bashref.pdf>.
>>> + (\"\\\\.pdf\\\\(?:::\\\\)?\\\\\\='\" . \"okular %s\")
>> This is a nice set of examples, but it probably does not belong to this
>> docstring. I'd rather see this in `org-file-apps' docstring or even in
>> the manual.
> I thought on this and I do not think it should be added to the manual.
> Instead a set of hooks should be defined for popular PDF viewers:
> evince, zathura, xpdf, firefox, chromium & Co, etc. Such hook injects a
> number of supported `org-file-apps' records and users may add suitable
> hook to e.g. (with-eval-after-load 'org (push ...)). It may be
> implemented as a dedicated package org-pdf-viewers.el. The only problems
> is that adding entries programmatically breaks easy customization
> interface for `org-file-apps'. Currently there is the same issue with
> `org-link-parameters' that is a defcustom variables with entries added
> by various org extensions.
We may alter the :type specifier in `org-file-apps' to something like
`org-file-apps-presets' will then contain :type specs for some common
file types and the apps. The variable can be easily populated by
third-party packages as well.
> I added the example with hope to better explain the purpose of this
I do not think that it is needed in the `org--open-file-format-command'
docstring. If you wish, it would be better to add examples of the
arguments and return values of `org--open-file-format-command' instead
of showing `org-file-apps' examples.
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-09-03 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 16:08 greedy substitution in org-open-file Maxim Nikulin
2021-02-12 7:16 ` Kyle Meyer
2021-02-12 16:46 ` Maxim Nikulin
2021-02-13 4:38 ` Kyle Meyer
2021-02-15 17:04 ` Maxim Nikulin
2021-03-03 12:47 ` Maxim Nikulin
2021-03-21 12:36 ` Maxim Nikulin
2022-08-27 17:20 ` [PATCH] org.el: Fix percent substitutions in `org-open-file' Max Nikulin
2022-09-02 12:08 ` Ihor Radchenko
2022-09-02 15:41 ` Max Nikulin
2022-09-03 8:26 ` Ihor Radchenko [this message]
2022-09-04 12:16 ` [PATCH v2] " Max Nikulin
2022-09-05 5:46 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).