emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: [ANSWERED] Re: [BUG] (org-element-context) on some link does not return search-option correctly
Date: Sun, 21 Nov 2021 16:15:22 +0800	[thread overview]
Message-ID: <PAXPR08MB66403A9C8FD0029B550CF81CA39E9@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87mtlzui3y.fsf@localhost>

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


Ihor Radchenko <yantar92@gmail.com> writes:

> "Christopher M. Miles" <numbchild@gmail.com> writes:
>
>> When I put point on an custom org link:
>>
>> #+begin_src org
>> [[pdf:~/Org/Wiki/Computer Technology/Programming/Programming Languages/Clojure/data/Books/Clojure
>> 经典实例.pdf::40++0.00][Clojure经典实例.pdf: Page 40]]
>> #+end_src
>> ...
>> You can see the result ~:search-option nil~. It suppose to be ~40++0.00~.
>
> AFAIK, only file: links are parsed to have search-option.
>
> If you want a custom link type to have search-option property, you
> should use link abbrev.

I see. Thanks, I will use other code way to parse the :search-option value.

-- 
[ stardiviner ]
       I try to make every word tell the meaning that I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2021-11-21  8:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20 11:13 [BUG] (org-element-context) on some link does not return search-option correctly Christopher M. Miles
2021-11-20 12:28 ` Ihor Radchenko
2021-11-21  8:15   ` Christopher M. Miles [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=PAXPR08MB66403A9C8FD0029B550CF81CA39E9@PAXPR08MB6640.eurprd08.prod.outlook.com \
    --to=numbchild@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).