From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kosorukoff Subject: Re: [PATCH] Fix capture to make it save the point location Date: Fri, 23 May 2014 09:04:02 -0700 Message-ID: References: <87oayo8vyc.fsf@bzg.ath.cx> <87bnuowll9.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c28f5eff06cf04fa136154 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnrxI-0001XV-2G for emacs-orgmode@gnu.org; Fri, 23 May 2014 12:04:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WnrxG-0005y7-TZ for emacs-orgmode@gnu.org; Fri, 23 May 2014 12:04:24 -0400 Received: from mail-qc0-x235.google.com ([2607:f8b0:400d:c01::235]:50028) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnrxG-0005xz-OY for emacs-orgmode@gnu.org; Fri, 23 May 2014 12:04:22 -0400 Received: by mail-qc0-f181.google.com with SMTP id m20so8383331qcx.40 for ; Fri, 23 May 2014 09:04:22 -0700 (PDT) In-Reply-To: <87bnuowll9.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org --001a11c28f5eff06cf04fa136154 Content-Type: text/plain; charset=UTF-8 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 wrote: > Hi Alex, > > Alex Kosorukoff 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 > --001a11c28f5eff06cf04fa136154 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Bastien:

yes, I can reproduce the= bug using capmove.el with the latest master. It is less salient in the sma= ll 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 pos= itions in those frames are different
3. try to capture some= thing 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 <bzg@altern.org> = wrote:
Hi Alex,

Alex Kosorukoff <alex@3form.com>= ; writes:

> did you mean the reply on the Capture Abort thre= ad? 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<= br> > 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,

--
=C2=A0Bastien

--001a11c28f5eff06cf04fa136154--