From: Carsten Dominik <dominik@science.uva.nl>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Bugs and suggestions for Org 4.70
Date: Fri, 13 Apr 2007 14:38:35 +0200 [thread overview]
Message-ID: <efb0f4fe30c8efaed1d13239ce276594@science.uva.nl> (raw)
In-Reply-To: <871wio1nl8.fsf@bzg.ath.cx>
On Apr 13, 2007, at 14:10, Bastien wrote:
>
>>> - If a list item contains a number that find itself at the beginning
>>> of
>>> a line (within this list item), this number will be considered as a
>>> start for another ordered-list item when exporting. For example :
>>
>> Yes, this is a problem. Again, I would not know how to fix it.
>
> Mmhh. It may require a full rewriting of the lists parsing funcs; i
> didn't
> check your code for that, but having spent a good amount of time
> trying to
> implement something like this for my old bhl-mode, I know list parsing
> is
> always challenging.
Well, in this case it is even impossible. How could
you distinguish the two? I guess the only way would be to require an
empty line before a new list item, but that is not acceptable.
>
>>> - I often attach a location to scheduled/deadlined events. Why not
>>> using LOCATION in addition to SCHEDULED or DEADLINE ? This would
>>> also
>>> end up in a new "LOCATION:" entry in the .ics export. Maybe default
>>> locations could be defined in some #+LOCATIONS: ?
>
> What about this suggestion ?
>
> I dare say this might turn out to be the most useful suggestion i've
> made
> so far. As far as i know, having a structured way to store locations
> for
> scheduled tasks or events is quite common in other organizers and
> text-based organizers like Org could again prove themselves very
> flexible
> when dealing with this.
Yes, interesting idea, implementation not very fast I am afraid, too
many other things on my plate right now.
Thanks for all the great ideas, when I find time I will implement
what I think fits in.
- Carsten
next prev parent reply other threads:[~2007-04-13 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 20:10 Bugs and suggestions for Org 4.70 Bastien
2007-04-13 8:41 ` Carsten Dominik
2007-04-13 10:41 ` Giovanni Ridolfi
2007-04-13 12:10 ` Bastien
2007-04-13 12:38 ` Carsten Dominik [this message]
2007-04-13 13:11 ` Bastien
2007-04-18 6:55 ` Carsten Dominik
2007-04-18 9:17 ` Bastien
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=efb0f4fe30c8efaed1d13239ce276594@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=bzg@altern.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).