From: Magnus Nilsson <magnus.nilsson@alumni.chalmers.se>
To: emacs-orgmode@gnu.org
Subject: Check for broken links in org-mode?
Date: Sat, 6 Nov 2010 09:22:25 +0100 [thread overview]
Message-ID: <AANLkTinPfRhVbcPVDH+8neth8SD5YmTH-_RTbDAihwGf@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
Dear all,
Is there any nice way to check for broken links of different kinds in org
files?
For example by parsing the file and reporting the lines with broken links in
a separate buffer so they can be fixed one after another? If not, I imagine
this is possible to implement (at least to some extent) as a lisp-function.
What do you all think? :)
My incentive for having this function is the following:
I have started using org mode to organize things at work.
One of the nice uses of org-mode is to keep link reminders together with my
notes, so that I quickly can find where information is located when I need
to retrieve it months/years later.
However, paths to where I keep files may be renamed as projects develop,
servers are changed, or as I "brainstorm" my way through different projects.
As my org-files can be quite large now, I have no way of remembering which
links I need to rename.
It would be great to (org-check-for-broken-links &optional org-files-list)
once in a while to keep links up-to-date. This could make it easier for me
and perhaps the next person that sometime will take over my job.
[-- Attachment #1.2: Type: text/html, Size: 1183 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-11-06 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 8:22 Magnus Nilsson [this message]
2010-11-09 20:58 ` Check for broken links in org-mode? David Maus
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=AANLkTinPfRhVbcPVDH+8neth8SD5YmTH-_RTbDAihwGf@mail.gmail.com \
--to=magnus.nilsson@alumni.chalmers.se \
--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).