emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Fletcher Charest <fletcher.charest@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Weird behaviour just after a capture
Date: Tue, 22 Jul 2014 02:13:58 +0200	[thread overview]
Message-ID: <CAGk6a7m_kiu0js0BkdydV4qj49iCFCzrKRrXCm4XVuVceZWKXA@mail.gmail.com> (raw)
In-Reply-To: <87r41e5ln9.fsf@alphaville.bos.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]

Dear Nick,

Apologies, you're absolutely right: the answer was already given in the
list and I must have missed it somehow. (setq-default cache-long-scans nil)
fixes the problem.

Thank you very much!

Regards,

FC


On Tue, Jul 22, 2014 at 1:37 AM, Nick Dokos <ndokos@gmail.com> wrote:

> Fletcher Charest <fletcher.charest@gmail.com> writes:
>
>
> > I am confronted to this bug in every version of Org (shipped with Emacs,
> from maint, and from master). Here is how I can reproduce it every time:
> >
> > 1. emacs -Q (in my case GNU Emacs 24.3.50.1, with Org-mode version
> 8.2.3a)
> >
> > 2. Evaluate this code:
> >
> > (setq org-capture-templates
> >       '(("t" "test" entry (file+olp "~/org2.org" "Todo" "Refile") "*
> TODO %?" :prepend t)))
> >
> > 3. Create the "~/org2.org" file like this:
> >
> > * Todo
> > ** Refile
> > * Other headline 1
> > * Other headline 2
> >
> > 4. M-x org-capture, then do a capture with t.
> >
> > 5. The cycling behaviour gets really weird in org2.org, from the
> captured task until the end of the file. It is just like if whole area was
> considered as a single line (this becomes apparent by turning hl-line-mode
> on). This error
> > appears while trying to cycle with TAB in the area: "byte-code: Invalid
> search bound (wrong side of point)".
> >
> > 6. Close the file and reopen it: everything is fine.
> >
> > Is anyone else confronted to this? I don't know if this is Emacs or
> Org-related.
> >
>
> Searching for "invalid search bound" in the list archives will produce
> lots of results. The last time that this appeared it was a bug in emacs
> (a recently introduced caching mechanism) that was fixed by Eli
> Zaretskii (emacs bug 16265).
>
> I cannot reproduce the problem with my setup:
>
> GNU Emacs 24.4.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.9) of
> 2014-07-07
> Org-mode version 8.2.7 (release_8.2.7 @ /home/nick/elisp/org-mode/lisp/)
>
> so my guess is that your version of emacs does not contain Eli's fix.
>
> Nick
>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2978 bytes --]

      reply	other threads:[~2014-07-22  0:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 23:19 [BUG] Weird behaviour just after a capture Fletcher Charest
2014-07-21 23:37 ` Nick Dokos
2014-07-22  0:13   ` Fletcher Charest [this message]

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=CAGk6a7m_kiu0js0BkdydV4qj49iCFCzrKRrXCm4XVuVceZWKXA@mail.gmail.com \
    --to=fletcher.charest@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).