From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Possible bug: Can not search for text in links - only description
Date: Mon, 23 Mar 2015 08:57:36 -0400 [thread overview]
Message-ID: <CAA6UvuGqx3-fE5GVk8S4D48kiKtEm52YVtdfxsUcGTcYeK42=w@mail.gmail.com> (raw)
In-Reply-To: <m21tkf2878.fsf@krugs.de>
On Mon, Mar 23, 2015 at 8:45 AM, Rainer M Krug <Rainer@krugs.de> wrote:
> First I must say it makes sense to give the error message, although I
> was quite surprised.
>
> But the message should contain a string one can easily search for. And I
> guess the most used search function is C-s I think the message should be
> changes to the description of the link and the target in brackets. This
> would make searching easier.
FWIW, I completely agree. I would be happy to provide a patch for
this, but I'm not sure how to get the link's description inside
org-export-resolve-fuzzy-link. AFAICT, the `link' object passed to
this function has properties as determined by
`org-element-link-parser'. The properties listed in the docstring
don't include the description.
Could anyone provide a hint on how to get the link's description?
Regards,
Jake
prev parent reply other threads:[~2015-03-23 12:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 13:44 Possible bug: Can not search for text in links - only description Rainer M Krug
2015-03-20 14:59 ` Richard Lawrence
2015-03-20 15:20 ` Sebastien Vauban
2015-03-21 23:34 ` Alexis
2015-03-20 15:38 ` Jacob Gerlach
2015-03-20 16:50 ` Ken Mankoff
2015-03-20 18:06 ` Charles C. Berry
2015-03-22 0:08 ` Jacob Gerlach
2015-03-23 12:42 ` Rainer M Krug
2015-03-23 14:37 ` Achim Gratz
2015-03-23 16:56 ` Rainer M Krug
2015-03-23 12:40 ` Rainer M Krug
2015-03-20 17:53 ` Samuel Wales
2015-03-20 17:57 ` Jacob Gerlach
2015-03-31 13:46 ` Ken Mankoff
2015-03-31 20:07 ` Samuel Wales
2015-03-21 23:45 ` Randomcoder
2015-03-23 12:45 ` Rainer M Krug
2015-03-23 12:57 ` Jacob Gerlach [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='CAA6UvuGqx3-fE5GVk8S4D48kiKtEm52YVtdfxsUcGTcYeK42=w@mail.gmail.com' \
--to=jacobgerlach@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).