From: Carsten Dominik <dominik@science.uva.nl>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-mode release 4.58
Date: Thu, 7 Dec 2006 00:09:57 +0100 [thread overview]
Message-ID: <12b26d3cb3449e66fc9b115845c4762f@science.uva.nl> (raw)
In-Reply-To: <87vekpmhfl.fsf@tallis.ilo.ucl.ac.uk>
On Dec 6, 2006, at 11:45, Bastien wrote:
> Hi Carsten,
>
> Thanks for this new release. I noticed some strange auto-fill related
> bugs in 4.57, but it seems okay now. Here is a little report:
>
> - '*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...
>
> - http:///this,url is not fontified because of the coma (,)
This is on purpose, please use <...> or [[...]]] around URL's with
special characters.
>
> - org-agenda-list-stuck-projects contains a call to (match) which
> leads C-c a # to produce a "Wrong number of arguments" error.
> Removing the (match) is okay.
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 :-(
> - 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?
>
> - 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.
>
> Some feature suggestion (for org v5 ??):
>
> - What about C-u C-c C-e to force ignoring timestamps when
> (re)publishing a project?
I don't understand this one.
>
> - Cycling through priorities does not allow to delete the priority.
> My guess is that [#A] -> [#B] -> [#C] -> nothing -> [#A] -> ...
> is more convenient.
Hmmm, yes, maybe.
>
> - 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?
>
> - In org-mode each task is potentially a project, since each headline
> is potentially at the top of a new tree. This default behavior is
> perfect but sometimes i need what i would call a frozen inline task.
> Something that is a task without being (un)foldable, something that
> is not at the top of a potential subtree.
>
> For example:
>
> ====================================================================
> * Project 1
>
> Text for project one.
>
> **: Frozen inline task for project one.
>
> Text for project one (won't be (un)folded by TABing the frozen task
> aboce)
> ====================================================================
>
> See my point?
I sort-of do. I guess you would to allow tags for these? And have them
listed in TODO lists etc???????
This would be great, but I cannot do it (don't know how).
See my discussion about plain list items some time ago.
But hmmmm, your proposal does ring a bell somewhere - I'll put this
into a background job, lets see what it does.
- Carsten
next prev parent reply other threads:[~2006-12-06 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 10:21 Org-mode release 4.58 Carsten Dominik
2006-12-05 20:59 ` Eddward DeVilla
2006-12-05 21:13 ` Carsten Dominik
2006-12-05 21:14 ` Jason F. McBrayer
2006-12-06 2:52 ` Carsten Dominik
2006-12-06 15:54 ` Jason F. McBrayer
2006-12-06 10:45 ` Bastien
2006-12-06 23:09 ` Carsten Dominik [this message]
2006-12-07 9:46 ` Bastien
2006-12-07 11:08 ` Carsten Dominik
2006-12-07 11:39 ` 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=12b26d3cb3449e66fc9b115845c4762f@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).