From: "andrés ramírez" <rrandresf@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 32068@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#32068: 26.1; problem with org-agenda and categories
Date: Mon, 09 Jul 2018 03:13:27 +0000 [thread overview]
Message-ID: <86h8l9kso8.fsf@gmail.com> (raw)
In-Reply-To: <877em6uk42.fsf@nicolasgoaziou.fr>
Hi Nicolas.
> > I still think this is a bug. Let me explain You why.....
>
> If you try "M-x org-lint" on your document, you'll discover what is your
> problem. In short, your usage of CATEGORY keyword is not possible
> anymore. It's a global keyword, like any other keyword.
I have tried org-lint it suggest me to use :CATEGORY: property. As I
have done on my example. But still It Does not work.
> Use headlines to separate your documents into parts with different
> categories.
I have created also headlines. But even with that. I can not get
previous behaviour.
see my modified file:
--8<---------------cut here---------------start------------->8---
* the world cup on my agenda
** groups
:CATEGORY: 0.6groups
%%(diary-block 6 22 2018 6 22 2018) 7:00 wc: brazil - costa rica (sans petersburgo){GE2}
%%(diary-block 6 22 2018 6 22 2018) 10:00 wc: nigeria - islanda (volgogrado){GD2}
%%(diary-block 6 22 2018 6 22 2018) 13:00 wc: serbia - suiza (kaliningrado){GE2}
%%(diary-block 6 23 2018 6 23 2018) 07:00 wc: belgica - tunez (otkrytiye, moscu){GG2}
%%(diary-block 6 23 2018 6 23 2018) 10:00 wc: mexico - korea (rostov){GF2}
%%(diary-block 6 23 2018 6 23 2018) 13:00 wc: alemania - suecia (sochi){GF2}
%%(diary-block 6 24 2018 6 24 2018) 07:00 wc: inglaterra - panama (nizhny){GG2}
%%(diary-block 6 24 2018 6 24 2018) 10:00 wc: japon - senegal (ekaterimburgo){GH2}
%%(diary-block 6 24 2018 6 24 2018) 13:00 wc: colombia - polonia (kazán){GH2}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: uruguay - rusia (samara){GA3}
%%(diary-block 6 25 2018 6 25 2018) 09:00 wc: egipto - arabia (volgogrado){GA3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: portugal - iran (saransk){GB3}
%%(diary-block 6 25 2018 6 25 2018) 13:00 wc: espanha - marruecos (kaliningrado){GB3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: Dinamarca - francia (luzhniki, moscu){GC3}
%%(diary-block 6 26 2018 6 26 2018) 09:00 wc: PERÙ - australia (sochi){GC3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: argentina - nigeria (san petersburgo){GD3}
%%(diary-block 6 26 2018 6 26 2018) 13:00 wc: croacia - islandia (rostov){GD3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: corea - alemania (kazán){GF3}
%%(diary-block 6 27 2018 6 27 2018) 09:00 wc: mexico - suecia (ekaterimburgo){GF3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: brazil - serbia (otkrytiye, moscu){GE3}
%%(diary-block 6 27 2018 6 27 2018) 13:00 wc: suiza - costa rica (nizhny){GE3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: polonia - japon (volgogrado){GH3}
%%(diary-block 6 28 2018 6 28 2018) 09:00 wc: colombia - senegal (samara){GH3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: inglaterra - belgica (kaliningrado){GG3}
%%(diary-block 6 28 2018 6 28 2018) 13:00 wc: panama - tunez (saransk){GG3}
** dieciseis
:CATEGORY: hello
%%(diary-block 6 30 2018 6 30 2018) 09:00 wc: 1cFrancia - 2dArgentina (kazán){16}
%%(diary-block 6 30 2018 6 30 2018) 13:00 wc: 1aUruguay -2bPortugal (sochi){16}
%%(diary-block 7 01 2018 7 01 2018) 09:00 wc: 2aRusia - 1bEspaña (moscu){16}
%%(diary-block 7 01 2018 7 01 2018) 13:00 wc: 2cDinamarca - 1dCroacia (nizhny){16}
%%(diary-block 7 02 2018 7 02 2018) 09:00 wc: 1eBrazil - 2fMexico (samara){16}
%%(diary-block 7 02 2018 7 02 2018) 13:00 wc: 1gBelgica - 2hJapon (rostov){16}
%%(diary-block 7 03 2018 7 03 2018) 09:00 wc: 2eSuiza - 1fSuecia (san petersburgo){16}
%%(diary-block 7 03 2018 7 03 2018) 13:00 wc: 2gInglaterra - 1hColombia (moscu){16}
** octavos
:CATEGORY: 0.octavos
%%(diary-block 7 06 2018 7 06 2018) 09:00 wc: 1qfFrancia - 2qfUruguay (nizhny){4}
%%(diary-block 7 06 2018 7 06 2018) 13:00 wc: 5qfBrasil - 6qfBelgica (kazán){4}
%%(diary-block 7 07 2018 7 07 2018) 09:00 wc: 7qfRusia - 8qfCrocia (samara){4}
%%(diary-block 7 07 2018 7 07 2018) 13:00 wc: 3qfSuecia - 4qfInglaterra (sochi){4}
** semifinales
:CATEGORY: 0.6semifi
%%(diary-block 7 10 2018 7 10 2018) 09:00 wc: 1sf - 2sf (san petersburgo){SF}
%%(diary-block 7 11 2018 7 11 2018) 09:00 wc: 3sf - 4sf (moscu){SF}
** la final
:CATEGORY: 0.6final
%%(diary-block 7 14 2018 7 14 2018) 09:00 wc: 1p - 2p (san petersburgo){F}
%%(diary-block 7 15 2018 7 15 2018) 09:00 wc: 1f - 2f (luzhniki, moscu){F}
--8<---------------cut here---------------end--------------->8---
the output(incorrect) is:
--8<---------------cut here---------------start------------->8---
Week-agenda (W28):
Monday 9 July 2018 W28
Diary: Martyrdom of the Báb
Tuesday 10 July 2018
jl-diary.agendatest: 9:00...... wc: 1sf - 2sf (san petersburgo){SF}
Wednesday 11 July 2018
jl-diary.agendatest: 9:00...... wc: 3sf - 4sf (moscu){SF}
Thursday 12 July 2018
Friday 13 July 2018
Saturday 14 July 2018
jl-diary.agendatest: 9:00...... wc: 1p - 2p (san petersburgo){F}
Sunday 15 July 2018
jl-diary.agendatest: 9:00...... wc: 1f - 2f (luzhniki, moscu){F}
--8<---------------cut here---------------end--------------->8---
Regards
next prev parent reply other threads:[~2018-07-09 3:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86tvpdnqcp.fsf@sacsa.i-did-not-set--mail-host-address--so-tickle-me>
2018-07-06 6:06 ` bug#32068: 26.1; problem with org-agenda and categories Eli Zaretskii
2018-07-06 13:22 ` andrés ramírez
2018-07-07 11:05 ` Nicolas Goaziou
2018-07-07 11:36 ` Eli Zaretskii
2018-07-07 13:02 ` andrés ramírez
2018-07-07 15:52 ` Nicolas Goaziou
2018-07-07 16:44 ` andrés ramírez
2018-07-07 23:34 ` Nicolas Goaziou
2018-07-08 0:32 ` rrandresf
2018-07-08 9:55 ` Nicolas Goaziou
2018-07-09 3:13 ` andrés ramírez [this message]
2018-07-09 7:23 ` Nicolas Goaziou
2018-07-09 14:29 ` bug#32068: obsolescense of #+CATEGORY on org-mode 9.x (was: bug#32068: 26.1; problem with org-agenda and categories) andrés ramírez
2018-07-09 14:38 ` bug#32068: obsolescense of #+CATEGORY on org-mode 9.x Nicolas Goaziou
2018-07-09 15:03 ` andrés ramírez
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=86h8l9kso8.fsf@gmail.com \
--to=rrandresf@gmail.com \
--cc=32068@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).