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: obsolescense of #+CATEGORY on org-mode 9.x (was: bug#32068: 26.1; problem with org-agenda and categories)
Date: Mon, 09 Jul 2018 14:29:00 +0000 [thread overview]
Message-ID: <86fu0slbyr.fsf@gmail.com> (raw)
In-Reply-To: <87in5okh30.fsf@nicolasgoaziou.fr>
Hi Nicolas.
> The correct syntax is
>
> ** groups
> :PROPERTIES:
> :CATEGORY: 0.6groups
> :END:
it worked. It also worked on emacs 23.4 with org-mode-version 6.33x
> See (info "(org) Property Syntax")
Thanks. For your help on solving this incompatibility.
I would like to add a word here "discoverability".
¿What would have been the way a user should discover this incompatibility
or obsolescense of the "#+CATEGORY"?.
Actually I have seen this behaviour
for more than two months time. because sometimes I use master. So this behaviour has
more than two months or merged. But I think this could lead to an
opportunity for explaning how a user should react to this change. On my
case It have not been easy to find the right way of solving this.
Regards
next prev parent reply other threads:[~2018-07-09 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 0:46 bug#32068: 26.1; problem with org-agenda and categories rrandresf
2018-07-06 0:52 ` bug#32068: forgotten file Andrés Ramírez
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
2018-07-09 7:23 ` Nicolas Goaziou
2018-07-09 14:29 ` andrés ramírez [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86fu0slbyr.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.