From: D Goel <deego@gnufans.org>
Subject: Re: appt: allowing hh.mm for time
Date: Fri, 05 Dec 2003 16:18:45 -0500 [thread overview]
Message-ID: <87ad67rmiy.fsf@gnufans.net> (raw)
In-Reply-To: <jwiskvf0zy.fsf@xpc14.ast.cam.ac.uk> (Glenn Morris's message of "Fri, 05 Dec 2003 20:44:33 +0000")
Glenn Morris <gmorris+emacs@ast.cam.ac.uk> writes:
> D Goel wrote:
>
> change consistent for the calendar/diary you will have to deal with
> all of those places. The ":" format may very well be assumed in other
> files in lisp/calendar AFAIK. You may find making this change is more
> trouble than it's worth to you. :(
Glenn
Thanks for pointing this out. I just looked at calendar.el and
diary.el, and indeed, there are some places there that time entries
are parsed, and changes should be made there too. I think there's onle
one or two places in each file that we need to replace : by
"\\(?::\\|\\.\\)", so I am still interested in making the change.
(I am no longer thinking of the customizable
"appt-time-separator". )... we could just replace . by \\|( . \\| :
\\) whenver time is parsed.
Please let me know what you think of it. If you think it is worth
making the change, I will do it, else not.
I do think it is worth it since I (others?) miss appointments (I did
try to get myself used to aa:bb, but still accidentally fill out time
as aa.bb) and I still find hand-editing diary the easiest way to do
it.
If you don't think it is worth it, I guess I will write a private
function that searches the diary for timestrings a.bb and prompts
replacing them, and add that function to my file-save-hook or such.
DG http://gnufans.net/~deego/
--
next prev parent reply other threads:[~2003-12-05 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 15:00 appt: allowing hh.mm for time D Goel
2003-12-05 20:44 ` Glenn Morris
2003-12-05 21:18 ` D Goel [this message]
2003-12-05 23:05 ` Andreas Schwab
2003-12-06 0:58 ` Thien-Thi Nguyen
2003-12-06 21:54 ` Glenn Morris
2003-12-08 15:35 ` D. Goel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ad67rmiy.fsf@gnufans.net \
--to=deego@gnufans.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.