emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Frankie Y. Liu" <frankie.y.liu@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-file-apps regex matching against path not link
Date: Sat, 14 Apr 2018 07:05:54 -0700	[thread overview]
Message-ID: <CAD+Roiyvz4VShLXA2s3KWsaYNeHkRXaPP6orgNL8qJWuR9D7Mw@mail.gmail.com> (raw)
In-Reply-To: <87bmemp724.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Hi Nicolas,

Sorry I mistyped in the message, I did have two colons when trying it out.
I will look into the
function you pointed out.

When you said you cannot reproduce it, does that mean it works/matches for
you?

I am using Emacs 25.3.5 and org-20180226

-f

On Sat, Apr 14, 2018 at 12:42 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> "Frankie Y. Liu" <frankie.y.liu@gmail.com> writes:
>
> > For:
> >
> > \\.pdf:\\([0-9]+\\)\\'
>
> You forgot a colon.
>
> > [0-9]+ vs \d+ same issue, since the path not the link is being
> > matched.
> >
> > Example:
> > file:foo.pdf::1 will be matching on file:foo.pdf and the ::1 is
> > dropped.
>
>
> I cannot reproduce it here. The function
> `org-file-apps-entry-match-against-dlink-p' is responsible for deciding
> if a link needs to be matched in full, or not.
>
> Regards,
>
> --
> Nicolas Goaziou                                                0x80A93738
>

[-- Attachment #2: Type: text/html, Size: 1662 bytes --]

  reply	other threads:[~2018-04-14 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 19:22 org-file-apps regex matching against path not link Frankie Y. Liu
2018-04-12 19:38 ` Nicolas Goaziou
2018-04-12 22:41   ` Frankie Y. Liu
2018-04-14  7:42     ` Nicolas Goaziou
2018-04-14 14:05       ` Frankie Y. Liu [this message]
2018-04-14 14:29         ` Nicolas Goaziou

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=CAD+Roiyvz4VShLXA2s3KWsaYNeHkRXaPP6orgNL8qJWuR9D7Mw@mail.gmail.com \
    --to=frankie.y.liu@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).