From: "andrés ramírez" <rrandresf@hotmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: 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: Mon, 26 Sep 2022 16:37:47 +0000 [thread overview]
Message-ID: <SJ1PR12MB63630251ED1599BDEC357A38A6529@SJ1PR12MB6363.namprd12.prod.outlook.com> (raw)
In-Reply-To: <878rm95r1g.fsf@localhost>
Hi. Ihor.
>>>>> "Ihor" == Ihor Radchenko <yantar92@gmail.com> writes:
[...]
--8<---------------cut here---------------start------------->8---
** PE etiro.espiritual {collaborator.family} :DAVID:
:PROPERTIES:
:CATEGORY: da.santi
:END:
<2022-09-24 Sat 9:00-11:00>
--8<---------------cut here---------------end--------------->8---
That above is an equivalent example using normal timestamps.
On my use case. I have seven categories on this file
for example: chores, work, home, family. I add entries for all this
categories every week (I just try to add entries once a week if possible
on the weekends).
In case I pick normal timestamps I would need to yank 5 lines and edit 2
lines one at the top and other at the bottom of the yanked region. On my
current worflow using diary-style timestamps I just need to add a line
at the bottom and edit that line.
The advantage of using normal timestamps is I could append the line at
the end of the file. On diary-style timestamps I should do occur for the
category and after it C-c C-n for appending at the end of the current subtree.
For my use case I should keep working with diary-style timestamps but
YMMV.
Thanks guys for the help, the tips and the explanation.
Best Regards
next prev parent reply other threads:[~2022-09-26 17:33 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 ` 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/)]) andrés ramírez
2022-09-24 4:34 ` Ihor Radchenko
2022-09-26 16:37 ` andrés ramírez [this message]
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=SJ1PR12MB63630251ED1599BDEC357A38A6529@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).