Re: Bugs and suggestions for Org 4.70

[Carsten Dominik <dominik@science.uva.nl>]

Hi Bastien,

On Apr 11, 2007, at 22:10, Bastien wrote:

> Bugs :
>
> - Comment syntax: M-; still complains that no comment syntax is 
> defined.

I would like to change this but I have given up to understand
this issue.  It has to do with the problem brouoght back up
yesterday by Leo, that after

    #+TITLE: foo

some lines are considered comments if I set the comment
syntax to "#".  If did stare at the lisp code of
newcomment.el and of `do-auto-fill' for several hours.
If anyone can figure out what the problem is in this case,
please!

> - *Bold* words at the beginning of lines are considered
>   headlines when folding/unfolding.

Yes, this is a known problem, unlikely to be fixed soon,
because of the obvious conflict with the outline regular
expression.  This could be ficed by including " " into
the regexp, but I don't dare to do this because of possible
side effects on many org-mode functions.

Best work-around is to use a different character for marking
bold text, configurable in `org-emphasis-alist'.

>
> - 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.

> - Org-mode can't use brackets within a link's label.

Another issue that is hard to fix.  I believe that emacs-wiki
fixes it by escaping the bracket, and then overlaying a
display property with the correct label.  However, this is at
the expense of direct editability (is that an english word????)
of the label.

I'll take a note, maybe this can be fixed.

> Suggestions :
>
> - 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: ?
>
> - TODO keywords could be stripped out from the iCal
>   export - or at least this bit of information could
>   be optional ?

This would look better in the ics export for sure, but
if people are using more than one TODO state, it looses
information.

>
> - It would be nice if we had some feedback in the modeline
>   telling us what project / headline is currently clocked
>   in -- suggestion stolen from the planner mailing list...

I like this idea.  However, it would probably take up a lot
of space in the mode line.....  What do you suggest as the
content of the label?  I guess the elapsed time since the
clock was started, and some info about the item.

> - Publishing a narrowed buffer should re-order levels of
>   headlines.   For example, if the buffer is narrowed
>   to a third-level headline, then this headline should
>   be considered as a first-level headline when exporting
>   (and the fourth as a second-level headline, and so on...)

>
> - Taking (cadr (current-time-zone)) as the exported timezone
>   in .ics format is not always accurate since the car of
>   (current-time-zone) is relevant to the definition of
>   the local timezone.

Hmmm.  What exactly does the ics format want there?  Right now
it would be CEST, is that not understood by calendar programs?
What would they need?
>
> - Instead of telling us that this is not an ordered list, C-c C-c on
>   unordered list items could cycle through these states :
>
>   - ...
>   - [ ] ...
>   - [X] ...

I guess it would not cycle, but switch from nothing to [ ]
and after that just toggle between the states.  I don't think
it should make [X] disappear entirely.  Do you agree?

>
>   ... but maybe the C-c C-c is already *very* busy !

It certainly is.  Does that actually bother anyone?
I quite like it.

>
> - Org-timeline might be aware of several files? -- the
>   default files being org-agenda-files.  But maybe
>   combination of org-agenda / org-agenda-ndays is enough?

I would think so.  The timeline is really a leftover,
because it was the first agenda-like view I implemented.
The agenda now has all but replaced it, but I am keeping
it for backward compatibility, and for an easy way to
restrict to a single project or file.

- Carsten



--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477