emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scott Randby <srandby@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: How are people handling their calendars?
Date: Tue, 25 Oct 2016 11:31:53 -0400	[thread overview]
Message-ID: <d3f97c2a-a77b-231d-c69b-91d68e714a0f@gmail.com> (raw)
In-Reply-To: <877f8wn3zk.fsf@delle7240.chemeng.ucl.ac.uk>

On 10/25/2016 05:59 AM, Eric S Fraga wrote:
> On Tuesday, 25 Oct 2016 at 00:49, Scott Randby wrote:
>> Since I lack the knowledge that appears to be needed to get calendar
>> syncing to work, my need for a calendar on my phone is limited, and it
>> pains me greatly to make any changes to my calendar outside of org, I
>> have a very primitive system for transferring my calendar to my phone.
>>
>> Whenever I make a change to my calendar on my laptop, I open the agenda
>> to show the month which contains the change, export that month to an
>> html file (with a name like 2016-10.html), and upload the html file to
>
> Curiosity: how do you export the agenda month view to HTML?

I'll just give all the commands even though some of them are known to
all org users. This is a totally manual process because I don't have
time to learn how to automate it.

1. Open the agenda: C-c a

2. Switch to month view: v m

3. Navigate to the desired month. Initially, I had to export every
month during which I had stuff on my calendar, but now I just update a
month when I make a change.

4. Export to html: C-x C-w

To export to html, you need to use the .html extension when you name
the file. You can export to other file formats, but the html export is
really nice. See the Exporting Agenda Views section of the manual for
more information.

Scott

  reply	other threads:[~2016-10-25 15:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-23 23:36 How are people handling their calendars? Tristan Strange
2016-10-24  4:20 ` zv
2016-10-24  5:10   ` B.V. Raghav
2016-10-24  6:07 ` Eric Abrahamsen
2016-10-24  6:38   ` Saša Janiška
2016-10-24  7:06     ` Eric Abrahamsen
2016-10-24 11:20       ` Saša Janiška
2016-10-25  5:34         ` Eric Abrahamsen
2016-10-26 18:42           ` Eric Abrahamsen
2016-10-24 10:02 ` Samuel Loury
2016-10-24 13:17 ` Daniel Clemente
2016-10-24 17:27 ` Philip Hudson
2016-10-25  0:49 ` Scott Randby
     [not found] ` <da1598bae16f4c389f9d6318622c0ad0@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-25  9:59   ` Eric S Fraga
2016-10-25 15:31     ` Scott Randby [this message]
     [not found]     ` <21ce04ca420949f3bbc7c34f027a80ed@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-25 19:50       ` Eric S Fraga
     [not found] <55f8276ed2d044288dc1602a9a10f9e9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-24 12:20 ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2016-10-25 10:49 Bartholomaios Edessa
2016-10-25 11:09 ` Saša Janiška
2016-10-25 16:26 Bala Ramadurai

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=d3f97c2a-a77b-231d-c69b-91d68e714a0f@gmail.com \
    --to=srandby@gmail.com \
    --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).