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: Fri, 20 Mar 2015 11:38:24 -0400 [thread overview]
Message-ID: <CAA6UvuEHsktko6ezN-hj5ruS=MZ70_xyoaTYXES3cSmwYZmiCQ@mail.gmail.com> (raw)
In-Reply-To: <m2lhir237m.fsf@krugs.de>
On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug <Rainer@krugs.de> wrote:
> Hi
>
> I got an error as follow when I tried to export:
>
> ,----
> | org-babel-exp process R at line 5495...
> | Evaluation of this R code-block is disabled.
> | user-error: Unable to resolve link "*uLELFit"
> `----
>
> I thought "OK - I'll search for uLELFit and just fix this link - but I
> could do what I wanted, I did not manage to find the link.
>
> I figured out that I can not search for text in the link.
`org-toggle-link-display' is very helpful here. See [1] for a
discussion of the patch and new behavior.
It is perhaps worth considering to change the error message to show
the link description (when it exists) rather than the link itself to
make it easier to find the bad link.
Regards,
Jake
[1] http://comments.gmane.org/gmane.emacs.orgmode/90891
next prev parent reply other threads:[~2015-03-20 15:38 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 [this message]
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
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='CAA6UvuEHsktko6ezN-hj5ruS=MZ70_xyoaTYXES3cSmwYZmiCQ@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).