all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: Scott Otterson <scotto@u.washington.edu>, emacs-orgmode@gnu.org
Subject: Re: bug in org-store-link
Date: Wed, 27 Feb 2008 11:20:31 -0500	[thread overview]
Message-ID: <11120.1204129231@alphaville.zko.hp.com> (raw)
In-Reply-To: Message from Carsten Dominik <dominik@science.uva.nl> of "Wed, 27 Feb 2008 15:55:33 +0100." <C0E24317-4DD1-4729-9E66-78D69FACF1F0@science.uva.nl>

Carsten Dominik <dominik@science.uva.nl> wrote:

> Hi Scott, this is not a small bug, but a problem that is really hard  
> to solve.
> Supposed I used the exact line text to search, then you still have two  
> lines in the buffer
> that would match.
> 
> This is really about what strategy should be used to find a location
> in a file that has possibly changed.
> I have no good answer to that.  Do you?
> 

Two suggestions:

o Use a line number, instead of a search pattern and don't worry
about subsequent edits to the file that the link points to.

o Use the find-tag strategy: go to the line number as an initial
approximation. If the pattern is found there, done; if not, search
around that point for the pattern and keep expanding the area of the
search until found. I don't know if they still do it that way but I 
think that's how it was done some time ago.

Nick

  reply	other threads:[~2008-02-27 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 20:40 bug in org-store-link Scott Otterson
2008-02-27 14:55 ` Carsten Dominik
2008-02-27 16:20   ` Nick Dokos [this message]
2008-02-27 20:28     ` Scott Otterson
2008-02-27 20:57       ` Phil Jackson
2008-02-27 23:05         ` Carsten Dominik
2008-02-27 19:05   ` Scott Otterson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11120.1204129231@alphaville.zko.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=scotto@u.washington.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.