From: Kyle Meyer <kyle@kyleam.com>
To: "Francis J. Monari, Esquire" <monarifj.esq@juno.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: searching for links [8.3.3 (8.3.3-17-gce80a0-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-20160118/)]
Date: Thu, 28 Jan 2016 17:45:40 -0500 [thread overview]
Message-ID: <87r3h1wcff.fsf@kyleam.com> (raw)
In-Reply-To: <56AA8D33.4040408@juno.com> (Francis J. Monari's message of "Thu, 28 Jan 2016 16:50:43 -0500")
Hello,
"Francis J. Monari, Esquire" <monarifj.esq@juno.com> writes:
[...]
> Due to file relocation on the server, I have a number of broken links in
> an org document. (problem: broken links.)
>
> How can I / Is it possible to search and replace on links?
> (expectation: I would like to use search and replace to fix the links.)
>
> I have tried search and replace, but emacs advises me that links have
> been filtered out. (issue: emacs reports that results from the search
> are filtered-out.)
isearch filters these out by default. To avoid this, you can set
search-invisible to t, but then you don't see what you're replacing.
Another option is to toggle literal link display with
org-toggle-link-display, and then run the search and replace as usual.
> The answer might be a "works as expected". I would like to remain
> within the org framework (but using standard search and replace) and
> accomplish this task.
>
> (I thought about forcing the files into a different mode, but I do not
> want to risk the org file structure.)
I don't really see any danger in that because it's just plain text and
it's querying you about what to replace, so I think that's fine too for
a one-off search and replace.
--
Kyle
next prev parent reply other threads:[~2016-01-28 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 21:50 searching for links [8.3.3 (8.3.3-17-gce80a0-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-20160118/)] Francis J. Monari, Esquire
2016-01-28 22:45 ` Kyle Meyer [this message]
2016-02-01 19:43 ` Francis J. Monari, Esquire
2016-02-01 21:07 ` Nick Dokos
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=87r3h1wcff.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=monarifj.esq@juno.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).