From: Alex Kosorukoff <alex@3form.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Fix capture to make it save the point location
Date: Fri, 23 May 2014 09:04:02 -0700 [thread overview]
Message-ID: <CAHD9_tQXvCDQKDwu=6U2uEs3kJ0vToEaEubxqoJoqB2O+bS4Tw@mail.gmail.com> (raw)
In-Reply-To: <87bnuowll9.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
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 <bzg@altern.org> wrote:
> Hi Alex,
>
> Alex Kosorukoff <alex@3form.com> 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
>
[-- Attachment #2: Type: text/html, Size: 2078 bytes --]
next prev parent reply other threads:[~2014-05-23 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 2:00 [PATCH] Fix capture to make it save the point location Alex Kosorukoff
2014-05-02 2:03 ` Alex Kosorukoff
2014-05-23 12:30 ` Bastien
2014-05-23 15:24 ` Alex Kosorukoff
2014-05-23 15:39 ` Bastien
2014-05-23 16:04 ` Alex Kosorukoff [this message]
2014-05-23 17:36 ` Bastien
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='CAHD9_tQXvCDQKDwu=6U2uEs3kJ0vToEaEubxqoJoqB2O+bS4Tw@mail.gmail.com' \
--to=alex@3form.com \
--cc=bzg@altern.org \
--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).