Re: [Orgmode] Unable to clock in on task

Keith Lancaster writes: > I updated to 6.32 this morning and am now unable to clock in on > tasks. At first, there was an issue with an org file having a dangling > clock- > in. When I attempted to log in to a task, it alerted me to the > dangling task. No matter how I answered (cancel, etc), Em

Re: [Orgmode] Unable to clock in on task

Nick Dokos writes: > This does look like a bug: org-resolve-clock calls org-files-list which > does not know about the "agenda files list in a file" convention. It > should probably call the function org-agenda-files instead of > org-files-list. org-files-list is only used in this one place and

Re: [Orgmode] Unable to clock in on task

Nick Dokos writes: > Even better, using org-submit-bug-report would have shown us that the > "agenda file list in a file" convention was being used - as you can > imagine, that's not the setting I use, so when I tried clocking in > yesterday, things worked without a problem for me. Back in the d

[Orgmode] Org-mode version 6.32trans; Cannot complete on #+SETUPFILE

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. -

[Orgmode] [PATCH] A few typos

Correct a few spelling mistakes. Some of these are American vs British spelling disagreements but the Org documentation uses the US spellings. diff --git a/doc/org.texi b/doc/org.texi index 25406c0..73289d2 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -434,7 +434,7 @@ Using header arguments S

[Orgmode] [PATCH] The docstring of org-capture-templates

A few minor corrections and suggestions for the org-capture-templates docstring diff --git a/lisp/org-capture.el b/lisp/org-capture.el index 2b02b77..8b6bd03 100644 --- a/lisp/org-capture.el +++ b/lisp/org-capture.el @@ -97,14 +97,16 @@ keys The keys that will select the template, as a st

[Orgmode] [PATCH] Correct some docstrings [part 3]

This is the third patch in a series that makes some straightforward corrections to a number of docstrings. Each change is normally to: - correct a typo, or - fix up hyperlinks to function or variable names, or - ensure slightly better conformance with the documentation guidelines and tips given

[Orgmode] [PATCH] Correct some docstrings [part 4]

Same rationale as previous patches in this series. Phil -- lisp/org-mac-message.el | 10 lisp/org-macs.el|4 +- lisp/org-mks.el | 12 +++-- lisp/org-mobile.el | 12 + lisp/org-mouse.el | 15 ++- lisp/org-plot.el|4 +

[Orgmode] [PATCH] Fix a few references to the JavaScript name

Subject: [PATCH] Fix some trivial typos People like Douglas Crockford (a member of the JavaScript 2.0 committee at ECMA and author of JavaScript: The Good Parts) capitalize the J and the S in JavaScript. This patch fixes some references to follow this standard. --- doc/org.texi | 10 +-

[Orgmode] [PATCH] Docstring fixes

This is the eighth patch in a series that makes some straightforward corrections to a number of docstrings. Each change is normally to: - correct a typo, or - fix up hyperlinks to function or variable names, or - ensure slightly better conformance with the documentation guidelines and tips give

[Orgmode] [PATCH] Docstring fixes

This is the ninth patch in a series that makes some straightforward corrections to a number of docstrings. Each change is normally to: - correct a typo, or - fix up hyperlinks to function or variable names, or - ensure slightly better conformance with the documentation guidelines and tips give

[Orgmode] Simple type

diff --git a/lisp/org-remember.el b/lisp/org-remember.el index 149bd30..91bf482 100644 --- a/lisp/org-remember.el +++ b/lisp/org-remember.el @@ -349,7 +349,7 @@ RET at beg-of-buf -> Append to file as level 2 headline (setq char0 (read-char-exclusive))

Re: [Orgmode] Custom agenda question

Carsten Dominik writes: > On Aug 26, 2009, at 2:04 PM, Daniel Clemente wrote: > >> I saw something strange: Emacs seems to beep with each C-n on that >> view. Not with C-p. >> >> The following (ding) is being run on next-line due to the condition >> end-of-buffer, I don't know why: >> >>(if

[Orgmode] Mode line colour under a clocked item

I have customised the background colour of my mode line face. However, when I clock into a task the background colour under the clocked task button on the mode line reverts to the default grey. That grey background also extends one character to the left of the clocked item button (that is one of