[O] taking note when clocking out
Hello, I cannot find this using google nor browsing documentation so I ask for help. Generally I don't want to take notes when I'm clocking out except for one task. Is there property I can set that forces me to take note everytime I clock out from this single task? Thanks, Radek.
Re: [O] ascii export problem/bug?
Do you have org-install.el in your init file? On Wed, Apr 13, 2011 at 8:08 AM, Scott Otterson wrote: > When I start emacs and then edit an org file, ascii export fails (M-x > org-export [return key] a). No export file is created and I see the > following message: > Autoloading failed to define function org-export-as-ascii > But if I type: > M-x org-customize > then export works. The other way I can get this to work is to manually load > org-ascii.el (which came with the org mode distribution). > This is with org-mode version 7.5. > Scott > > -- Jeffrey Horn http://www.failuretorefrain.com/jeff/
[O] Nick Dokos: Typo (was: Re: [BUG] doc/org.texi)
Pfui - I forgot to cc: the list - again...
--- Forwarded Message
Date:Wed, 13 Apr 2011 23:09:01 -0400
From:Nick Dokos
To: Carsten Dominik
cc: nicholas.do...@hp.com
Subject: Typo (was: Re: [O] [BUG] doc/org.texi)
... and a typo:
diff --git a/doc/org.texi b/doc/org.texi
index 44d7d21..a2b4b55 100644
- --- a/doc/org.texi
+++ b/doc/org.texi
@@ -8080,7 +8080,7 @@ s @r{Schedule all items to a new date. To shift existin
g schedule dates}
@r{by a fixed number of days, use something starting with double plus}
@r{at the prompt, for example @samp{++8d} or @samp{++2w}.}
S @r{Reschedule randomly into the coming N days. N will be prompted for.}
- - @r{With prefix arg (@kbd{C-u B S}), scatter only accross weekdays.}
+ @r{With prefix arg (@kbd{C-u B S}), scatter only across weekdays.}
d @r{Set deadline to a specific date.}
f @r{Apply a function to marked entries.}
@r{For example, the function below sets the CATEGORY property of the}
--- End of Forwarded Message
Re: [O] [bug?] [babel] cannot generate table format output for octave results
Hi- Eric S Fraga ucl.ac.uk> writes: > > Hello, > > I want an octave babel code block to generate an org table as the > /result/ so that it can be used by another code block elsewhere in my > document. Typically, because of how I generate my data, I would like > babel to create the table from the /output/ of the octave code, not the > value. However, specifying =:results output table= doesn't seem to work > (for me, in any case). I can report a very similar apparent bug, but using python. -- Ethan Ligon, Associate Professor Agricultural & Resource Economics University of California, Berkeley
Re: [O] html export question
On Wed, Apr 13, 2011 at 12:28 PM, Nick Dokos wrote: > Rustom Mody wrote: > >> On Wed, Apr 13, 2011 at 8:43 AM, Bernt Hansen wrote: >> > Rustom Mody writes: >> > >> >> If the >> >> $+EMAIL: r...@somewhere.com >> >> option is set it used to appear at the bottom of the html-export. >> >> >> >> Does not seem to appear now. >> >> >> >> Is this a regression or am I missing some option? >> >> >> >> IOW with >> >> >> >> #+AUTHOR: Rusi >> >> #+EMAIL: myn...@somewhere.com >> >> >> >> Rusi appears in the html output but not myn...@somewhere.com >> >> >> >> org-version 7.5 >> >> emacs 23.1 and 24.0 >> >> >> >> Thanks >> >> Rusi >> > >> > Hi Rusi, >> > >> > This has been fixed after the 7.5 release. The development version of >> > git exports the email address. >> > >> > Regards, >> > Bernt >> > >> >> Did a git pull just now and still its the same. >> How do I check that we are on the same git commit? >> > > You have to add an option to include the email address in the postamble: > > , > | #+AUTHOR: foo > | #+EMAIL: bar@baz > | #+OPTIONS: email:t > ` > > That will produce > > , > | > | Date: 2011-04-13 02:46:10 EDT > | Author: foo > | mailto:bar@baz";>bar@baz > | Org version 7.5 with Emacs version 24 > | http://validator.w3.org/check?uri=referer";>Validate XHTML 1.0 > | > ` > > Alternatively, set org-export-html-postamble to t (by default, it's auto). Thanks Nick. Sorry I did not look a few lines below on the same page -- I guessed there was some (set of) options but did not know where to look :-) Still maybe the line in the doc #+EMAIL: his/her email address (default from user-mail-address) is a bit misleading -- given that the default is no email? Rusi
Re: [O] Bug: Backtrace [7.5 (release_7.5.135.g7021f.dirty)]
At Thu, 14 Apr 2011 00:17:46 +0200, Carsten Dominik wrote: > > Please try the latest git version. Thanks, I will! -- Dave Abrahams BoostPro Computing http://www.boostpro.com
[O] [BUG] doc/org.texi
I just pulled (Org-mode version 7.5 (release_7.5.177.ge201)) and got this: , | $ make info | (cd doc; makeinfo --no-split org.texi -o org) | /home/nick/src/emacs/org/org-mode/doc | org.texi:8082: @r missing close brace. | makeinfo: Removing output file `org' due to errors; use --force to preserve. | make: *** [doc/org] Error 1 `
Re: [O] Bug: Backtrace [7.5 (release_7.5.135.g7021f.dirty)]
At Thu, 14 Apr 2011 00:17:46 +0200, Carsten Dominik wrote: > > I think I have fixed this bug - along with a few more issues in this bulk > command. > Please try the latest git version. Thanks; I will! -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] Bug: Backtrace [7.5 (release_7.5.135.g7021f.dirty)]
On 11.4.2011, at 19:39, Dave Abrahams wrote:
>
>
> 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.
>
>
> I had mistakenly un-scheduled a bunch of items. Then I marked them all
> in the agenda and tried to scatter over 20 weekdays (`C-u B S 2 0 RET')
> and got this backtrace:
I think I have fixed this bug - along with a few more issues in this bulk
command.
Please try the latest git version.
- Carsten
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
> <(nil nil)
> (cond ((equal ... ...) (< ... ...)) (t (string< ... ...)))
> (lambda (a b) (cond (... ...) (t ...)))(# # no buffer>)
> sort((#) (lambda (a b) (cond (... ...) (t ...
> (setq entries (sort entries (lambda ... ...)))
> (let* ((action ...) (org-log-refile ...) (entries ...) redo-at-end cmd rfloc
> state e tag pos (cnt 0) (cntskip 0)) (cond (... ...) (... ...) (... ... ...
> ...) (... ... ...) (... ... ...) (... ...) (... ...) (... ...) (t ...)) (setq
> entries (sort entries ...)) (while (setq e ...) (setq pos ...) (if ... ...
> ... ... ... ...)) (setq org-agenda-bulk-marked-entries nil)
> (org-agenda-bulk-remove-all-marks) (when redo-at-end (org-agenda-redo))
> (message "Acted on %d entries%s" cnt (if ... "" ...)))
> org-agenda-bulk-action((4))
> call-interactively(org-agenda-bulk-action nil nil)
>
>
> Emacs : GNU Emacs 23.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.35)
> of 2011-03-09 on black.porkrind.org
> Package: Org-mode version 7.5 (release_7.5.135.g7021f.dirty)
>
> current state:
> ==
> (setq
> org-agenda-deadline-leaders '("D: " "D%d: ")
> org-clock-in-switch-to-state "STARTED"
> org-agenda-skip-scheduled-if-deadline-is-shown t
> org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
> org-todo-keyword-faces '(("TODO" :foreground "medium blue" :weight bold)
> ("APPT" :foreground "medium blue" :weight bold)
> ("NOTE" :foreground "brown" :weight bold) ("STARTED"
> :foreground "dark orange" :weight bold)
> ("WAITING" :foreground "red" :weight bold)
> ("DELEGATED" :foreground "dark violet" :weight bold)
> ("DEFERRED" :foreground "dark blue" :weight bold)
> ("SOMEDAY" :foreground "dark blue" :weight bold)
> ("PROJECT" :height 1.5 :weight bold :foreground
> "black"))
> org-speed-command-hook '(org-speed-command-default-hook
> org-babel-speed-command-hook)
> org-agenda-custom-commands '(("E" "Errands (next 3 days)" tags
>
> "Errand&TODO<>\"DONE\"&TODO<>\"CANCELLED\"&STYLE<>\"habit\"&SCHEDULED<\"<+3d>\""
> ((org-agenda-overriding-header "Errands (next 3
> days)")))
> ("A" "Priority #A tasks" agenda ""
> ((org-agenda-ndays 1)
> (org-agenda-overriding-header "Today's priority #A tasks: ")
>(org-agenda-skip-function (quote
> (org-agenda-skip-entry-if (quote notregexp) "\\=.*\\[#A\\]"
> )
> ("B" "Priority #A and #B tasks" agenda ""
> ((org-agenda-ndays 1)
> (org-agenda-overriding-header "Today's priority #A and #B tasks: ")
>(org-agenda-skip-function (quote
> (org-agenda-skip-entry-if (quote regexp) "\\=.*\\[#C\\]"
> )
> ("w" "Waiting/delegated tasks" tags
> "TODO=\"WAITING\"|TODO=\"DELEGATED\""
> ((org-agenda-overriding-header
> "Waiting/delegated tasks:")
>(org-agenda-sorting-strategy (quote
> (todo-state-up priority-down category-up
> )
> ("u" "Unscheduled tasks" tags
>
> "TODO<>\"\"&TODO<>\"DONE\"&TODO<>\"CANCELLED\"&TODO<>\"NOTE\"&CATEGORY<>{CEG\\|ABC\\|Bizcard\\|Adagio\\|EVAprint\\|\\}"
> ((org-agenda-overriding-header "Unscheduled
> tasks: ")
>
>
>
> (org-agenda-skip-function
>
>
>
> (quote
>
>
>
>
>
> (org-agenda-skip-entry-if
>
>
[O] [PATCH] Fix typo in agenda local variable
* lisp/org-agenda.el (org-agenda-filter-by-tag): Fix variable name typo maybe-reftresh -> maybe-refresh --- This patch is available at git://git.norang.ca/org-mode.git fix-agenda-var-typo -Bernt lisp/org-agenda.el | 10 +- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 5571838..321221d 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -5905,7 +5905,7 @@ to switch to narrowing." (effort-prompt "") (inhibit-read-only t) (current org-agenda-filter) -maybe-reftresh a n tag) +maybe-refresh a n tag) (unless char (message "%s by tag [%s ], [TAB], %s[/]:off, [+-]:narrow, [>== char ?0) (<= char ?9) @@ -5974,9 +5974,9 @@ to switch to narrowing." (cons (concat (if strip "-" "+") tag) (if narrow current nil))) (org-agenda-filter-apply org-agenda-filter) - (setq maybe-reftresh t)) + (setq maybe-refresh t)) (t (error "Invalid tag selection character %c" char))) -(when (and maybe-reftresh +(when (and maybe-refresh (eq org-agenda-clockreport-mode 'with-filter)) (org-agenda-redo -- 1.7.5.rc0.100.gcb35c0
Re: [O] Display missing/overlapping clock ranges
Paul Mead writes: > Rainer Stengele writes: > >> I do clock every task I work on during the whole day. >> At the end of the day or week I have to go over all clock entries in my >> agenda >> and see if there are holes or overlappings in my clock tables. >> If yes I have to adjust the clocks. >> >> I read Bernt Hansen's comments on how he works with clocks >> (http://doc.norang.ca/org-mode.html#Clocking). >> >> What about a function showing the lacking clock ranges over >> the day while being in the agenda with log mode on? >> >> The function could even check for overlapping clock ranges and indicate these >> or jump to these. >> >> Maybe it would even be good to be able to configure daily and weekly >> regular holes in the ranges, for example >> >> - daily lunch time from [12:00]--[13:00] >> - week end days (maybe with diary syntax) >> - working days (Monday to Friday for example) >> >> What do you think? >> >> -- Rainer > > I'd defintely use something which identified the gaps and overlaps as > they're taking some time to find now that I have to account more closely > for my time! I've been considering whether to raise this for a > while. The 'regular holes' idea is good to, although not as important > for me. > > Paul Hi Rainer and Paul, Locating gaps would be useful. I've been meaning to investigate this but haven't spent any time on it yet. With my current clocking setup I've found I get very few holes. Checking the times is a task I do manually just before billing for my time. I currently just use a visual scan of the daily agenda(s) including clocking lines displayed ensuring that the start and end times match over the clocking period. It should be possible to automate the check. How should a filtered agenda be handled? I expect you'd want to see the gaps for the entries that are filtered away otherwise it's only really meaningful when you look at the entire clocking data. The major problem I used to have was clocks that would be opened and never closed. These were bad because they count as 0 minutes and without fixing those entries I don't bill for that time. Since the invention of M-x org-resolve-clocks (which runs everytime I clock in) I now find these open clocks quickly and don't need to reconstruct the data a week later. I haven't had this problem in a long time. Maybe something like the following mock up? --8<---cut here---start->8--- Day-agenda (W15): Wednesday 13 April 2011 todo:7:09- 7:11 Clocked: (0:02) Organization :PERSONAL:: 7:11- 8:00 - Gap -> (0:49) org: 8:00- 8:12 Clocked: (0:12) DONE Try to fix this bug :ORG:WORK:tuning:: todo:8:12- 8:26 Clocked: (0:14) Organization :PERSONAL:: diary: 8:26- 9:06 Clocked: (0:40) Breakfast todo:9:06- 9:30 Clocked: (0:24) Task A :PERSONAL:: 9:30-10:58 - Gap -> (1:28) 10:00.. todo: 10:58-11:11 Clocked: (0:13) Organization :PERSONAL:: vvv -- Overlap -- vvv todo: 11:11-11:12 Clocked: (0:01) Read Mail and News :PERSONAL:: todo: 11:10-11:14 Clocked: (0:01) Organization :PERSONAL:: ^^^ -- Overlap -- ^^^ todo: 11:14-11:15 Clocked: (0:01) Read Mail and News :PERSONAL:: todo: 11:15-11:16 Clocked: (0:01) Organization :PERSONAL:: 12:00.. 14:00.. 16:00.. 11:16-16:33 - Gap -> (5:17) todo: 16:33.. Clocked: (-) Read Mail and News :PERSONAL:: 16:43.. now - - - - - - - - - - - - - - - - - - - - - - - - - 18:00.. 20:00.. --8<---cut here---end--->8--- Regards, Bernt
[O] Unable to use M-Ret from line-wrapped relative time items
Hi,
I am an inexperienced org-mode user, so my apologies if this bug report
falls short, or is submitted to the wrong forum.
I've been experiencing an annoying bug/break since upgrading to OrgMode
7.5. I'm running it on GNU Emacs 22.3.1 (i386-apple-darwin9, Carbon
Version 1.6.0).
When I am using a relative timer, I can usually hit M-Ret at the end of
the current item, to create a new time-stamped item (I'm using [X] for
point):
- 0:02:04 :: foo[X]
This leads to a new timestamp item:
- 0:02:04 :: foo
- 0:02:06 ::
But when the text of the second note gets to be too long, Emacs wraps
the text to the next line (I have the Fill minor mode active). Trying to
use M-Ret from the end of the second line of the second item leads to
the attached break/backtrace:
- 0:02:04 :: foo
- 0:02:06 :: bar bar bar bar bar bar bar bar bar bar bar bar bar bar
bar[X]
Any ideas on how to fix this bug/break? Do I merely need to upgrade my
version of GNU Emacs?
Thank you for your time & help,
~Tomer
Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
<=(13 nil)
(cond ((>= ... lim-down) (throw ... ...)) ((get-text-property ... ...)
(goto-char ...)) ((and ... ...) (throw ... ...)) ((looking-at "^[
]*#\\+begin_") (re-search-forward "^[ ]*#\\+end_") (forward-line 1))
((looking-at drawers-re) (re-search-forward "^[ ]*:END:" nil t) (forward-line
1)) ((and inlinetask-re ...) (org-inlinetask-goto-end)) ((looking-at "^[ ]*$")
(forward-line 1)) ((looking-at item-re) (push ... itm-lst-2) (push ...
end-lst-2) (forward-line 1)) ((eq org-list-ending-method ...) (forward-line 1))
((<= ind ...) (throw ... ...)) ((<= ind ...) (push ... end-lst-2) (forward-line
1)) (t (forward-line 1)))
(let ((ind ...)) (cond (... ...) (... ...) (... ...) (... ... ...) (... ...
...) (... ...) (... ...) (... ... ... ...) (... ...) (... ...) (... ... ...) (t
...)))
(while t (let (...) (cond ... ... ... ... ... ... ... ... ... ... ... ...)))
(catch (quote exit) (while t (let ... ...)))
(let* ((case-fold-search t) (context ...) (lim-up ...) (lim-down ...)
(text-min-ind 1) (item-re ...) (drawers-re ...) (inlinetask-re ...)
(beg-cell ...) ind itm-lst itm-lst-2 end-lst end-lst-2 struct (assoc-at-point
...) (end-before-blank ...)) (save-excursion (catch ... ...)) (catch (quote
exit) (while t ...)) (setq struct (append itm-lst ...)) (setq end-lst (append
end-lst ...)) (let (...) (mapc ... struct)) (org-list-struct-assoc-end struct
end-lst) struct)
(save-excursion (beginning-of-line) (let* (... ... ... ... ... ... ... ...
... ind itm-lst itm-lst-2 end-lst end-lst-2 struct ... ...) (save-excursion
...) (catch ... ...) (setq struct ...) (setq end-lst ...) (let ... ...)
(org-list-struct-assoc-end struct end-lst) struct))
org-list-struct()
(let* ((struct ...) (prevs ...) (s ...)) (setq struct (org-list-insert-item
... struct prevs nil s)) (org-list-write-struct struct (org-list-parents-alist
struct)) (looking-at org-list-full-item-re) (goto-char (match-end 0)))
(cond ((and itemp ...) (let* ... ... ... ... ...)) (itemp (error "This is not
a timer list")) (t (beginning-of-line) (org-indent-line-function) (insert "- ")
(org-timer ...) (insert ":: ")))
(let ((itemp ...)) (cond (... ...) (itemp ...) (t ... ... ... ... ...)))
org-timer-item()
(progn (org-timer-item) t)
(if (save-excursion (goto-char itemp) (org-at-item-timer-p)) (progn
(org-timer-item) t) (goto-char itemp) (let* (... ... ... ...) (setq struct ...)
(org-list-write-struct struct ...) (when checkp ...) (looking-at
org-list-full-item-re) (goto-char ...) t))
(if (or (not itemp) (save-excursion ... ...)) nil (if (save-excursion ...
...) (progn ... t) (goto-char itemp) (let* ... ... ... ... ... ... t)))
(unless (or (not itemp) (save-excursion ... ...)) (if (save-excursion ...
...) (progn ... t) (goto-char itemp) (let* ... ... ... ... ... ... t)))
(let ((itemp ...) (pos ...)) (unless (or ... ...) (if ... ... ... ...)))
org-insert-item()
(not (org-insert-item))
(or force-heading (not (org-insert-item)))
(if (or force-heading (not ...)) (progn (let* ... ... ... ... ... ... ... ...
...)))
(when (or force-heading (not ...)) (let* (... ... ... ... ... ... pos
hide-previous previous-pos) (cond ... ... ...) (insert head) (just-one-space)
(setq pos ...) (end-of-line 1) (unless ... ... ...) (when ... ...) (run-hooks
...)))
(if (or (= ... 0) (and ... ...)) (progn (insert "\n* ") (run-hooks ...))
(when (or force-heading ...) (let* ... ... ... ... ... ... ... ... ...)))
org-insert-heading(nil)
call-interactively(org-insert-heading)
(cond ((run-hook-with-args-until-success ...)) ((org-at-table-p)
(call-interactively ...)) (t (call-interactively ...)))
org-meta-return(nil)
call-interactively(org-meta-return)
recursive-edit()
byte-code("Æ @Ç=! ÈÉÊ\"ËÉ!A@)¢Ì=! ÈÍÊ\"Î !Ï Ð!\fc Ñed\"
VW ebÒ
¥y` dbÒ
¥
Zy`|)ÓcebÔÕÖ \"× ÔØ!ÙÊ ÔØ!Ú +Ù" [unread-co
Re: [O] org-babel (org-babel-detangle)
"Eric Schulte" writes: Hi Eric, Thanks for this swift reply. I will try :) Best regards, Mohamed > Hi Mohamed, > > You have a small typo in your header arguments, ":comment" should be > ":comments". After that change then code block should be tangled > wrapped in comments, and then Babel can use these comments to jump back > to the original org-mode file. > > That said, the detangle mechanisms are in need of some work, > specifically regarding their use of the Org-mode's link resolution, > which doesn't currently make it possible to programmatically jump to the > results of a link. So, until some time is spent fixing up the > detangling machinery inside of Babel, you may not find detangling to be > extremely robust. > > Best -- Eric > > Mohamed HIBTI writes: > >> Dear all, >> I have a problem with detangling org-babel fragments. >> May be this is because XML is not a supported feature/or I use it in a wrong >> way. >> Any help is welcome. >> >> My org-file is below. I can tangle this file to obtain the XML file but >> when I try to jump to org I get the message "not in tangled code". >> >> *** TODO Question that needs validation >> :PROPERTIES: >> :ID: 2788f65d-5613-40c1-80ae-ae966f4bb398 >> :END: >> #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes >> >> >> >> AC Power System Bus 2 >> >> AC Power System Bus 2 fails >> >> >> >> >> >> >> #+END_SRC >> >> Best regards, >> >> Mohamed >> >> >>
Re: [O] org-babel (org-babel-detangle)
Hi Mohamed, You have a small typo in your header arguments, ":comment" should be ":comments". After that change then code block should be tangled wrapped in comments, and then Babel can use these comments to jump back to the original org-mode file. That said, the detangle mechanisms are in need of some work, specifically regarding their use of the Org-mode's link resolution, which doesn't currently make it possible to programmatically jump to the results of a link. So, until some time is spent fixing up the detangling machinery inside of Babel, you may not find detangling to be extremely robust. Best -- Eric Mohamed HIBTI writes: > Dear all, > I have a problem with detangling org-babel fragments. > May be this is because XML is not a supported feature/or I use it in a wrong > way. > Any help is welcome. > > My org-file is below. I can tangle this file to obtain the XML file but > when I try to jump to org I get the message "not in tangled code". > > *** TODO Question that needs validation > :PROPERTIES: > :ID: 2788f65d-5613-40c1-80ae-ae966f4bb398 > :END: > #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes > > > > AC Power System Bus 2 > > AC Power System Bus 2 fails > > > > > > > #+END_SRC > > Best regards, > > Mohamed > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Complex numbers
Renier Marchand writes: > I have found the following way to reference my data correctly without > having to quote it or have data rewritten. > > I do: > > #+tblname: my-data > | hmin | > |--| > | | > | 0.05 | > | 0.2 | > | 0.2 | > #+TBLFM: @5$1='(sbe "myfunc" (data "my-data[3:4,0]")) > > This also works for complex data as you suggested. > Very cool, I would never have thought to use a reference within a table formula. > > But is there a way to refer in the formula to the current table > instead of a specific table? Because this would obviously not work for > multiple tables with the same name. (i.e. copy and paste for another > dataset) > No, there is no support for that sort of usage, and adding such a position dependent reference would be a fairly large change from the existing reference resolution mechanisms. Best -- Eric > > Regards, > > Renier > > On Wed, Apr 13, 2011 at 5:52 AM, Eric Schulte wrote: >> Hi Renier, >> >> The Org-mode table machinery is interpreting the values of your table >> cells as emacs lisp (given that the table formula is an elisp, rather >> than a calc formula). Due to the "," the result is a weird nested list >> which confuses your python code block. Some options here include... >> >> 1. wrapping these cells in quotes so that they are passed to the python >> block as strings... >> >> #+source: parameter-variation(data=0) >> #+begin_src python :result values >> return 'text' >> #+end_src >> >> |---| >> | "(0.0331901438056,0.000535222885197)" | >> | "(0.0333434157791,0.000537930174356)" | >> | "(0.0345727512157,0.000559346040457)" | >> | "(0.0353146483908,0.000571501584524)" | >> | "(0.0355522909393,0.000574387067408)" | >> | "(0.0356575682336,0.000574851263615)" | >> | "(0.0357806926897,0.000575051685084)" | >> |---| >> | text | >> #+TBLFM: @8$1='(sbe parameter-variation (nums @1$1..@7$1)) >> >> 2. referencing the table from an external code block, rather than inside >> of a table formula. This is probably the easier solution, but it >> doesn't insert the result into your table, unless you do something >> tricky like give the code block and the table the same name so that >> the results of the code block replace the table... >> >> #+results: complex-data >> |-| >> | (0.0331901438056,0.000535222885197) | >> | (0.0333434157791,0.000537930174356) | >> | (0.0345727512157,0.000559346040457) | >> | (0.0353146483908,0.000571501584524) | >> | (0.0355522909393,0.000574387067408) | >> | (0.0356575682336,0.000574851263615) | >> | (0.0357806926897,0.000575051685084) | >> #+TBLFM: @8$1='(sbe parameter-variation (nums @1$1..@7$1)) >> >> #+begin_src python :var data=complex-data >> return data >> #+end_src >> >> Hope this helps -- Eric >> >> Renier Marchand writes: >> >>> Hi. >>> >>> I have been playing around with complex data that has been returned >>> from Python. This is obviously not in calc.el format but if I change >>> them to the correct format I can manipulate them using calc. >>> >>> but >>> >>> When I want to pass the complex numbers (python format) to python I >>> get an error. If I pass real number everything works as expected >>> >>> For example: >>> >>> #+source: parameter-variation(data=0) >>> #+begin_src python :result values >>> return 'text' >>> #+end_src >>> >>> >>> | | hmin | | >>> |---+---+-| >>> | | | | >>> | | 0.05 | (0.0331901438056,0.000535222885197) | >>> | | 0.1 | (0.0333434157791,0.000537930174356) | >>> | | 0.3 | (0.0345727512157,0.000559346040457) | >>> | | 0.6 | (0.0353146483908,0.000571501584524) | >>> | | 0.9 | (0.0355522909393,0.000574387067408) | >>> | | 1.2 | (0.0356575682336,0.000574851263615) | >>> | | 10.0 | (0.0357806926897,0.000575051685084) | >>> | $ | x=0.1 | y=0.1 | >>> | | text | | >>> #+TBLFM: @11$2='(sbe "parameter-variation" (data >>> @3$2..@9$2))::@11$3='(sbe "parameter-variation" (data @3$3..@9$3)) >>> >>> i.e. I get the word 'text' returned for column 2 where there are real >>> numbers but I don't get anything returned where there are complex >>> numbers. As you can see, there are no actual calculation performed on >>> the data I am just returning 'text' so I am expecting it to work in >>> both instances. >>> >>> The debug sessions show the following for the real column: >>> >>> Substitution history of formula >>> Orig: '(sbe "parameter-variation" (data @3$2..@9$2)) >>> $xyz-> '(sbe "parameter-variation" (data @3$2..@9$2)) >>> @r$c-> '(sbe "param
Re: [O] Display missing/overlapping clock ranges
Rainer Stengele writes: > Hi all! > > I do clock every task I work on during the whole day. > At the end of the day or week I have to go over all clock entries in my agenda > and see if there are holes or overlappings in my clock tables. > If yes I have to adjust the clocks. > > I read Bernt Hansen's comments on how he works with clocks > (http://doc.norang.ca/org-mode.html#Clocking). > > What about a function showing the lacking clock ranges over > the day while being in the agenda with log mode on? > > The function could even check for overlapping clock ranges and indicate these > or jump to these. > > Maybe it would even be good to be able to configure daily and weekly > regular holes in the ranges, for example > > - daily lunch time from [12:00]--[13:00] > - week end days (maybe with diary syntax) > - working days (Monday to Friday for example) > > What do you think? > > -- Rainer I'd defintely use something which identified the gaps and overlaps as they're taking some time to find now that I have to account more closely for my time! I've been considering whether to raise this for a while. The 'regular holes' idea is good to, although not as important for me. Paul
Re: [O] Occurance property, or some similar name?
On 12.4.2011, at 22:00, Memnon Anon wrote: > Hi, > Christopher Allan Webber writes: > >> I was once one of the many people who apparently originally >> misunderstood what "SCHEDULED" meant, and used to set it to like, an >> appointment time. > > Well, you can use it that way. > The point is: Scheduled items behave differently to timestamped items. > If you prefer the behaviour scheduling provides you with, go for it. > >> I kind of miss how nice it was back when I misunderstood how events work >> (escept for all of those non-TODOs staying around forever on my >> agenda..) where I had a dedicated property for this, and pressing >> C-c C-s would always change that property. > > I just did a quick check. > It seems to me that timestamps within a property work. > So, if you prefer, you can set your timestamps in a property like this: > > * NEXT Task 2 > :LOGBOOK: > :END: > :PROPERTIES: > :DATE: <2011-04-12> > :END: > > If you want a convenient keybinding to set this property, this seems > to work: > > --8<---cut here---start->8--- > (defun my-org-set-date () > "Set DATE Property via org-read-date." > (interactive) > (org-set-property "DATE" (concat "<"(org-read-date)">"))) > > (define-key org-mode-map (kbd "C-c C-S-s") 'my-org-set-date) > --8<---cut here---end--->8--- > > Okay, there is still setting it in the agenda. > There are already functions doing special treatment for e.g. effort. > It should work to grab it and modify it to our needs ... > > --8<---cut here---start->8--- > (defun my-org-agenda-set-date () > "Set the DATE property for the current headline." > (interactive) > (org-agenda-check-no-diary) > (org-agenda-show) ;;; FIXME This is a stupid hack and should not be needed > (let* ((hdmarker (or (org-get-at-bol 'org-hd-marker) > (org-agenda-error))) >(buffer (marker-buffer hdmarker)) >(pos (marker-position hdmarker)) >(inhibit-read-only t) >newhead) >(org-with-remote-undo buffer > (with-current-buffer buffer > (widen) > (goto-char pos) > (save-excursion > (org-show-context 'agenda)) > (save-excursion > (and (outline-next-heading) > (org-flag-heading nil))) ; show the next heading > (goto-char pos) > (call-interactively 'my-org-set-date) > (end-of-line 1) > > (define-key org-agenda-keymap (kbd "C-c C-S-s") 'my-org-agenda-set-date) > --8<---cut here---end--->8--- That looks like it should work. I did some quick checking - I believe it would be possible to make DEADLINE, SCHEDULED and CLOSED properties instead of having them in the second line. You and Matt have just shown that an arbitrary property (like appointment) can serve as the standard date of an entry. The parser that is looking for CLOSED, SCHEDULED, DEADLINE is lenient and does not mind if there is an additional colon in front of the keyword. So if you have a (currently not allowed) :SCHEDULED: property, it will behave correctly when constructing the agenda. If I am not mistaken, we could introduce (not-trivial, but likely without major headaches) an option like org-planning-use-properties or so. Much will work out of the box. The places where changes are needed are these functions: org-add-planning-info org-entry-put org-entry-get org-entry-properties The main problem would be that it would not be trivial to have mixed entries - user would have to make a decision if they want planning info in the property drawer or not. Things would not work well or require a lot of extra checking with files that as mixed (agenda production would work OK, but changing dates may cause problems. But I guess this could be handled one way or another. As I have explained earlier, to have planning info like tags and the TODO keyword outside of drawers has historic reasons, but it is also good for newcomers. - Carsten > > Did some quick testing, it *seems* to work. > But I have no expertise in elisp (or programming for that matter), so > this is probably "wrong" in one way or the other :). > >> What I'm saying I guess is: >> - Is there a popular property name for when something should be >> happening, in a non-TODO way? I've thought of "OCCURANCE" but maybe >> that isn't the best (I suspect not) >> - Maybe if we formalize this property, we should make a command for it? >> Maybe C-c C-S-o? >> - It would be nice to formalize this so we could actually steer people >> in the right direction in the docs. > > Oh, this was not a "How can I do x?" mail, but a request to formalize > this in org core > > Nevermind ;) > > Memnon > >
Re: [O] Occurance property, or some similar name?
Michael Brand writes: > On Wed, Apr 13, 2011 at 16:43, Christopher Allan Webber > Are your concerns concrete? > > I have thought about and tested this already before: The three example > items above show up in the agenda, and are still correct even after > changing with `S->'. So this "newer/future" Org file format works even > with the "older/today" Org software. This is because the Org software > of today flexibly binds the special property TIMESTAMP per item to the > first active timestamp (i. e. "<>", not "[]") that is not prefixed > with `SCHEDULED: ' or `DEADLINE: '. This binding is the reason why I > would stick to the name TIMESTAMP when it comes to possibly new > features that should write this special property keyword explicitly > for this kind of timestamp. The sibling (not `C-c .') of `C-c > C-s'/`C-c C-d' that you suggested originally would be such a feature. > > Michael That's interesting, and no, my concerns weren't concrete. I just tried inserting the timestamp property via C-c C-x p and saw that it error'ed, and wondered if there were further blocks around orgmode's system than just the property insertion tools. -- The bottom line.
[O] Display missing/overlapping clock ranges
Hi all! I do clock every task I work on during the whole day. At the end of the day or week I have to go over all clock entries in my agenda and see if there are holes or overlappings in my clock tables. If yes I have to adjust the clocks. I read Bernt Hansen's comments on how he works with clocks (http://doc.norang.ca/org-mode.html#Clocking). What about a function showing the lacking clock ranges over the day while being in the agenda with log mode on? The function could even check for overlapping clock ranges and indicate these or jump to these. Maybe it would even be good to be able to configure daily and weekly regular holes in the ranges, for example - daily lunch time from [12:00]--[13:00] - week end days (maybe with diary syntax) - working days (Monday to Friday for example) What do you think? -- Rainer
Re: [O] Occurance property, or some similar name?
On Wed, Apr 13, 2011 at 16:43, Christopher Allan Webber wrote: > Michael Brand writes: >> * _appointment_ that _occurs_ at bike shop (keyword inside drawer) >> :PROPERTIES: >> :TIMESTAMP: <2011-04-12 Tue 19:00> >> :END: >> * _appointment_ that _occurs_ at bike shop (keyword outside drawer) >> :TIMESTAMP: <2011-04-12 Tue 19:00> >> * _appointment_ that _occurs_ at bike shop (keyword-less, at least for >> backward compatibility) >> <2011-04-12 Tue 19:00> > > Interesting, I like that style. My main concern is that newer orgmode > files written in this form might break in older versions of orgmode. Are your concerns concrete? I have thought about and tested this already before: The three example items above show up in the agenda, and are still correct even after changing with `S->'. So this "newer/future" Org file format works even with the "older/today" Org software. This is because the Org software of today flexibly binds the special property TIMESTAMP per item to the first active timestamp (i. e. "<>", not "[]") that is not prefixed with `SCHEDULED: ' or `DEADLINE: '. This binding is the reason why I would stick to the name TIMESTAMP when it comes to possibly new features that should write this special property keyword explicitly for this kind of timestamp. The sibling (not `C-c .') of `C-c C-s'/`C-c C-d' that you suggested originally would be such a feature. Michael
Re: [O] Occurance property, or some similar name?
Michael Brand writes: > Yes, I suggest to remove this limitation and would prefer TIMESTAMP > much over OCCURANCE, APPOINTMENT (not every occurrance is an > appointment) or any other name to avoid a second name for the same > behavior of the existing special property TIMESTAMP and to avoid > confusions/collisions at other places like e. g. selecting a property > for a column view. In the sense of special properties I also suggest > to allow different formats: > > * _appointment_ that _occurs_ at bike shop (keyword inside drawer) > :PROPERTIES: > :TIMESTAMP: <2011-04-12 Tue 19:00> > :END: > * _appointment_ that _occurs_ at bike shop (keyword outside drawer) > :TIMESTAMP: <2011-04-12 Tue 19:00> > * _appointment_ that _occurs_ at bike shop (keyword-less, at least for > backward compatibility) > <2011-04-12 Tue 19:00> > Interesting, I like that style. My main concern is that newer orgmode files written in this form might break in older versions of orgmode. -- The bottom line.
Re: [O] Occurance property, or some similar name?
On Wed, Apr 13, 2011 at 15:08, Christopher Allan Webber wrote: > Michael Brand writes: > >> The name could be critical. To avoid any confusions/collisions I would >> recommend to use just that name TIMESTAMP for easy get/set access: >> >> * _appointment_ that _occurs_ at bike shop >> :PROPERTIES: >> :TIMESTAMP: <2011-04-12 Tue 19:00> >> :END: >> > > Maybe you're already aware, but since TIMESTAMP is a "special property" > it currently isn't legal to use it as a property. But maybe you're > suggesting changing that? Yes, I suggest to remove this limitation and would prefer TIMESTAMP much over OCCURANCE, APPOINTMENT (not every occurrance is an appointment) or any other name to avoid a second name for the same behavior of the existing special property TIMESTAMP and to avoid confusions/collisions at other places like e. g. selecting a property for a column view. In the sense of special properties I also suggest to allow different formats: * _appointment_ that _occurs_ at bike shop (keyword inside drawer) :PROPERTIES: :TIMESTAMP: <2011-04-12 Tue 19:00> :END: * _appointment_ that _occurs_ at bike shop (keyword outside drawer) :TIMESTAMP: <2011-04-12 Tue 19:00> * _appointment_ that _occurs_ at bike shop (keyword-less, at least for backward compatibility) <2011-04-12 Tue 19:00> With this I imagine that reading and writing the special property TIMESTAMP would address the first found with the chosen format or, if not found, for writing create one with the chosen format. The chosen format would of course default to the now only format "keyword-less", or with e. g. #+SPECIAL_PROPERTIES: TIMESTAMP=drawer:PROPERTIES <= example syntax only to get an idea could be changed to the first format "keyword inside drawer". The format "keyword-less" seems to overlap with the others which might need some more care. See also http://thread.gmane.org/gmane.emacs.orgmode/40801/focus=40813 Michael
[O] org-babel (org-babel-detangle)
Dear all, I have a problem with detangling org-babel fragments. May be this is because XML is not a supported feature/or I use it in a wrong way. Any help is welcome. My org-file is below. I can tangle this file to obtain the XML file but when I try to jump to org I get the message "not in tangled code". *** TODO Question that needs validation :PROPERTIES: :ID: 2788f65d-5613-40c1-80ae-ae966f4bb398 :END: #+BEGIN_SRC XML :tangle ./sample04.xml :comment yes AC Power System Bus 2 AC Power System Bus 2 fails #+END_SRC Best regards, Mohamed
Re: [O] Occurance property, or some similar name?
Michael Brand writes: > The name could be critical. To avoid any confusions/collisions I would > recommend to use just that name TIMESTAMP for easy get/set access: > > * _appointment_ that _occurs_ at bike shop > :PROPERTIES: > :TIMESTAMP: <2011-04-12 Tue 19:00> > :END: > Maybe you're already aware, but since TIMESTAMP is a "special property" it currently isn't legal to use it as a property. But maybe you're suggesting changing that? -- 𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
Re: [O] Occurance property, or some similar name?
Matt Lundin writes: > O.K. I wasn't clear what you meant by property in the original post. > What about :APPOINTMENT:? "Appointment" makes a lot of sense. +1. Better than "occurance" I think. :) -- The bottom line.
Re: [O] Recurring events with ranges broken
On Apr 13, 2011, at 11:35 AM, Philipp M. wrote: > I apologize for the poor wording of my mail. > > > On 11 April 2011 10:18, Giovanni Ridolfi wrote: > "Philipp M." writes: > > Hi, Philipp, > > In the recent org-mode realease something > could ou be more precise, please? > > In org-mode 7.5. > > > recurring ranges with timestamps > > are not properly recognized in the agenda. > > This wont work: > > <2011-04-07 Thu +1w>--<2011-04-20 Wed> > uh! Has it ever worked ?-) > > and > > Could you please give us an idea approximately > when it was working? > > I don't think it ever worked. > > Could you also, please, explain to me what's the > rationale behind this kind of time range? > Why do intend to use it? > > It would be the proper way to set up timetables for a semester. > The workaround I use is mentioned in the FAQ > http://orgmode.org/worg/org-faq.html#org-diary-class > Unfortunately the FAQ doesn't state that putting the time in the heading is > the only way to get the time into the agenda and that all other attempts you > might expect to do what you want break silently. > Also it doesn't state the drawbacks of doing it like this (exporting breaks). Since you have now figured it out, why don't you change the FAQ to reflect that knowledge? The FAQ is user-editable. - Carsten > > > The _repeater interval_, indicates that the event applies > not only on the given date, but again and again after a > certain interval. > > > <2011-04-07 Thu +1w>--<2011-04-20 Wed> > > when the first date is passed e.g. 21st of April <2011-04-21 Thr> > how can it match with a negative interval, since the second member is > at the <2011-04-20 Wed> ? > > > I hope the usecase explains how I would want that to work. > > > cheers, > Giovanni > > regards, > Philipp - Carsten
Re: [O] [PATCH] Fix agenda display when headlines are missing
Bernt Hansen writes: > Hi Richard, > > This should if your issue. Please test it and report back. ^^ fix > This patch is available at git://git.norang.ca/org-mode.git > fix-agenda-empty-headines > > Regards, > Bernt -Bernt
[O] [PATCH] Fix agenda display when headlines are missing
* lisp/org-agenda.el (org-agenda-get-timestamps): Fix agenda display when headlines are missing The following entry breaks the agenda display. , | | :PROPERTIES: | :DateCreated: <2011-04-13 Mi 10:00> | :END: | | [[gnus:nntp%2BGwene:gwene.org.emacsen.planet][gnus:nntp+Gwene:gwene.org.emacsen.planet]] ` Provide the empty string as the headline if the search for the headline returns nil. org-format-agenda-items requires a string for the headline parameter. --- Hi Richard, This should if your issue. Please test it and report back. This patch is available at git://git.norang.ca/org-mode.git fix-agenda-empty-headines Regards, Bernt lisp/org-agenda.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 5571838..768c417 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -4710,7 +4710,7 @@ This function is invoked if `org-agenda-todo-ignore-deadlines', (setq hdmarker (org-agenda-new-marker) tags (org-get-tags-at)) (looking-at "\\*+[ \t]+\\([^\r\n]+\\)") - (setq head (match-string 1)) + (setq head (or (match-string 1) "")) (setq txt (org-format-agenda-item (if inactivep org-agenda-inactive-leader nil) head category tags timestr -- 1.7.5.rc0.100.gcb35c0
[O] ascii export problem/bug?
When I start emacs and then edit an org file, ascii export fails (M-x org-export [return key] a). No export file is created and I see the following message: Autoloading failed to define function org-export-as-ascii But if I type: M-x org-customize then export works. The other way I can get this to work is to manually load org-ascii.el (which came with the org mode distribution). This is with org-mode version 7.5. Scott
Re: [O] Clock-in task when emacs starts
--8<---cut here---start->8--- (require 'org-id) (defun bh/clock-in-organization-task () (interactive) (bh/clock-in-task-by-id "eb155a82-92b2-4f25-a3c6-0304591af2f9")) (defun bh/clock-in-task-by-id (id) "Clock in a task by id" (save-restriction (widen) (org-with-point-at (org-id-find id 'marker) (org-clock-in '(16) --8<---cut here---end--->8--- Thanks Bernt, that is so cool. In fact I conceived something simillar but it dependent on exact headline name. Your version is way more versilite. Thanks!
Re: [O] Recurring events with ranges broken
I apologize for the poor wording of my mail. On 11 April 2011 10:18, Giovanni Ridolfi wrote: > "Philipp M." writes: > > Hi, Philipp, > > In the recent org-mode realease something > could ou be more precise, please? > In org-mode 7.5. > > recurring ranges with timestamps > > are not properly recognized in the agenda. > > This wont work: > > <2011-04-07 Thu +1w>--<2011-04-20 Wed> > uh! Has it ever worked ?-) > and Could you please give us an idea approximately > when it was working? > I don't think it ever worked. > Could you also, please, explain to me what's the > rationale behind this kind of time range? > Why do intend to use it? > It would be the proper way to set up timetables for a semester. The workaround I use is mentioned in the FAQ http://orgmode.org/worg/org -faq.html#org-diary-class Unfortunately the FAQ doesn't state that putting the time in the heading is the only way to get the time into the agenda and that all other attempts you might expect to do what you want break silently. Also it doesn't state the drawbacks of doing it like this (exporting breaks). > The _repeater interval_, indicates that the event applies > not only on the given date, but again and again after a > certain interval. > > > <2011-04-07 Thu +1w>--<2011-04-20 Wed> > > when the first date is passed e.g. 21st of April <2011-04-21 Thr> > how can it match with a negative interval, since the second member is > at the <2011-04-20 Wed> ? > > I hope the usecase explains how I would want that to work. > > cheers, > Giovanni > regards, Philipp
Re: [O] [BUG] HTML Export/Broken coderef links?
Oops, looks like I’m rather late. Scratch that. :-) Aankhen
Re: [O] [BUG] HTML Export/Broken coderef links?
On Tue, Apr 12, 2011 at 17:31, Jambunathan K wrote: > > On HTML export, I am unable to follow references to lines within the > code examples. > > Firefox complains with the following message: > > "Firefox doesn't know how to open this address; because the > protocol(coderef) isn't associated with any program." > > [snip] Try the attached patch for a quick fix. Works here. Aankhen fix-coderefs-in-html.patch Description: Binary data
Re: [O] Complex numbers
I have found the following way to reference my data correctly without
having to quote it or have data rewritten.
I do:
#+tblname: my-data
| hmin |
|--|
| |
| 0.05 |
| 0.2 |
| 0.2 |
#+TBLFM: @5$1='(sbe "myfunc" (data "my-data[3:4,0]"))
This also works for complex data as you suggested.
But is there a way to refer in the formula to the current table
instead of a specific table? Because this would obviously not work for
multiple tables with the same name. (i.e. copy and paste for another
dataset)
Regards,
Renier
On Wed, Apr 13, 2011 at 5:52 AM, Eric Schulte wrote:
> Hi Renier,
>
> The Org-mode table machinery is interpreting the values of your table
> cells as emacs lisp (given that the table formula is an elisp, rather
> than a calc formula). Due to the "," the result is a weird nested list
> which confuses your python code block. Some options here include...
>
> 1. wrapping these cells in quotes so that they are passed to the python
> block as strings...
>
> #+source: parameter-variation(data=0)
> #+begin_src python :result values
> return 'text'
> #+end_src
>
> |---|
> | "(0.0331901438056,0.000535222885197)" |
> | "(0.0333434157791,0.000537930174356)" |
> | "(0.0345727512157,0.000559346040457)" |
> | "(0.0353146483908,0.000571501584524)" |
> | "(0.0355522909393,0.000574387067408)" |
> | "(0.0356575682336,0.000574851263615)" |
> | "(0.0357806926897,0.000575051685084)" |
> |---|
> | text |
> #+TBLFM: @8$1='(sbe parameter-variation (nums @1$1..@7$1))
>
> 2. referencing the table from an external code block, rather than inside
> of a table formula. This is probably the easier solution, but it
> doesn't insert the result into your table, unless you do something
> tricky like give the code block and the table the same name so that
> the results of the code block replace the table...
>
> #+results: complex-data
> |-|
> | (0.0331901438056,0.000535222885197) |
> | (0.0333434157791,0.000537930174356) |
> | (0.0345727512157,0.000559346040457) |
> | (0.0353146483908,0.000571501584524) |
> | (0.0355522909393,0.000574387067408) |
> | (0.0356575682336,0.000574851263615) |
> | (0.0357806926897,0.000575051685084) |
> #+TBLFM: @8$1='(sbe parameter-variation (nums @1$1..@7$1))
>
> #+begin_src python :var data=complex-data
> return data
> #+end_src
>
> Hope this helps -- Eric
>
> Renier Marchand writes:
>
>> Hi.
>>
>> I have been playing around with complex data that has been returned
>> from Python. This is obviously not in calc.el format but if I change
>> them to the correct format I can manipulate them using calc.
>>
>> but
>>
>> When I want to pass the complex numbers (python format) to python I
>> get an error. If I pass real number everything works as expected
>>
>> For example:
>>
>> #+source: parameter-variation(data=0)
>> #+begin_src python :result values
>> return 'text'
>> #+end_src
>>
>>
>> | | hmin | |
>> |---+---+-|
>> | | | |
>> | | 0.05 | (0.0331901438056,0.000535222885197) |
>> | | 0.1 | (0.0333434157791,0.000537930174356) |
>> | | 0.3 | (0.0345727512157,0.000559346040457) |
>> | | 0.6 | (0.0353146483908,0.000571501584524) |
>> | | 0.9 | (0.0355522909393,0.000574387067408) |
>> | | 1.2 | (0.0356575682336,0.000574851263615) |
>> | | 10.0 | (0.0357806926897,0.000575051685084) |
>> | $ | x=0.1 | y=0.1 |
>> | | text | |
>> #+TBLFM: @11$2='(sbe "parameter-variation" (data
>> @3$2..@9$2))::@11$3='(sbe "parameter-variation" (data @3$3..@9$3))
>>
>> i.e. I get the word 'text' returned for column 2 where there are real
>> numbers but I don't get anything returned where there are complex
>> numbers. As you can see, there are no actual calculation performed on
>> the data I am just returning 'text' so I am expecting it to work in
>> both instances.
>>
>> The debug sessions show the following for the real column:
>>
>> Substitution history of formula
>> Orig: '(sbe "parameter-variation" (data @3$2..@9$2))
>> $xyz-> '(sbe "parameter-variation" (data @3$2..@9$2))
>> @r$c-> '(sbe "parameter-variation" (data #("0.05" 0 4 (fontified t
>> face org-table)) #("0.1" 0 3 (fontified t face org-table)) #("0.3" 0 3
>> (fontified t face org-table)) #("0.6" 0 3 (fontified t face
>> org-table)) #("0.9" 0 3 (fontified t face org-table)) #("1.2" 0 3
>> (fontified t face org-table)) #("10.0" 0 4 (fontified t face
>> org-table
>> $1-> '(sbe "parameter-variation" (data #("0.05" 0 4 (fontified t
>> face org-table)) #("0.1" 0 3 (fontified
Re: [O] Occurance property, or some similar name?
On Tue, Apr 12, 2011 at 22:52, Christopher Allan Webber wrote: > ** Pick up bike from the shop > :PROPERTIES: > :OCCURANCE: <2011-04-12 Tue 19:00> > :END: > > etc. > > It's nice to know there's a meta-property for TIMESTAMP, but I'm > specifically looking for a nice place to put that timestamp away. This > is for cleanliness / easy get-set purposes. The name could be critical. To avoid any confusions/collisions I would recommend to use just that name TIMESTAMP for easy get/set access: * _appointment_ that _occurs_ at bike shop :PROPERTIES: :TIMESTAMP: <2011-04-12 Tue 19:00> :END: > I'm partly trying to see if other people want this as much as I do. > Surely I'm not the only one who finds putting active timestamps on the > headline or scattered just anywhere in the entry kind of gross? I would like to have generally some special properties case by case inside _or_ outside of the properties drawer, like e. g. CLOSED, CATEGORY, TAG etc. See also the current discussion http://thread.gmane.org/gmane.emacs.orgmode/40801/focus=40813 and the similar discussion linked there. In this case of TIMESTAMP it would be allowed e. g. * _appointment_ that _occurs_ at bike shop (keyword inside drawer) :PROPERTIES: :TIMESTAMP: <2011-04-12 Tue 19:00> :END: * _appointment_ that _occurs_ at bike shop (keyword outside drawer) :TIMESTAMP: <2011-04-12 Tue 19:00> * _appointment_ that _occurs_ at bike shop (keyword-less, at least for backward compatibility) <2011-04-12 Tue 19:00> Michael
[O] empty titles - backtrace
Is not too rare for me to accidentally wipe or neglect to add a subject
line to a new journal/or entry. Of course I should have one - bUt
regardless, generating the agenda shouldnt fail if it comes across an
entry with no title as it can be hard to find the offending org
item. e.g
,
| Debugger entered--Lisp error: (wrong-type-argument stringp nil)
| string-match("^ +" nil)
| org-format-agenda-item(nil nil #("Journal" 0 7 (fontified t org-category
"Journal" face org-meta-line font-lock-fontified t)) (#("journal" 0 7
(inherited t))) #("<2011-04-13 Mi 10:00>" 0 20 (org-category #("Journal" 0 7
...) keymap (keymap ... ... ...) mouse-face highlight org-no-flyspell t face
org-date fontified t) 20 21 (org-category #("Journal" 0 7 ...) rear-nonsticky
(mouse-face highlight keymap invisible intangible help-echo org-linked-text)
keymap (keymap ... ... ...) mouse-face highlight org-no-flyspell t face
org-date fontified t)) "<2011-04-13.*?>")
| byte-code("\306 \203\n.\307\310\311\"\210\312
\210\313\225\203$.\314\315\313!\311
$U\204$.\307\310\311\"\210\n\2037.\316 \n{\317\f#\2047.\307\310\311\"\210e.)Z].{.* \203I.\317\202M.
\320
{.+.f\321U.,\322.-.*\"..\322./.*\".0.1\205p.\322.2.*\".3.1\205\205.\322.4.*\"\206\205.\322\323.*\".5.%.6\235.7.0\204\254..\204\254.3\204\254.5\204\254.7\203\261.8\203\261.\307\310\324\"\210\322\325.+\"\203\301.+\326\211\225O.+\327.!.9\330.!.:\212\331\332\311\324#\204\333.;.<\202.\326\224b\210\327
.=\333
.>\334\335!\210\315\313!.?\336.,\205\370.@.?.:.>.+.A&.<\337." 0
org-agenda-new-marker org-get-category re-search-backward "^\\*+ "
org-get-tags-at looking-at "\\*+[ ]+\\([^.\n]+\\)"
org-format-agenda-item org-get-priority org-add-props org-marker org-hd-marker
priority org-category todo-state type "timestamp" outline-next-heading
org-ds-keyword-length tmp timestr inactivep org-deadline-regexp deadlinep
org-scheduled-regexp scheduledp org-agenda-include-inactive-timestamps ...] 13)
| org-agenda-get-timestamps()
`
Where the item in question was:
,
|
| :PROPERTIES:
| :DateCreated: <2011-04-13 Mi 10:00>
| :END:
|
|
[[gnus:nntp%2BGwene:gwene.org.emacsen.planet][gnus:nntp+Gwene:gwene.org.emacsen.planet]]
`
a nilstring check in org-format-agenda-item isnt enough.
So, is there a way to enforce a default value "org wide" subject if the user
accidentally deletes or doesnt enter an org subject?
