From: Ypo <ypuntot@gmail.com>
To: Samuel Wales <samologist@gmail.com>, Jean Louis <bugs@gnu.support>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Dates in headlines
Date: Wed, 29 Jun 2022 20:11:26 +0200 [thread overview]
Message-ID: <dcfcb73a-78a4-fb74-ad62-6e992435fe90@gmail.com> (raw)
In-Reply-To: <CAJcAo8tZLdLLL0NmPAzFcjKF4QXGcS7B=sOozvt0axYG7DWmoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
Thanks, Jean and Samuel, I will keep using them without remorse then :-)
Best regards!
El 28/06/2022 a las 23:13, Jean Louis escribió:
> On 2022-06-28 12:06, Ypo wrote:
>> I think I've read somewhere that it is a "bad practice" to use dates
>> in headlines, is it correct? I haven't found it in the manual.
>>
>> Like:
>>
>> **** <2022-06-29 mi. 10:30> Meeting
>>
>> Best regards
>
> In many of my notes I use dates in titles of the section. Note
creation is not always equal to date to which not relates. When it is
useful, use it.
El 29/06/2022 a las 1:23, Samuel Wales escribió:
> this iirc has been obsolete for many years and ime and on ml never was
> an issue. i tried to find out why it was mentioned but did not find
> anything. it might have been an ambiguity in the manual to do with
> active tses like in your example? e.g. the agenda will remove the
> active ts at least in certain cases, but that is a deliberate feature.
>
> i successfully rely on inactive as below. they are sorted by the ts.
> a capture template inserts them.
>
> much better than date trees for my case. always show, sorted at
> bottom, no hierarchy, nothing out of sync, can scan and bisect to find
> an entry or get a sense of number, can change a ts and sort again,
> looks the same in the agenda, etc.
>
>
> ***** LOG [2021-07-01 Thu] vulcans mediating with klingons
> ***** LOG [2021-06-28 Mon 15:44] brawl. scottie of course :(.
> ***** LOG [2021-06-28 Mon 15:44] hauled away AS garbage?
> ***** LOG [2021-06-28 Mon 15:44] klingons said garbage scow
>
>
> On 6/28/22, Ypo<ypuntot@gmail.com> wrote:
>> I think I've read somewhere that it is a "bad practice" to use dates in
>> headlines, is it correct? I haven't found it in the manual.
>>
>> Like:
>>
>> **** <2022-06-29 mi. 10:30> Meeting
>>
>> Best regards
>>
[-- Attachment #2: Type: text/html, Size: 2726 bytes --]
next prev parent reply other threads:[~2022-06-29 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:06 Dates in headlines Ypo
2022-06-28 21:13 ` Jean Louis
2022-06-28 23:23 ` Samuel Wales
2022-06-29 18:11 ` Ypo [this message]
2022-10-06 10:04 ` What is a "date tree"? (find manual unclear) [was: Re: Dates in headlines] Alain.Cochard
2022-10-07 4:05 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2022-08-16 17:45 Dates in headlines Ypo
2022-08-19 5:58 ` Ihor Radchenko
2023-01-28 8:12 Max Nikulin
2023-02-02 20:37 ` Ihor Radchenko
2023-07-14 12:57 ` Max Nikulin
2023-07-18 9:24 ` Ihor Radchenko
2023-07-19 16:27 ` Max Nikulin
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=dcfcb73a-78a4-fb74-ad62-6e992435fe90@gmail.com \
--to=ypuntot@gmail.com \
--cc=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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).