On Feb 27, 2008, at 9:57 PM, Phil Jackson wrote:
Scott Otterson <[EMAIL PROTECTED]> writes:
[...]
+ expand matching pattern outwards until matching uniqueness is
assured across the whole file
This isn't foolproof as an identical line could be added later leaving
us with much the same probl
Scott Otterson <[EMAIL PROTECTED]> writes:
[...]
> + expand matching pattern outwards until matching uniqueness is
> assured across the whole file
This isn't foolproof as an identical line could be added later leaving
us with much the same problem.
> + store line number
This actually is alrea
Yes, starting with line numbers sounds like a good idea. So far, then,
the suggestion in its full glory is:
link storage
include punctuation in matching pattern
expand matching pattern outwards until matching uniqueness is
assured across the whole file
stor
Yeah, I guess that instead of saying it was a small bug, I should have
said that it's a bug of small consequence (for most users, but matters
to me, least).
The ambiguity problem you mention could be solved by matching more than
one line. To keep the string stored in the org link short,
org-
Carsten Dominik <[EMAIL PROTECTED]> 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 use
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.
