emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: TRS-80 <lists.trs-80@isnotmyreal.name>, emacs-orgmode@gnu.org
Subject: Re: generate an org file for today's appointments
Date: Fri, 04 Dec 2020 09:20:17 +0100	[thread overview]
Message-ID: <87blfa56f2.fsf@m4x.org> (raw)
In-Reply-To: <8a5115860cf1cc98c48d83829efc3da1@isnotmyreal.name>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]


On 2020-12-03 20:15, TRS-80 <lists.trs-80@isnotmyreal.name> writes:

> I am also not someone who uses one of these "daily journal" workflows,
> so I can't help but wonder how you link these daily notes back to the
> underlying project that generated the event on the agenda in the first
> place.  Becasue in my mind, I would jump from the agenda to the
> underlying project or task and be making my notes in there directly.
> Those linking considerations, in my mind anyway, would really dictate
> the rest of the workflow.

This is a very good point. My appointments do not currently have links
to the related projects (the "database of trust" is the calendar one,
which is caldav outside of emacs… maybe I should change that, but I need
to synchronize my calendar with my phone). So I currently add the links
manually. I'll have to think about this.



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]

  reply	other threads:[~2020-12-04  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02  8:36 generate an org file for today's appointments Alan Schmitt
2020-12-03 11:01 ` Mikhail Skorzhisnkii
2020-12-04  1:15   ` TRS-80
2020-12-04  8:20     ` Alan Schmitt [this message]
2020-12-04  8:13   ` Alan Schmitt

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:

  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=87blfa56f2.fsf@m4x.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lists.trs-80@isnotmyreal.name \


* 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


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).