emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Harri Kiiskinen <harri.kiiskinen@utu.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: filetags and org-todo-list
Date: Wed, 25 Mar 2009 10:17:40 +0100	[thread overview]
Message-ID: <A9482F94-7F21-4012-9A58-1055663D0719@gmail.com> (raw)
In-Reply-To: <20090325.092133.176664718.harri.kiiskinen@utu.fi>

Yes, a bug.  Fixed, thanks.

- Carsten

On Mar 25, 2009, at 8:21 AM, Harri Kiiskinen wrote:

> Hello!
>
> It seems that org-use-tag-inheritance set to regexp, the use of
> #+FILETAGS: and org-todo-list do not work together. It seems, that a
> regexp in org-use-tag-inheritance matching a tag set in #+FILETAGS
> causes this error:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>  string-match("^ +" nil)
>  org-format-agenda-item("" nil "org_filetag" ("tea" "test"))
>  byte-code("Æ \x18ÇŽÈ ˆ`\x11ŠÉ ˆ`)\x12Ê\n!ƒ(	Tbˆ\v„#ËÌ!ˆÍÎÏ\"ˆ*	bˆÐ ˆÑ”bˆÒÓ”!\x14 
> Ô \x15Õ`!\x16#Ö×ØÑ!
> \x0e#$\x16$Ù\x0e$!T\x16\x1eÚ \x16\"Û\x0e$\x0e%Ü\fÝ\fÞ\x0e\x1eß
> àáâ\x0e\"&\x0eˆ\x0e$\x0e&B\x16&\vƒ~Ñ•bˆ‚‚ËÌ!ˆÏ‡" [save-match-data-internal beg end  
> org-agenda-todo-list-sublevels marker category match-data ((byte- 
> code "Á\bÂ\"‡" [save-match-data-internal set-match-data evaporate]  
> 3)) beginning-of-line outline-next-heading org-agenda-check-for- 
> timestamp-as-reason-to-ignore-todo-item org-end-of-subtree invisible  
> throw :skip nil org-agenda-skip 1 org-agenda-new-marker 0 org-get- 
> category org-get-tags-at org-format-agenda-item "" match-string org- 
> get-priority org-get-todo-state org-add-props org-marker org-hd- 
> marker priority org-category type "todo" todo-state tags txt props  
> ee] 15)
>  org-agenda-get-todos()
>  org-agenda-get-day-entries("~/org_filetag.org" (3 24 2009) :todo)
>  byte-code("Ä\b!ˆÅ\b	Æ#\x12Ç\v\n\"\x13ć" [file date rtn rtnall org-check- 
> agenda-file org-agenda-get-day-entries :todo append] 4)
>  org-todo-list(nil)
>  call-interactively(org-todo-list)
>  execute-extended-command(nil)
>  call-interactively(execute-extended-command)
>
> when org-use-tag-inheritance is set to regexp "te"
> with this file:
>
> --------
> #+STARTUP:
> #+FILETAGS: tea
> * TODO testing 							       :test:
> ** TODO too							       :data:
> -----
>
> When the regexp is "tes", so that the FILETAG does not match,
> org-todo-list produces a correct list.
>
> (org-mode 6.24trans, updated from git 2009/03/25)
>
> Harri
>
> --
> Harri Kiiskinen (harkiisk[at]gmail.com)
> _______________________________________________
> 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

      reply	other threads:[~2009-03-25  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  7:21 filetags and org-todo-list Harri Kiiskinen
2009-03-25  9:17 ` Carsten Dominik [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=A9482F94-7F21-4012-9A58-1055663D0719@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=harri.kiiskinen@utu.fi \
    /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).