From: Matt Price <moptop99@gmail.com>
To: Henrik Frisk <frisk.h@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: citar--library-file-action
Date: Tue, 25 Oct 2022 16:47:21 -0400 [thread overview]
Message-ID: <CAN_Dec84WHMN=ZamT3dbFVvfCE9KqK8XLk-a+Xbhk9ZfDgrd2Q@mail.gmail.com> (raw)
In-Reply-To: <CAN_Dec8tNKbjJQKjKemiAPbFanNAfomns2h9U-noiyVW5Nc5cw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Bruce will know better than me!!!
On Tue, Oct 25, 2022 at 4:46 PM Matt Price <moptop99@gmail.com> wrote:
> I’d look at the current function definition to be sure (C-h f
> citar—library-file-action), but open is the standard macOS command for
> opening files. The Linux equivalent is xdg-open. My guess is that somehow
> you’ve told citar or org or emacs to use open for these links. Or it’s
> possible that the citar devs accidentally hard coded open into the
> function.
>
> On Tue, Oct 25, 2022 at 4:27 PM Henrik Frisk <frisk.h@gmail.com> wrote:
>
>> Hi,
>>
>> After updating a bunch of packages I'm getting this error message when I
>> try to open an associated file via a reference:
>>
>> [cite:@key]
>>
>> Before it was working fine via emark either by clicking on the reference
>> or by running embark-act on it. Now I get this instead:
>>
>> citar--library-file-action: Symbol’s function definition is void: open
>>
>> Any suggestions?
>>
>> /Henrik
>>
>>
[-- Attachment #2: Type: text/html, Size: 1690 bytes --]
prev parent reply other threads:[~2022-10-25 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 20:22 citar--library-file-action Henrik Frisk
2022-10-25 20:42 ` citar--library-file-action Bruce D'Arcus
2022-10-29 23:02 ` citar--library-file-action Henrik Frisk
2022-10-25 20:46 ` citar--library-file-action Matt Price
2022-10-25 20:47 ` Matt Price [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='CAN_Dec84WHMN=ZamT3dbFVvfCE9KqK8XLk-a+Xbhk9ZfDgrd2Q@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=frisk.h@gmail.com \
/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).