From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Gaspard <orgmode@leo.gaspard.io>
Subject: =?UTF-8?B?UmU6IOKAnEZ1enp54oCdIHRpbWVzICjigJxldmVuaW5n4oCdLCA=?=
 =?UTF-8?B?4oCcbW9ybmluZ+KAnSwg4oCcbmlnaHTigJ3igKYp?=
Date: Mon, 10 Dec 2018 16:55:44 +0900
Message-ID: <87lg4xhl33.fsf@llwynog.ekleog.org>
References: <875zw3j4g8.fsf@llwynog.ekleog.org>
	<871s6q8p2q.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45408)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <leo@gaspard.io>) id 1gWGQ2-00024n-9e
	for emacs-orgmode@gnu.org; Mon, 10 Dec 2018 02:55:58 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <leo@gaspard.io>) id 1gWGPy-0004jH-79
	for emacs-orgmode@gnu.org; Mon, 10 Dec 2018 02:55:58 -0500
Received: from grym.ekleog.org ([94.23.42.210]:51876 helo=smtp.gaspard.ninja)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <leo@gaspard.io>) id 1gWGPx-0004i4-Qw
	for emacs-orgmode@gnu.org; Mon, 10 Dec 2018 02:55:54 -0500
In-Reply-To: <871s6q8p2q.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Richard Lawrence <richard.lawrence@berkeley.edu>, emacs-orgmode@gnu.org

Hi Richard,

Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> What about just adding a tag (:evening:, :morning:, etc.) to represent a
> fuzzy time, with a plain date stamp, like <2018-12-04>?
>
> That would allow you to easily create a custom agenda view containing
> just entries with fuzzy times (if they have a timestamp with just a
> date, you can even filter for those that are coming up in the next
> couple of days).  Then when it's convenient, you can look at this agenda
> view and schedule things that are still fuzzy more precisely.

This sounds like a good idea, thanks! Especially combined with Ken
Mankoff's, so that the event still is shown in the overall agenda at an
approximately correct hour so I don't schedule two things at the same
(fuzzy) time :)

With your two ideas it should make a quite good workaround, thank you!

Cheers,
  Leo