emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: Alan Schmitt <alan.schmitt@polytechnique.org>, emacs-orgmode@gnu.org
Subject: Re: generate an org file for today's appointments
Date: Thu, 03 Dec 2020 20:15:56 -0500	[thread overview]
Message-ID: <8a5115860cf1cc98c48d83829efc3da1@isnotmyreal.name> (raw)
In-Reply-To: <878saf8878.fsf@eml.cc>

> On 2020-12-03 06:01, Mikhail Skorzhisnkii wrote:
>> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>> 
>> I have my calendars converted to org files (using ical2orgpy), and as 
>> I
>> include them as agenda files, I have this nice view in org-agenda:
>> 
>>                9:10...... now - - - - - - - - - - - - - - - - -
>>   AlanWork:   10:00-12:00 Event A -
>>   Chris:      10:00-11:00 Event B -
>>               10:00...... ----------------
>>               12:00...... ----------------
>>   AlanWork:   14:00-15:30 Event C -
>>               14:00...... ----------------
>>               16:00...... ----------------
>>               18:00...... ----------------
>>   Alan:       20:00-21:30 Event D -
>> 
>> Is there a way to piggy-back on all the work that org-agenda already 
>> did
>> to generate something like:
>> 
>> ** 10:00 Event A
>> ** 10:00 Event B
>> ** 14:00 Event C
>> ** 20:00 Event D
>> 
>> This would then be inserted in my daily journal file.
>> 
>> I guess the alternative is using org-element to extract the 
>> information
>> from the calendars in org format, but it seems to me org-agenda 
>> already
>> did all the hard work.

> I'd suggest to use function "org-agenda-write". You can export your
> agenda views to org files too! However, the formatting will be
> different. Probably something like:
> 
> * Event A
>  SCHEDULED: <2020-12-03 Thu 10:00-12:00>
> * Event B
>  SCHEDULED: <2020-12-03 Thu 10:00-11:00>
> * Event C
>  SCHEDULED: <2020-12-03 Thu 14:00-15:30>
> * Event D
>  SCHEDULED: <2020-12-03 Thu 20:00-21:30>
> 
> I personally do this to generate separate org-file and then generate
> ics file based on that and upload this ics file through WebDAV to my
> calendar server.

@Alan,

I don't know if there is a way directly in Org to do what you want or
not, but for some reason my brain goes toward copying the text (either
directly from your agenda, or from Mikhail solution) into some other
buffer and then doing some macro or ELisp based post-processing.  But
I really don't know if that's the Right Thing to do or not.

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.

Cheers,
TRS-80


  reply	other threads:[~2020-12-04  1:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02  8:36 Alan Schmitt
2020-12-03 11:01 ` Mikhail Skorzhisnkii
2020-12-04  1:15   ` TRS-80 [this message]
2020-12-04  8:20     ` Alan Schmitt
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:
  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=8a5115860cf1cc98c48d83829efc3da1@isnotmyreal.name \
    --to=lists.trs-80@isnotmyreal.name \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    /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).