Bug: Follow mode error when a task contains % in the headline [6.33d (release_6.33d.1.g858d)]

Bug: Follow mode error when a task contains % in the headline [6.33d (release_6.33d.1.g858d)]

[Bernt Hansen]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

     http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------

I'm reviewing my tasks in the agenda with follow mode enabled (F) and
when I get to the following task org-mode throws an error

** SOMEDAY org-remember-templates Add %C to clock in the task	    :WAITING:

Debugger entered--Lisp error: (error "Not enough arguments for format string")
  message(#("org.org/Enhancements/org-remember-templates Add %C to clock in the task" 0 8 nil 8 20 (face org-level-1) 20 21 nil 21 71 (face org-level-2)))
  (let ((bfn ...) (path ...)) (if current (setq path ...)) (message (org-format-outline-path path ... ...)))
  org-display-outline-path(t)
  (save-excursion (goto-char (or m ...)) (org-display-outline-path t))
  (save-excursion (if (markerp m) (set-buffer ...)) (save-excursion (goto-char ...) (org-display-outline-path t)))
  (org-with-point-at m (org-display-outline-path t))
  (message (org-with-point-at m (org-display-outline-path t)))
  (if (and m org-agenda-show-outline-path) (message (org-with-point-at m ...)))
  (let ((m ...)) (if (and org-agenda-follow-mode m) (org-agenda-show)) (if (and m org-agenda-show-outline-path) (message ...)))
  org-agenda-do-context-action()
  org-agenda-next-line()
  call-interactively(org-agenda-next-line)

-Bernt


Emacs  : GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
 of 2008-11-09 on raven, modified by Debian
Package: Org-mode version 6.33d (release_6.33d.1.g858d)

Re: Bug: Follow mode error when a task contains % in the headline [6.33d (release_6.33d.1.g858d)]

[Bernt Hansen]

Bernt Hansen <bernt@norang.ca> writes:

> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.  You don't know how to make a good report?  See
>
>      http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org-mode mailing list.
> ------------------------------------------------------------------------
>
> I'm reviewing my tasks in the agenda with follow mode enabled (F) and
> when I get to the following task org-mode throws an error
>
> ** SOMEDAY org-remember-templates Add %C to clock in the task	    :WAITING:

Actually it's this heading not the one above

*** TODO Add %C trigger in remember template processing		       :NEXT:

-Bernt

>
> Debugger entered--Lisp error: (error "Not enough arguments for format string")
>   message(#("org.org/Enhancements/org-remember-templates Add %C to clock in the task" 0 8 nil 8 20 (face org-level-1) 20 21 nil 21 71 (face org-level-2)))
>   (let ((bfn ...) (path ...)) (if current (setq path ...)) (message (org-format-outline-path path ... ...)))
>   org-display-outline-path(t)
>   (save-excursion (goto-char (or m ...)) (org-display-outline-path t))
>   (save-excursion (if (markerp m) (set-buffer ...)) (save-excursion (goto-char ...) (org-display-outline-path t)))
>   (org-with-point-at m (org-display-outline-path t))
>   (message (org-with-point-at m (org-display-outline-path t)))
>   (if (and m org-agenda-show-outline-path) (message (org-with-point-at m ...)))
>   (let ((m ...)) (if (and org-agenda-follow-mode m) (org-agenda-show)) (if (and m org-agenda-show-outline-path) (message ...)))
>   org-agenda-do-context-action()
>   org-agenda-next-line()
>   call-interactively(org-agenda-next-line)

Re: Bug: Follow mode error when a task contains % in the headline [6.33d (release_6.33d.1.g858d)]

[Carsten Dominik]

Fixed, thanks.

- Carsten

On Nov 20, 2009, at 8:06 PM, Bernt Hansen wrote:

>
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen.  You don't know how to make a good report?   
> See
>
>     http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org-mode mailing list.
> ------------------------------------------------------------------------
>
> I'm reviewing my tasks in the agenda with follow mode enabled (F) and
> when I get to the following task org-mode throws an error
>
> ** SOMEDAY org-remember-templates Add %C to clock in the  
> task	    :WAITING:
>
> Debugger entered--Lisp error: (error "Not enough arguments for  
> format string")
>  message(#("org.org/Enhancements/org-remember-templates Add %C to  
> clock in the task" 0 8 nil 8 20 (face org-level-1) 20 21 nil 21 71  
> (face org-level-2)))
>  (let ((bfn ...) (path ...)) (if current (setq path ...)) (message  
> (org-format-outline-path path ... ...)))
>  org-display-outline-path(t)
>  (save-excursion (goto-char (or m ...)) (org-display-outline-path t))
>  (save-excursion (if (markerp m) (set-buffer ...)) (save-excursion  
> (goto-char ...) (org-display-outline-path t)))
>  (org-with-point-at m (org-display-outline-path t))
>  (message (org-with-point-at m (org-display-outline-path t)))
>  (if (and m org-agenda-show-outline-path) (message (org-with-point- 
> at m ...)))
>  (let ((m ...)) (if (and org-agenda-follow-mode m) (org-agenda- 
> show)) (if (and m org-agenda-show-outline-path) (message ...)))
>  org-agenda-do-context-action()
>  org-agenda-next-line()
>  call-interactively(org-agenda-next-line)
>
> -Bernt
>
>
> Emacs  : GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
> of 2008-11-09 on raven, modified by Debian
> Package: Org-mode version 6.33d (release_6.33d.1.g858d)
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

Re: Bug: Follow mode error when a task contains % in the headline [6.33d (release_6.33d.1.g858d)]

[Bernt Hansen]

Carsten Dominik <carsten.dominik@gmail.com> writes:

> Fixed, thanks.
>
> - Carsten

Thanks :)  It works fine now.

-Bernt