From: "andrés ramírez" <rrandresf@hotmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)])
Date: Sat, 24 Sep 2022 04:10:51 +0000 [thread overview]
Message-ID: <SJ1PR12MB63632D303F71422543441D1DA6509@SJ1PR12MB6363.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87illd5ug5.fsf@localhost>
Hi. Ihor.
>>>>> "Ihor" == Ihor Radchenko <yantar92@gmail.com> writes:
[...]
Ihor> What about
--8<---------------cut here---------------start------------->8---
** PE :DAVID:
:PROPERTIES:
:CATEGORY: da.santi
:END:
<2022-10-01 Sat>
--8<---------------cut here---------------end--------------->8---
The only missing part from the given example was the message. The given
example was:
,---- [ ]
| ** PE :DAVID:
| :PROPERTIES:
| :CATEGORY: da.santi
| :END:
| %%(diary-block 10 1 2022 10 1 2022) 9:00-11:00 retiro.espiritual {collaborator.family}
`----
which one would the place for 'retiro.espiritual {collaborator.family}'?
Ihor> The long file name you are seeing in agenda is dictated by category in
Ihor> org-agenda-prefix-format:
Ihor> %c the category of the item, "Diary" for entries from the diary, or as given by the
Ihor> CATEGORY keyword or derived from the file name
I started using org-mode on emacs-23. So I remember from that year until
now. Once I needed to reformat my agenda files (because CATEGORY was
needed for trying to mimic my previous behaviour of org-agenda). After
settle on that I have not examined that part of my workflow anymore. But
this is emacs 'trying to shave things of our workflow and improve our
daily tasks routines'. I am reviewing it now with You guys.
Best Regards
next prev parent reply other threads:[~2022-09-24 4:16 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 17:02 [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)] Andrés Ramírez
2022-09-08 5:59 ` Ihor Radchenko
2022-09-12 17:55 ` andrés ramírez
2022-09-13 1:56 ` Ihor Radchenko
2022-09-13 2:53 ` andrés ramírez
2022-09-13 3:03 ` Ihor Radchenko
2022-09-13 4:00 ` andrés ramírez
2022-09-13 4:45 ` Ihor Radchenko
2022-09-13 23:29 ` andrés ramírez
2022-09-14 2:15 ` Ihor Radchenko
2022-09-14 16:30 ` andrés ramírez
2022-09-16 4:35 ` Ihor Radchenko
2022-09-16 11:31 ` andrés ramírez
2022-09-20 11:30 ` Ihor Radchenko
2022-09-20 13:28 ` andrés ramírez
2022-09-20 13:51 ` Ihor Radchenko
2022-09-20 14:51 ` andrés ramírez
2022-09-21 4:47 ` Ihor Radchenko
2022-09-22 1:59 ` andrés ramírez
2022-09-22 3:32 ` Ihor Radchenko
2022-09-22 4:27 ` andrés ramírez
2022-09-22 4:44 ` Ihor Radchenko
2022-09-22 5:00 ` andrés ramírez
2022-09-22 5:04 ` Ihor Radchenko
2022-09-22 13:23 ` andrés ramírez
2022-09-23 3:05 ` Ihor Radchenko
2022-09-23 3:19 ` andrés ramírez
2022-09-23 3:35 ` Ihor Radchenko
2022-09-23 3:57 ` andrés ramírez
2022-09-23 5:11 ` Ihor Radchenko
2022-09-23 14:55 ` andrés ramírez
2022-09-23 15:36 ` Ihor Radchenko
2022-09-23 16:14 ` andrés ramírez
2022-09-23 17:08 ` Fraga, Eric
2022-09-23 17:23 ` andrés ramírez
2022-09-24 3:20 ` Ihor Radchenko
2022-09-24 4:10 ` andrés ramírez [this message]
2022-09-24 4:34 ` on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)]) Ihor Radchenko
2022-09-26 16:37 ` andrés ramírez
2022-09-27 2:38 ` Ihor Radchenko
2022-09-27 2:59 ` on picking diary-style timestamps or normal timestamps when adding agenda entries andrés ramírez
2022-09-27 3:21 ` Ihor Radchenko
2022-09-23 16:33 ` [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/share/emacs/28.1/lisp/org/)] Max Nikulin
2022-09-24 3:28 ` Ihor Radchenko
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=SJ1PR12MB63632D303F71422543441D1DA6509@SJ1PR12MB6363.namprd12.prod.outlook.com \
--to=rrandresf@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).