From: Paul Sexton <psexton@xnet.co.nz>
To: emacs-orgmode@gnu.org
Subject: Re: Integrating ctags & org mode (patch)
Date: Tue, 15 Dec 2009 20:36:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20091215T213448-675@post.gmane.org> (raw)
In-Reply-To: loom.20091215T205247-286@post.gmane.org
Also I realised there was a misplaced parenthesis in the "(if (y-or-n-p..."
clause. Corrected patch follows.
----BEGIN PATCH for org.el (delete this line)----
8349,8369c8349,8350
{ (condition-case nil (eval cmd)
{ ;; ORG-TAGS
{ (error
{ (progn
{ (widen)
{ (condition-case nil (eval cmd)
{ (error
{ ;; No matching link found anywhere in this file
{ ;; See if we can find a tag
{ ;; If so, jump to it
{ (condition-case nil (find-tag path)
{ (error
{ (cond
{ (org-make-new-topics-for-missing-links-p
{ (if (y-or-n-p
{ (format "Topic `%S' not found; append to current
buffer?"
{ path))
{ (org-append-new-topic path nil)))
{ (t
{ (error "No match found"))))))))))))
{
---
} (condition-case nil (eval cmd)
} (error (progn (widen) (eval cmd))))))
8592,8595d8572
{ ;; ORG-TAGS
{ ((not org-open-link-defaults-to-normal-string-search-p)
{ ;; We don't want to search for a plain text match.
{ (error "No match."))
8651,8682d8627
{
{
{ ;; ORG-TAGS
{
{ (defvar org-open-link-defaults-to-normal-string-search-p nil
{ "Behaviour when attempting to open a 'thisfile' hyperlink for which no
{ EXACT match can be found (i.e. no match in angled brackets, etc).
{ If true (default), exhibit normal org behaviour of doing a search for a string
{ matching the link name.
{ If nil, abort the attempt to open the link.")
{
{
{ (defvar org-make-new-topics-for-missing-links-p nil
{ "If true, when attempting to follow a 'plain' hyperlink for which no precise
{ match is found, offer to append a top-level heading with the same name as the
{ hyperlink, to the end of the buffer.")
{
{
{ (defun org-append-new-topic (word)
{ (interactive "s")
{ (widen)
{ (end-of-buffer)
{ (newline 2)
{ (insert (format "* <<%s>>" word)) ; <<<>>> to make radio word
{ (backward-char 4)
{ ;;(org-update-radio-target-regexp)
{ (end-of-line)
{ (newline 2)
{ (next-line 2))
{
{
{
----END PATCH (delete this line)----
next prev parent reply other threads:[~2009-12-15 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 3:02 Integrating ctags & org mode (patch) Paul Sexton
2009-12-15 3:41 ` Bill Powell
2009-12-15 7:20 ` Carsten Dominik
2009-12-15 14:29 ` Carsten Dominik
2009-12-15 19:58 ` Paul Sexton
2009-12-15 20:36 ` Paul Sexton [this message]
2009-12-15 21:08 ` Paul Sexton
2009-12-15 21:33 ` Nick Dokos
2009-12-15 22:06 ` Óscar Fuentes
2009-12-18 16:00 ` Carsten Dominik
2010-02-06 0:10 ` Samuel Wales
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=loom.20091215T213448-675@post.gmane.org \
--to=psexton@xnet.co.nz \
--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).