From: Ulf Jasper <ulf.jasper@web.de>
To: emacs-pretest-bug@gnu.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: Re: icalendar "description" suggestion
Date: Tue, 08 Jan 2008 21:26:14 +0100 [thread overview]
Message-ID: <87fxx8awt5.fsf@web.de> (raw)
In-Reply-To: <m33atdxrwd.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 04 Jan 2008 13:22:26 -0700")
Tom Tromey <tromey@redhat.com> writes:
> It would be nice if icalendar-import-buffer understood this convention
> and deleted any text before the magic string from the description.
>
> More generally it would be nice to be able to exert more control the
> over formatting of the description than is provided by a format string
> like icalendar-import-format-description. For instance, in my case I
> want to compact sequences of newlines into a single newline.
That magic string stuff is not part of the icalendar standard. It is
just some secret convention that some ical export tool uses. It may
change anytime. I don't think that icalendar.el should support stuff
like that.
Instead I suggest to allow not only format strings but also functions as
values of icalendar-import-format-description. Such a function must take
the imported description string as argument. Of course, the same should
be done for the other icalendar-import-format-* variables and for
icalendar-import-format itself (which would require a function with more
than 1 arguments).
That will give users complete control over the import of icalendar data.
However, I see a problem regarding export of diary data. Import and
export was supposed to be reversible and so icalendar.el currently uses
icalendar-import-format-* for *formatting icalendar entries* when
importing and for *parsing diary entries* when exporting. This will not
work with formatting functions.
On the other hand: I have noticed there are other problems with export,
so this might not count. ;)
Ulf
--
Merken Sie auch, muss diese Verhandlung wegen seiner Natur behalten
werden. ich, mich auf Annahme Ihre unverzügliche Erwiderung zu freuen.
next prev parent reply other threads:[~2008-01-08 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 20:22 icalendar "description" suggestion Tom Tromey
2008-01-08 20:26 ` Ulf Jasper [this message]
2008-01-10 1:50 ` Tom Tromey
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=87fxx8awt5.fsf@web.de \
--to=ulf.jasper@web.de \
--cc=emacs-pretest-bug@gnu.org \
--cc=tromey@redhat.com \
/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.