emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] Infinite loop in org-agenda-show-new-time
Date: Tue, 06 Aug 2013 17:35:25 -0400	[thread overview]
Message-ID: <87zjsujyea.fsf@gmail.com> (raw)
In-Reply-To: 87txj2lo0j.fsf@fastmail.fm

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

Matt Lundin <mdl@imapmail.org> writes:

> Nick Dokos <ndokos@gmail.com> writes:
>
>> So you revert that commit and the infloop goes away? I looked at the
>> functions briefly and I don't understand how this commit could affect
>> what move-to-column does.
>
> Just to confirm: Did you try rescheduling with the agenda buffer
> filtered only to the home tag using the sample file I provided? To
> trigger the bug one must attempt to reschedule an item when 1) the
> agenda is filtered by tags and 2) the item being changed contains
> invisible lines immediately beneath it (b/c of the filtering). Both
> these conditions are necessary to cause the bug on my end.
>

Just a quick follow-up to this question: I believe I followed your
recipe exactly except for loading a minimal startup to set load-path and
to do initial setup (C-c a etc). The org file I used was just as in your
mail (just now, I changed the dates to today's date before trying the
recipe again). I do

     M-x org-agenda
     <
     a
     / <TAB> home <RET>

(I have to hit <TAB> before typing "home" to get the tag - not sure
that's different or whether it matters), then arrow down to the D TODO and

     M-x org-agenda-date-later

The result is shown in the attached screenshot: success afaict -
certainly no infinite loops.


[-- Attachment #2: Screenshot after rescheduling item D --]
[-- Type: image/png, Size: 74124 bytes --]

[-- Attachment #3: Type: text/plain, Size: 1690 bytes --]


Here's my minimal.org.el file:

--8<---------------cut here---------------start------------->8---
;;; -*- mode: emacs-lisp -*-
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/contrib/lisp"))

(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))

(require 'org)

(setq debug-on-error t)
(setq debug-on-quit t)
(setq eval-expression-print-length nil)
(setq eval-expression-print-level nil)

(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
--8<---------------cut here---------------end--------------->8---

here's the foo.org:

--8<---------------cut here---------------start------------->8---
* TODO A							       :home:
  SCHEDULED: <2013-08-06 Tue>
* TODO B							       :work:
  SCHEDULED: <2013-08-06 Mon>
* TODO C							       :play:
  SCHEDULED: <2013-08-06 Mon>
* TODO D							       :home:
  SCHEDULED: <2013-08-06 Tue>
* TODO E							       :work:
  SCHEDULED: <2013-08-06 Mon>
* TODO F							       :play:
  SCHEDULED: <2013-08-06 Mon>
* TODO G							       :home:
  SCHEDULED: <2013-08-06 Mon>
* TODO H							       :work:
  SCHEDULED: <2013-08-06 Mon>
* TODO I							       :play:
  SCHEDULED: <2013-08-06 Mon>
--8<---------------cut here---------------end--------------->8---

and here's the command line:

    emacs -Q -l minimal.org.el foo.org

Can we get some more votes perhaps? If people try the above recipe
(subject to any corrections Matt might have), does emacs go into an
infinite loop?

I haven't read through the rest of your mail yet (let alone tried
anything) but I'll try to do that later tonight.

-- 
Nick

  reply	other threads:[~2013-08-06 21:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05 15:42 [BUG] Infinite loop in org-agenda-show-new-time Matt Lundin
2013-08-05 17:13 ` Nick Dokos
2013-08-05 20:14   ` Matt Lundin
2013-08-05 22:05     ` Nick Dokos
2013-08-06 17:36       ` Matt Lundin
2013-08-06 21:35         ` Nick Dokos [this message]
2013-08-06 22:45           ` Nick Dokos
2013-08-14 15:19             ` Matt Lundin
2013-08-14 15:38               ` Nick Dokos
2013-08-10 15:06         ` Nick Dokos
2013-08-14 15:15           ` Matt Lundin
2013-08-14 15:45             ` Nick Dokos
2013-08-23  9:58               ` Carsten Dominik
2013-08-23 12:07                 ` Nick Dokos
2019-12-26 19:37                   ` Andrew Hyatt
2020-02-01  9:32                     ` Bastien
2020-02-02 15:19                       ` Andrew Hyatt
2020-02-03 19:04                         ` Bastien
2020-02-04 19:25                           ` Andrew Hyatt
2020-02-04 23:38                             ` Bastien
2020-02-05 16:34                               ` Andrew Hyatt
2020-02-05 19:50                               ` Matthew Lundin
2020-02-11  7:56                                 ` Bastien
2020-02-14  3:27                                   ` Andrew Hyatt
2020-02-14 10:02                                     ` Bastien
2020-02-17 19:20                                       ` Andrew Hyatt
2020-02-17 22:53                                         ` 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=87zjsujyea.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --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).