Re: [O] [PATCH] Fix capture to make it save the point location

[Alex Kosorukoff]

Bastien:

yes, I can reproduce the bug using capmove.el with the latest master. It is less salient in the small file that capmove makes, but very obvious in big files where you get to a completely different place after capture finished.

Description of the steps:

1. open the same org file in two frames

2. make sure the positions in those frames are different

3. try to capture something from one of those frames

4. after capture finished, the positions in those frames become the same, i.e. the frame where capture was invoked copied the position from another frame and lost its context that was there before capture.

Best,

Alex

On Fri, May 23, 2014 at 8:39 AM, Bastien <address@hidden> wrote:

Hi Alex,

Alex Kosorukoff <address@hidden> writes:

> did you mean the reply on the Capture Abort thread? This is a
> different bug, unrelated to that the Capture Abort one. In this case
> capture doesn't abort, but returns to a different place in buffer
> than the one it was invoked from.

Indeed, sorry for the confusion.

The thing is: I can't reproduce the problem, even when following the
capmove.el instructions.

Can you reproduce the bug using latest maint or master branch?

If so, a simple description of the steps will be easier than a
file like capmove.el.

Thanks,

--
 Bastien