From: Viktor Rosenfeld <listuser36@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Hotkeys defined in org-tag-alist repeated in agenda filter dispatcher
Date: Mon, 22 Apr 2013 14:01:32 +0200 [thread overview]
Message-ID: <20130422120132.GF7821@cartman> (raw)
In-Reply-To: <87li8aapbq.fsf@bzg.ath.cx>
Hi Bastian,
Bastien wrote:
> Hi Viktor,
>
> Viktor Rosenfeld <listuser36@gmail.com> writes:
>
> > If I hit the =/= key in the agenda to filter the agenda by tag, the
> > hotkeys defined in the list above are repeated multiple times.
>
> Can you test this patch against latest maint or master branch?
The problem still remains with the patch. However, I was able to narrow
the problem to a specific line and can provide a minimal example:
Consider the following configuration (which is loaded in init.el via
org-babel-load-file):
#+BEGIN_SRC emacs-lisp
(global-set-key (kbd "<f12>") 'org-agenda)
(setq org-agenda-files '(
"~/org/dokumente.org"
"~/org/openloops.org"
"~/org/routine.org"
"~/org/arbeit.org"
))
(setq org-tag-alist '((:startgroup . nil)
("@home" . ?h)
("@comp" . ?c)
("@otg" . ?o)
("@fon" . ?f)
("@agenda" . ?a)
("@read" . ?r)
("@write" . ?w)
(:endgroup . nil)
(:startgroup . nil)
("IMPORTANT" . ?*)
("SOMEDAY" . ??)
(:endgroup . nil)))
#+END_SRC
The four agenda files are as follows: The first file, "dokumente.org"
caontains a single headline and a #+TAGS: definition:
#+BEGIN_SRC org :tangle dokumente.org
#+TAGS: foo
* 1996
#+END_SRC
The other three files only contain a heading and no #+TAGS: definition:
#+BEGIN_SRC org :tangle openloops.org
* Inbox
#+END_SRC
#+BEGIN_SRC org :tangle routine.org
* Review
#+END_SRC
#+BEGIN_SRC org :tangle arbeit.org
* 1996
#+END_SRC
With this setup the tag hotkeys are repeated three times, one time for
each file with no tags definition. If I remove the #+TAGS definition in
dokumente.org, the bug disappears. If I add a #+TAGS definition to every
other file, then no tag hotkeys are printed, which is another unexpected
behavior. In other words, the presence of #+TAGS in a file causes the
tag hotkeys to repeated once for every file which does not have a #+TAGS
definition. To achieve the correct behavior, either no #+TAGS:
definition must appear anywhere or there must be exactly one file
without a #+TAGS definition.
Note that the number of repetions also depends on where the file with
the #+TAGS definition is located in the org-agenda-files list. Using the
four files above, if I move the file dokumente.org with the #+TAGS
definition to the end of the list then there are no repetitions.
Cheers,
Viktor
>
> Thanks,
>
next prev parent reply other threads:[~2013-04-22 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 1:50 Viktor Rosenfeld
2013-04-22 9:26 ` Bastien
2013-04-22 12:01 ` Viktor Rosenfeld [this message]
2013-04-24 9:46 ` Bastien
2013-04-24 12:29 ` Viktor Rosenfeld
2013-04-24 13:44 ` 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=20130422120132.GF7821@cartman \
--to=listuser36@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--subject='Re: [BUG] Hotkeys defined in org-tag-alist repeated in agenda filter dispatcher' \
/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
Code repositories for project(s) associated with this 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).