emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Goldman <rpgoldman@sift.info>
To: David Maus <dmaus@ictsoc.de>
Cc: Org Mode <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Re: bug with link following --- a (partial) solution
Date: Sun, 12 Sep 2010 21:36:29 -0500	[thread overview]
Message-ID: <4C8D8E2D.3050704@sift.info> (raw)
In-Reply-To: <87hbhvb1hn.wl%dmaus@ictsoc.de>

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]

On 9/12/10 Sep 12 -7:16 AM, David Maus wrote:
> Robert P. Goldman wrote:
>> On 8/29/10 Aug 29 -10:36 AM, Robert Goldman wrote:
>>> I used org-store-link and org-insert-link to make a link in the attached
>>> document (I distilled it down from a real document).  In my org-mode
>>> (pulled from git this morning), using Aquamacs 2.0 on Mac OSX Snow
>>> Leopard (10.6), org-mode cannot follow the link I inserted with o-i-l,
>>> and it pops up a dialog asking if I should add such a link target.
> 
>> A quick followup:
> 
>> I had a shot with git blame, and it seems like the only thing that might
>> have interfered with this search recently is the commit with the SHA1
>> has starting a84c8a2c
> 
>> And, indeed, when I comment out the block that was introduced in this
>> commit (starting at line 9389):
> 
>> ...
> 
>> Carsten, could this patch be reverted until it can be fixed?
> 
> It's not a bug, it's a feature: To revert to the old behaviour you
> can customize the variable `org-link-search-must-match-exact-headline'
> and set it to nil.

I believe I have narrowed down the problem to a more specific case.

I have reexamined the bug I had, and as far as I can tell, it occurs
because of the punctuation at the end of the header line.  I am
attaching a file that shows the funny behavior.  I can link to a header
titled "Foobar" correctly, but not one titled "submit through submission
site:"  Attempts to link to the one word header "Bletch:" also fail.

I conjecture that the problem is the final ":" as punctuation.  Does
that seem plausible?  If so, should we simply extend the escaping in the
links to handle this case (akin to the way spaces are escaping)?  Or am
I off base here?

[-- Attachment #2: link-bug.org --]
[-- Type: text/plain, Size: 848 bytes --]

#+STARTUP: showall

* Notes:

* TODO Figure out org mode

Just do outlines with TODO's in them.  Change them to DONE when they are done.
You don't need to figure out how to use org-mode if you don't like.  We used it
on OBTW, and it worked fine.

If you like (I will probably do this), you can use the org-mode commands to add
deadlines and scheduling (or you can ignore them).  I will probably do this in
an incremental way so that I can further focus my mind on individual subsections
as they need to get written.  See example in [[*submit%20through%20submission%20site][submit through submission site:]]

* TODO submit through submission site:

* TODO Foobar

* Reference to foobar

[[*Foobar][Foobar]]

* Reference to submit...

[[*submit%20through%20submission%20site][submit through submission site]]
  
# Local Variables:
# mode: org
# End:

[-- Attachment #3: 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

  reply	other threads:[~2010-09-13  2:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-29 15:36 bug with link following Robert Goldman
2010-08-29 23:27 ` bug with link following --- a (partial) solution Robert P. Goldman
2010-09-12 12:16   ` David Maus
2010-09-13  2:36     ` Robert Goldman [this message]
2010-09-15  9:18       ` David Maus
2010-09-22 18:11         ` David Maus
2010-09-22 18:36           ` Robert Goldman
2010-09-22 18:38             ` Robert Goldman
2010-09-22 18:44             ` 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=4C8D8E2D.3050704@sift.info \
    --to=rpgoldman@sift.info \
    --cc=carsten.dominik@gmail.com \
    --cc=dmaus@ictsoc.de \
    --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).