From: Carsten Dominik <dominik@science.uva.nl>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Tiny bugs (and org-toggle-comments?)
Date: Wed, 22 Nov 2006 06:17:16 +0100 [thread overview]
Message-ID: <7d991b54c91f21ede68ef2222195bc7b@science.uva.nl> (raw)
In-Reply-To: <87psbg68eu.fsf@tallis.ilo.ucl.ac.uk>
Hi Bastien,
On Nov 21, 2006, at 18:01, Bastien wrote:
> Hi Carsten,
>
> - <bbdb:...> links are not recognized as links in the agenda buffer
Links in angular brackets are kept mostly for backward compatibility
in Org-mode. Please write [[bbdb:...]] instead.
>
> - M-TAB expands ":ta" to ":tag:" (which is correct) but
> M-TAB expands ":tag" to ":tag" (":" lacking)
Hmmm, thats right. Not easy to fix this, but I will put it on my list.
> - Comment regions are not filled (auto-fill is just ignored). Maybe
> that's not a bug, but I think we should be able to turn filling on
> for comment regions if needed.
Yes, even M-q does not work to fill a paragraph of comment.
I'll check into it.
> Since i'm on this, What about org-toggle-comment-at-point that would
> hide/show comment under the point? org-toggle-comments that would do
> this on the whole buffer? Not sure about this though.
You mean to hide this like an outline-subtree????
> - Time clocking :
>
> When clocking in-and-out on a single task several times, it may end
> up in a long list of "CLOCK: []" lines. We might be only interested
> in the "how much time" we spent, not the exact "when".
>
> In this case, clocking in would open a temporary "CLOCK:" line, but
> clocking out would just leave a single "TIME:" line as a summary of
> the time spent. And maybe this "TIME:" line would also be useful
> for those who want to use the normal CLOCK: system.
Yes, this would be a good way to keep these lists from growing too much,
which has also bothering me. I will also put this on my list,
but this will not be in the next version, some time down the road.
> - Other C-c C-c capabilities (?)
>
> C-c C-c on time intervals could update the "=> ..:.." result
>
> C-c C-c on other time intervals could display the interval (in the
> minibuffer)
Hmmm, yes, I'll consider this too.
Thanks!
- Carsten
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
next prev parent reply other threads:[~2006-11-22 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 17:01 Tiny bugs (and org-toggle-comments?) Bastien
2006-11-22 5:17 ` Carsten Dominik [this message]
2006-11-22 7:57 ` Bastien
2006-11-22 22:55 ` Carsten Dominik
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=7d991b54c91f21ede68ef2222195bc7b@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).