From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "andrés ramírez" <rrandresf@gmail.com>
Cc: 32068@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#32068: 26.1; problem with org-agenda and categories
Date: Sun, 08 Jul 2018 01:34:10 +0200 [thread overview]
Message-ID: <87d0vyei31.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <86k1q7knbo.fsf@gmail.com> ("andrés ramírez"'s message of "Sat, 07 Jul 2018 16:44:27 +0000")
Hello,
andrés ramírez <rrandresf@gmail.com> writes:
> It is possible for me to have the previous behaviour. on 26.1
> ¿What change should i do?.
You can definitely get the previous behaviour, but I cannot remember the
change. Just look at the docstring, it is probably straightforward.
> I share my agenda among several devices with different emacs versions
> ("23.4" "25.1" "26.1|26.2|master")
Note that recent Org, i.e., Org 9.0+ do not support Emacs 23 anymore.
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2018-07-07 23:35 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 [this message]
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 ` 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=87d0vyei31.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=32068@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rrandresf@gmail.com \
/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).