Re: [O] exporting clock-in and clock-out times
Wait, I was wrong—adding the c:t OPTION actually did not solve the problem. I forgot I had converted my clock-in and clock-out to plain text in an attempt to work around the problem, so it appeared to work only because it was plain text. Apologies. So. I still have the same problem, namely: How to get my clock-in and clock-out times to appear in HTML export? My specs: GNU Emacs 23.3.50.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54) of 2011-10-25 on braeburn.aquamacs.org - Aquamacs Distribution 2.4 Org-mode version 7.9.2 (7.9.2-dist @ /Users/peter/elisp/org-7.9.2/lisp/) OS X 10.8.2 Thanks! On Fri, Nov 9, 2012 at 5:31 AM, Giovanni Ridolfi giovanni.rido...@yahoo.itwrote: Da: Peter Salazar cycleofs...@gmail.com Inviato: Venerdì 9 Novembre 2012 10:50 Hi, Peter, I'm exporting to HTML and trying to get my clock-in and clock-out times to export as well, but it's not working. My org file looks like this: #+OPTIONS: d:t timestamp:t * foo CLOCK: [2012-11-09 Fri 03:58]--[2012-11-09 Fri 03:59] = 0:01 foo. FIRST : always, please, always. Please, always, did I already say always? please always send: Org-version, Emacs version Operatig System and in this case, dealing with the exporter, if you used the new or the old exporter. Here: Org-mode version 7.9.2 (854ddf6 @ c:/Users/ridolfi/programs/emacs-o/org/lisp/) GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) of 2012-06-10 on MARVIN 1. I can export the clock line *IF* I have a property drawer: #+OPTIONS: d:t timestamp:t * foo CLOCK: [2012-11-09 Fri 03:58]--[2012-11-09 Fri 03:59] = 0:01 :PROPERTIES: :END: foo. -+HTML 1 foo CLOCK: 11/09/12 ven 03:58– 11/09/12 ven 03:59 = 0:01 PROPERTIES foo. 2 byeARCHIVE -+ so this is a quick and dirty solution. 2. Otherwise I cannot get the clock line in the HTML file: - without (i.e. commenting out) the :PROPERTIES: drawer - with the new exporter (with or without propertiies) cheers, Giovanni
Re: [O] How to set up a recurring task wich is automatically set on done
Hi, Ukhara Arahku ukh...@gmail.com writes: I have to do a job every 2 weeks on Friday I want to have a task which: - remembers me (or is shown in the agenda) 2 days before, thus Wednesday - when the recurring date is over it is set on DONE automatically - and is shown again 2 days before the next Friday another 2 weeks Hmm, requirement 1 and 3 would be something like this: DEADLINE: 2012-11-11 So ++2w -2d , a repeated task with an explicit deadline for the item. Regarding 2, the setting to DONE automatically bit: May I ask, why you consider that? It doesn't seem really useful to me; a status change, purely based on time, does not convey any information whatsoever afaict. Memnon
Re: [O] Sexp aganda entries broken?
Hello, Simon Thum simon.t...@gmx.de writes: To prevent further breakage, I am attaching a doc fix. I hope it is useable? This is already documented in section 10.3.1 (Calendar/Diary integration) of the manual. I don't think it's useful to drop another note there. Thanks for your patch, though. Regards, -- Nicolas Goaziou
Re: [O] exporting clock-in and clock-out times
Peter Salazar cycleofs...@gmail.com writes: Wait, I was wrong—adding the c:t OPTION actually did not solve the problem. I forgot I had converted my clock-in and clock-out to plain text in an attempt to work around the problem, so it appeared to work only because it was plain text. Apologies. I was talking about the new exporter, where it should work. Regards,
Re: [O] How to customize the heading definition in org-mode
Hi, Avner Moshkovitz avnermoshkov...@lighthausvci.com writes: I want to use a lisp file (the .emacs file) in org-mode. This will help me to navigate through sections of the .emacs configuration file. I do so with the following setup: I have a minimal init.el file in my ~/.emacs.d directory. It basically looks like this: --8---cut here---start-8--- (require 'cl) ;; Load Path to org and babel (setq load-path (cons path/to/elisp/org-latest/lisp load-path)) (setq load-path (cons path/to/elisp/org-latest/contrib/lisp load-path)) (setq load-path (cons path/to/elisp/org-latest/contrib/babel/lisp load-path)) ;; modules got to be set _before_ org is loaded (setq org-modules '(org-bbdb org-bibtex org-gnus org-info org-jsinfo org-irc org-vm org-w3m org-crypt org-learn org-collector org-habit org-depend org-timer)) ;; load up Org-mode and Org-babel (require 'org) ;;(require 'org-babel-init) ;; Load my .emacs (org-babel-load-file path/to/emacs.org) --8---cut here---end---8--- That last org-babel-load-file bit actually loads my other settings. (see http://memnon.sdf-eu.org/emacs.html http://memnon.sdf-eu.org/emacs.org for an example) I looked for an equivalent to this in org-mode but couldn't find a way to customize the heading definition. Is there a way to do so? AFAIK, the * is a fixed part of the org syntax and is not customizable. hth Memnon
Re: [O] How to set up a recurring task wich is automatically set on done
Hi, thanks for this syntax. 2012/11/10 Memnon Anon gegendosenflei...@googlemail.com requirement 1 and 3 would be something like this: DEADLINE: 2012-11-11 So ++2w -2d , a repeated task with an explicit deadline for the item. Regarding 2, the setting to DONE automatically bit: May I ask, why you consider that? It doesn't seem really useful to me; a status change, purely based on time, does not convey any information whatsoever afaict. In this special issue I have to do a report every two weeks and the agenda should only remember myself; in case the date passed, it doesn't matter: the status should change for a fortnight to DONE I don't want to have list of items in the agenda, which are always done and I have to change manually the status. ukhara
[O] [babel] [new exporter] bug in subtree export
Hi all,
I am not able to export a subtree, that has babel references pointing
outside, when I use the new exporter (it is working with the old one).
See the following example and export the second subtree only to
reproduce the problem:
---[ example orgmode file ]
#+TITLE: refs not in tree
#+LATEX_HEADER: \usepackage{hyperref}
* Some code
#+name: mycode
#+begin_src R
1 + 1
#+end_src
#+results: mycode
: 2
* Some text
Here, I input the results:
1 + 1 is src_R[:var ttt=mycode() :results raw]{paste(=, ttt)}
-
Regards,
Andreas
Re: [O] [babel] [new exporter] bug in subtree export
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
I am not able to export a subtree, that has babel references pointing
outside, when I use the new exporter (it is working with the old one).
See the following example and export the second subtree only to
reproduce the problem:
---[ example orgmode file ]
#+TITLE: refs not in tree
#+LATEX_HEADER: \usepackage{hyperref}
* Some code
#+name: mycode
#+begin_src R
1 + 1
#+end_src
#+results: mycode
: 2
* Some text
Here, I input the results:
1 + 1 is src_R[:var ttt=mycode() :results raw]{paste(=, ttt)}
-
After a restart of emacs, I am not able to reproduce it myself, anymore.
Sorry for the noise.
Regards,
Andreas
Re: [O] [babel] [new exporter] bug in subtree export
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
I am not able to export a subtree, that has babel references pointing
outside, when I use the new exporter (it is working with the old one).
I cannot reproduce it.
When exporting * Some text subtree on:
--8---cut here---start-8---
#+TITLE: refs not in tree
#+LATEX_HEADER: \usepackage{hyperref}
* Some code
#+name: mycode
#+BEGIN_SRC emacs-lisp
(+ 1 1)
#+END_SRC
* Some text
Here, I input the results:
1 + 1 is src_emacs-lisp[:var ttt=mycode() :results raw]{ttt}
--8---cut here---end---8---
I get:
--8---cut here---start-8---
\begin{document}
\maketitle
Here, I input the results:
1 + 1 is 2
% Generated by Org mode 7.9.2 in Emacs 24.2.1.
\end{document}
--8---cut here---end---8---
Do you use the latest Org? Is it specific to R, or can you reproduce my
example?
Regards,
--
Nicolas Goaziou
Re: [O] How to customize the heading definition in org-mode
On Sat, 10 Nov 2012 10:38:41 + (UTC) Memnon Anon gegendosenflei...@googlemail.com wrote: Avner Moshkovitz avnermoshkov...@lighthausvci.com writes: I looked for an equivalent to this in org-mode but couldn't find a way to customize the heading definition. Is there a way to do so? AFAIK, the * is a fixed part of the org syntax and is not customizable. Yes, there was a discussion here not so long ago - the result of the discussion was (and I'm only paraphrasing) It's true there is no way to change it, and we're intentionally keeping it that way to prevent needless complexity in org-mode. -- David
Re: [O] Sexp aganda entries broken?
On 11/10/2012 11:31 AM, Nicolas Goaziou wrote: Hello, Simon Thumsimon.t...@gmx.de writes: To prevent further breakage, I am attaching a doc fix. I hope it is useable? This is already documented in section 10.3.1 (Calendar/Diary integration) of the manual. I don't think it's useful to drop another note there. I know that, but I deemed it useful to document it as a related but separate mechanism on its own merit. Perhaps there could be a link to 10.3.1 to make it clear that the notations differ in important ways? Cheers, Simon Thanks for your patch, though. Regards,
Re: [O] Sexp aganda entries broken?
Simon Thum simon.t...@gmx.de writes: I know that, but I deemed it useful to document it as a related but separate mechanism on its own merit. Perhaps there could be a link to 10.3.1 to make it clear that the notations differ in important ways? Since %%(...) syntax isn't a timestamp /per se/, there is no reason to refer to it in the timestamps part of the manual. Also, despite its own merit, it's an antiquated[fn:1] and irregular syntax, which doesn't deserve much publicity. It won't disappear, but it's better to circumvent its uses. Regards, [fn:1] Even the example given in Calendar/Diary integration section is outdated, as it relies on CATEGORY keyword to change category on the fly within the same section (see footnote in 10.4.1). -- Nicolas Goaziou
[O] [babel] bug[?] when calling src_R from table?
Hi,
I wanted to combine a table of text and a generated result (in org to
LaTaX using the new exporter). It would seem src_R snips would be
perfect for this. However, it does not seem to work. I.e. src_R is
translated correctly in the text, but not in the table.
Is this a feature or a bug?
Example below.
Thanks,
Rasmus
Org-mode version 7.9.2 (release_7.9.2-556-g7cdfa6.dirty @
/usr/share/emacs/site-lisp/org/)
#+BEGIN_SRC org
#+PROPERTY: session *R*
#+BEGIN_SRC R :exports none
att - c(1+1, 3)
#+END_SRC
it's length is src_R[:results raw]{length(att)}.
| src_R[:results raw]{length(ate)} |
#+END_SRC
#+BEGIN_SRC latex
it's length is 2.
\begin{center}
\begin{tabular}{l}
\toprule
src$_\mathrm{R[}$:results raw]\{length(ate)\}\\
\bottomrule
\end{tabular}
\end{center}
#+END_SRC
--
Hooray!
Re: [O] [babel] bug[?] when calling src_R from table?
Hello, Rasmus ras...@gmx.us writes: I wanted to combine a table of text and a generated result (in org to LaTaX using the new exporter). It would seem src_R snips would be perfect for this. However, it does not seem to work. I.e. src_R is translated correctly in the text, but not in the table. That's because inline src blocks are not allowed in table cells. Appropriate place for formulas in the spreadsheet is the TBLFM line. Regards, -- Nicolas Goaziou
Re: [O] exporting clock-in and clock-out times
Oh cool. How do I install the new exporter? I don't use git. My specs: GNU Emacs 23.3.50.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54) of 2011-10-25 on braeburn.aquamacs.org - Aquamacs Distribution 2.4 Org-mode version 7.9.2 (7.9.2-dist @ /Users/peter/elisp/org-7.9.2/lisp/) OS X 10.8.2 On Sat, Nov 10, 2012 at 5:33 AM, Nicolas Goaziou n.goaz...@gmail.comwrote: Peter Salazar cycleofs...@gmail.com writes: Wait, I was wrong—adding the c:t OPTION actually did not solve the problem. I forgot I had converted my clock-in and clock-out to plain text in an attempt to work around the problem, so it appeared to work only because it was plain text. Apologies. I was talking about the new exporter, where it should work. Regards,
[O] make update fails
Aloha all, I get this error message: mk/targets.mk:75: *** target file `update' has both : and :: entries. Stop. I suspect I've done something wrong and will appreciate suggestions how to get back on track. All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] How to set up a recurring task wich is automatically set on done
Hi Ukhara On Sat, Nov 10, 2012 at 2:29 PM, Ukhara Arahku ukh...@gmail.com wrote: 2012/11/10 Memnon Anon gegendosenflei...@googlemail.com [...] DEADLINE: 2012-11-11 So ++2w -2d [...] In this special issue I have to do a report every two weeks and the agenda should only remember myself; in case the date passed, it doesn't matter: the status should change for a fortnight to DONE I don't want to have list of items in the agenda, which are always done and I have to change manually the status. Maybe you want to use * TODO task 2012-11-23 Fri ++2w or if you really don’t want to look ahead in the agenda and really want the reminders on the two days before * TODO task (due on Fri) 2012-11-21 Wed ++2w 2012-11-22 Thu ++2w 2012-11-23 Fri ++2w which will shift all three timestamps synchronously when set to DONE. This can even be used without TODO when there is no need for the possibility of getting the task out of the way when it’s done before it’s overdue. Michael
[O] [New exporter][texinfo] noexport tag ignored
Aloha, #+TITLE: export-test.org #+AUTHOR:Thomas Dye #+EMAIL: t...@tsdye.com #+DATE: 2012-11-10 Sat #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * Export * Do not export:noexport: Exports a menu that doesn't respect the noexport tag: ... @menu * Export:: * Do not export:: ... All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] [new exporter] no \caption and \label upon export of #+BEGIN_LATEX block
Hello,
I'd like to use a tikz snippet in a few different documents and it would
be convenient to be able to include it in a latex document like so:
#+CAPTION: a fine figure
#+NAME: figure:fine_figure
#+ATTR_LaTeX: width=5cm
#+BEGIN_LATEX
\input{/home/myles/tex/tikz_figure.tex}
#+END_LATEX
What is exported is just the \input line, with no \label or \caption, i.e.:
\input{/home/myles/tex/tikz_figure.tex}
I believe this was possible with current (old) exporter, based on this
thread:
http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00267.html
Is it currently possible or could it be added please?
On second thoughts, perhaps another way to do it would be to have a
source block make the tikz graphic as a standalone pdf/eps and then
insert it as a link to the file. The disadvantage of that would be that
the tikz .tex file would need to be expanded to have it's own
\begin/end{document} and would loose some flexibility. Any thoughts on
that route?
Thanks,
Myles
Org-mode version 7.9.2 (release_7.9.2-571-g359891 @
/home/myles/.emacs.d/plugins/org-mode/lisp/)
Re: [O] [new exporter] no \caption and \label upon export of #+BEGIN_LATEX block
Myles English writes:
Hello,
I'd like to use a tikz snippet in a few different documents and it would
be convenient to be able to include it in a latex document like so:
#+CAPTION: a fine figure
#+NAME: figure:fine_figure
#+ATTR_LaTeX: width=5cm
#+BEGIN_LATEX
\input{/home/myles/tex/tikz_figure.tex}
#+END_LATEX
I realise now that this is wishful thinking because org doesn't know
that the input file will result in a graphic and so doesn't know to wrap
the input file in \begin{figure} \end{figure}.
What is exported is just the \input line, with no \label or \caption, i.e.:
\input{/home/myles/tex/tikz_figure.tex}
I believe this was possible with current (old) exporter, based on this
thread:
http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00267.html
Is it currently possible or could it be added please?
On second thoughts, perhaps another way to do it would be to have a
source block make the tikz graphic as a standalone pdf/eps and then
insert it as a link to the file. The disadvantage of that would be that
the tikz .tex file would need to be expanded to have it's own
\begin/end{document} and would loose some flexibility. Any thoughts on
that route?
Thanks,
Myles
Org-mode version 7.9.2 (release_7.9.2-571-g359891 @
/home/myles/.emacs.d/plugins/org-mode/lisp/)
Re: [O] [New exporter][texinfo] noexport tag ignored
Hello, t...@tsdye.com (Thomas S. Dye) writes: #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport This should be (see `org-export-options-alist'): #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport Regards, -- Nicolas Goaziou
Re: [O] exporting clock-in and clock-out times
Peter Salazar cycleofs...@gmail.com writes: Oh cool. How do I install the new exporter? I don't use git. You can use package.el, for example and install org-plus-contrib package (new exporter is in contrib/ directory). See: http://orgmode.org/elpa.html Regards,
Re: [O] How to set up a recurring task wich is automatically set on done
Hi Michael, that sounds good, didn't know that I can use more than one date specification, and to omit TODO looks tricky. I will give them a shot. Thanks. ukhara 2012/11/10 Michael Brand michael.ch.br...@gmail.com or if you really don’t want to look ahead in the agenda and really want the reminders on the two days before * TODO task (due on Fri) 2012-11-21 Wed ++2w 2012-11-22 Thu ++2w 2012-11-23 Fri ++2w which will shift all three timestamps synchronously when set to DONE. This can even be used without TODO when there is no need for the possibility of getting the task out of the way when it’s done before it’s overdue. Michael
Re: [O] [new exporter] no \caption and \label upon export of #+BEGIN_LATEX block
Hello,
Myles English mylesengl...@gmail.com writes:
I'd like to use a tikz snippet in a few different documents and it would
be convenient to be able to include it in a latex document like so:
#+CAPTION: a fine figure
#+NAME: figure:fine_figure
#+ATTR_LaTeX: width=5cm
#+BEGIN_LATEX
\input{/home/myles/tex/tikz_figure.tex}
#+END_LATEX
What is exported is just the \input line, with no \label or \caption, i.e.:
\input{/home/myles/tex/tikz_figure.tex}
Well, IMO, it doesn't make much sense to add a caption or a label to an
export block. Just write whatever you want within the block. I.e.:
#+BEGIN_LATEX
\caption{\label{figure:fine_figure}a fine figure}
\input{/home/myles/tex/tikz_figure.tex}
#+END_LATEX
Is there any downside to it?
I believe this was possible with current (old) exporter, based on this
thread:
http://lists.gnu.org/archive/html/emacs-orgmode/2012-10/msg00267.html
This thread is about src blocks. Adding a label or a caption is fine for
them.
On second thoughts, perhaps another way to do it would be to have a
source block make the tikz graphic as a standalone pdf/eps and then
insert it as a link to the file. The disadvantage of that would be that
the tikz .tex file would need to be expanded to have it's own
\begin/end{document} and would loose some flexibility. Any thoughts on
that route?
I don't know. for my graphics, I use Asymptote src-blocks generating
links to pdf files. E.g.:
#+NAME: app
#+BEGIN_SRC asymptote :file application.pdf
import graph;
defaultpen(fontsize(10pt));
unitsize(2cm);
pen p=blue;
real f(real x) { return x**2; }
real g(real x) { return -x + 2; }
draw(graph(f,0,1),p);
draw(graph(g,1,2),p);
xaxis(xmax=2.3,Ticks(Size=1mm,NoZero),Arrow(6pt));
yaxis(ymax=1.3,Ticks(step=.5,Step=1,Size=1mm,NoZero),Arrow(6pt));
label($O$,(0,0),SW);
label($C_f$,(1.5,g(1.5)),2N,p);
#+END_SRC
#+BEGIN_CENTER
#+RESULTS: app
[[file:application.pdf]]
#+END_CENTER
Regards,
--
Nicolas Goaziou
Re: [O] Sexp aganda entries broken?
On 11/10/2012 05:24 PM, Nicolas Goaziou wrote: Simon Thumsimon.t...@gmx.de writes: I know that, but I deemed it useful to document it as a related but separate mechanism on its own merit. Perhaps there could be a link to 10.3.1 to make it clear that the notations differ in important ways? Since %%(...) syntax isn't a timestamp /per se/, there is no reason to refer to it in the timestamps part of the manual. Also, despite its own merit, it's an antiquated[fn:1] and irregular syntax, which doesn't deserve much publicity. It won't disappear, but it's better to circumvent its uses. I see, it just seemed to me that org-contacts uses it for (seemingly) good reasons and there is no replacement or deprecation. Is there missing consensus on this syntax? Cheers, Simon Regards, [fn:1] Even the example given in Calendar/Diary integration section is outdated, as it relies on CATEGORY keyword to change category on the fly within the same section (see footnote in 10.4.1).
[O] [patch] Typo in org-e-texinfo.el
Aloha, Patch attached. Tom From f615b7727b5e95df68f84ad22ff86f2e9722bef2 Mon Sep 17 00:00:00 2001 From: Thomas Dye t...@tsdye.com Date: Sat, 10 Nov 2012 16:41:54 -1000 Subject: [PATCH] * contrib/lisp/org-e-texinfo.el: Correct typo in error message --- contrib/lisp/org-e-texinfo.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/lisp/org-e-texinfo.el b/contrib/lisp/org-e-texinfo.el index 6eb536e..6e5730d 100644 --- a/contrib/lisp/org-e-texinfo.el +++ b/contrib/lisp/org-e-texinfo.el @@ -1749,7 +1749,7 @@ none. (errors )) (when (save-excursion (re-search-forward perhaps incorrect sectioning? nil t)) - (setq errors (concat errors [incorrect sectionnng]))) + (setq errors (concat errors [incorrect sectioning]))) (when (save-excursion (re-search-forward missing close brace nil t)) (setq errors (concat errors [syntax error]))) -- 1.8.0 -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] [New exporter][texinfo] noexport tag ignored
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, t...@tsdye.com (Thomas S. Dye) writes: #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport This should be (see `org-export-options-alist'): #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport Regards, #+TITLE: export-test.org #+AUTHOR:Thomas Dye #+EMAIL: t...@tsdye.com #+DATE: 2012-11-10 Sat #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+SELECT_TAGS: export #+EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * Export * Do not export:noexport: Exports: ... @menu * Export:: * Do not export:: @end menu ... Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] make update fails
Thomas S. Dye t...@tsdye.com wrote: Aloha all, I get this error message: mk/targets.mk:75: *** target file `update' has both : and :: entries. Stop. I suspect I've done something wrong and will appreciate suggestions how to get back on track. Probably added something to your local.mk that looks like this: update: mk/targets.mk has this however: update update2::up0 all The single vs double colons cause the problem: see (info (make) Multiple Rules) (info (make) Double-Colon) for the details. Nick
Re: [O] make update fails
Nick Dokos nicholas.do...@hp.com writes: Thomas S. Dye t...@tsdye.com wrote: Aloha all, I get this error message: mk/targets.mk:75: *** target file `update' has both : and :: entries. Stop. I suspect I've done something wrong and will appreciate suggestions how to get back on track. Probably added something to your local.mk that looks like this: update: mk/targets.mk has this however: update update2:: up0 all The single vs double colons cause the problem: see (info (make) Multiple Rules) (info (make) Double-Colon) for the details. Nick Yes, update:: seems to work. Thanks, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Suggestions for progress tracking
David Rogers davidandrewrog...@gmail.com writes: Eric Abrahamsen e...@ericabrahamsen.net writes: I'm starting another novel translation, and want to keep track of progress in org (I've blown too many deadlines in the past). I've been looking at the habits functionality, but it doesn't quite match what I want, and I'm looking for a little advice here. I'd like to: 1. Set myself a minimum of pages translated per day, on weekdays. 2. Record how many pages I do each day. 3. View some habit-style report of how I'm doing relative to my goal. 4. Project when I will be done with the novel at the current rate of progress. Obviously I'll be writing some custom elisp to get all of this functionality, but I'm looking for some advice on the best way to build the basics. Habits are currently based on either/or values: done or not done, which doesn't incorporate enough detail. Properties seem like the best way to keep track of number of pages translated per day, but that means having a separate TODO heading for each day of work. State logging could do it, but there are no pre-fab ways of extracting data out of the log itself. It seems like there are so many good tools here: the history reporting of habits, or the progress cookies you can put in headlines, etc. But they're all tied to headlines or list items being in an on or off state: TODO/DONE, checked/unchecked. I think the key for making this work with Org is choosing a unit of work (ten pages, a hundred pages, one page, one chapter, whatever) as your standard, thus allowing you to use the on/off nature of the list items to your advantage. Org also gives flexibility about the time-frames you're working within, so use that too if necessary. [...] Maybe your original method, tallying pages per day after the fact, could be used for the first few days, to arrive at some reasonable numbers to plug into the habits. I guess you're right I'll eventually need to set a daily target. But it's going to make a very big difference to me to know by _how much_ I was under or over. At any rate, I've started logging, with a capture template that gives me something like this: --8---cut here---start-8--- * Santi Schedule DEADLINE: 2013-06-01 Sat :PROPERTIES: :PAGES:502 :ID: 908fc17c-c620-4212-98eb-2e028f08dce3 :END: ** 2012-11-07 Wed:log: :PROPERTIES: :PAGES:9 :END: ** 2012-11-08 Thu:log: :PROPERTIES: :PAGES:3 :END: --8---cut here---end---8--- Something tells me I'll eventually make these into TODOs, but maybe I'll also try to jury-rig an Agenda timeline view that will give me a sense of my varying progress over time. Below is my first stab at a function to read and use this data. Anyhow, thanks for the food for thought! Eric --8---cut here---start-8--- (defun my-translation-schedule () (interactive) (require 'org) (save-excursion (org-id-goto 908fc17c-c620-4212-98eb-2e028f08dce3) (let ((deadline (org-entry-get nil DEADLINE)) (page-total (string-to-number (org-entry-get nil PAGES))) (completed 0)) (org-map-entries (lambda () (setq completed (+ (string-to-number (org-entry-get nil PAGES)) completed))) +log 'file) (let* ((remaining-days (- (org-time-string-to-absolute deadline) (org-today))) (remaining-pages (float (- page-total completed))) (pages-per-day (fceiling (/ remaining-pages remaining-days (message %d pages left to go, you'll need to do %d pages per day to finish by %s remaining-pages pages-per-day deadline) --8---cut here---end---8---
