Re: Org-mode release 4.58

[Bastien <bzg@altern.org>]

Carsten Dominik <dominik@science.uva.nl> writes:

>> - '*word* is not fontified because of leading single quote (')
>
> Emphasis, this is a never-ending story.  I'll check if it makes
> sense to change this case, but there will always be special cases
> where things do not work...

I just mentionned this one because french people like me often use
single quotes - but that's not that important (sure).

>> - http:///this,url is not fontified because of the coma (,)
>
> This is on purpose, please use <...> or [[...]]] around URL's with
> special characters.

Oops, i forgot that - sorry.

> Arrrgh, yes this is a bug.  Will be fixed soon.  Dammit, I messed up a
> release again - and I thought I had implemented something cool :-(

This *is* cool!   Except that i've found to many stuck projects...

>> - Maybe a naive question because i don't know the .ics format, but are
>>   the warnings like "This is a deadline" mandatory ?  DL and S already
>>   indicate the status of the event, don't they?
>
> Yes.  I don't remember why I put these, maybe to make things more clear.
> Can you suggest a better output format?

I think DL/S is clear enough.  Maybe another way to implement the
distinction between deadlines and scheduled events is to use VEVENT
and VTODO?  http://tools.ietf.org/html/rfc2445 shows a typical VTODO:

     BEGIN:VTODO
     UID:19970901T130000Z-123404@host.com
     DTSTAMP:19970901T1300Z
     DTSTART:19970415T133000Z
     DUE:19970416T045959Z
     SUMMARY:1996 Income Tax Preparation
     CLASS:CONFIDENTIAL
     CATEGORIES:FAMILY,FINANCE
     PRIORITY:1
     STATUS:NEEDS-ACTION
     END:VTODO

This introduce the DUE: and STATUS: elements.  I'm not sure about this
because it would make a strong difference between ical-scheduled and
ical-"deadlined" items (iCal would display them differently), and this
distinction is more flexible in org-mode.  Just to let you know in
case.

>> - Again on .ics: my scheduled headlines often have links, those are
>>   not well displayed in any iCal i know.  What about striping links
>>   from their first part (i.e. [[A][B]] -> B)?
>
> Hmmmm, would it not be useful to click on them?  I am not sure what
> calendar programs would support that.  Need to make a few test
> myself.

AFAIK, SUMMARY is not very suitable for storing URLs. You might add a
URL=http://... element, but you need to strip all emacs-relevant links
(like gnus: bbdb: vm: etc.).

By the way, if seen the combined ics output insert something like
(category ...) - why not using the CATEGORY: element?  

>> - What about C-u C-c C-e to force ignoring timestamps when
>> (re)publishing a project?
>
> I don't understand this one.

While trying to publish all projects from my ~/org/ directory, I
discovered that org-publish uses timestamps.

`org-publish-use-timestamps-flag' let us turn this off/on, but i'd
like to be able to bypass this flag manually and force re-publishing
of all files when needed (since timestamps might not be accurate).

>> - What about diary inclusion in timeline (C-c a L)?
>
> That is a no, it has no place there.
>
> Use the agenda restricted to the current file:
>
> C-c a 1 a, maybe make a custom command where you change the ndays
> parameter to get a longer listing?

Yes, i'll do that.  While playing with custom commands, i found that
tags-todo commands are wrongly associated with ??? Here is a patch.

--- /home/guerry/e/org/org.el           2006-12-07 10:40:08.000000000 +0100
+++ /home/guerry/e/org/org.el.orig	2006-12-07 10:25:40.000000000 +0100
@@ -7525,7 +7525,6 @@
 			   ((stringp type) type)
 			   ((eq type 'tags) "Tags query")
 			   ((eq type 'todo) "TODO keyword")
-			   ((eq type 'tags-todo) "Tags TODO")
 			   ((eq type 'tags-tree) "Tags tree")
 			   ((eq type 'todo-tree) "TODO kwd tree")
 			   ((eq type 'occur-tree) "Occur tree")

> But hmmmm, your proposal does ring a bell somewhere - I'll put this
> into a background job, lets see what it does.

All right!  Thanks.

-- 
Bastien