Re: [O] [PATH] Speedups to org-table-recalculate

[Nathaniel Flath]

Fixed.

On Fri, Dec 5, 2014 at 3:57 PM, Nicolas Goaziou 
wrote:

> Nathaniel Flath  writes:
>
> > Sorry, that was incorrect - real patches attached.
>
> Thanks.
>
> > +(defun org-table-message-once-per-second (t1 &rest args)
> > +  "If there has been more than one second since T1, display message.
> > +ARGS are passed as arguments to the 'message' function.  Returns
> > +current time if a message is printed, otherwise returns t1..  If
> > +T1 is nil, always messages."
> > +  (let ((curtime (current-time)))
> > +(when (or (not t1) (< 0 (nth 1 (time-subtract curtime t1
> > +  (apply message args)
> > +  curtime))
> > +t1)
>
> The docstring seems incorrect, as the function always returns T1, no
> matter if a message is printed or not.
>
> > + (setq log-last-time
> > +   (org-table-message-once-per-second
> > +(when all log-last-time)
>
> Nitpick: (and all log-last-time)
>
> > +  (when all log-last-time)
>
> Ditto.
> > + (when all log-first-time)
>
> Ditto.
>
>
> Regards,
>


0001-org-table.el-org-table-recalculate-early-returns(1).patch
Description: Binary data


0001-org-table.el-org-table-recalculate-is-quieter.patch
Description: Binary data

Re: [O] C-x RET r utf-8 RET

[Eric Abrahamsen]

Sharon Kimble  writes:

> I'm trying to set this
>
> ╭
> │C-x RET r utf-8 RET
> ╰
>
> as "C-x zx" as I'm finding that I need to use this block-quoted
> command fairly regularly for some unknown reason.
>
> I have set it as
>
> #+BEGIN_SRC emacs-lisp
> (global-set-key (kbd "C-x zx") 'r utf8)
> #+END_SRC
>
> but the system rejects it as the "utf8" stage.

You've got a small confusion here between "key sequence" and "command
name". Up at the top, you're typing in the key sequence "C-x RET r".
That key sequence calls the command `revert-buffer-with-coding-system'.
You can verify this by using "C-h c" (for describe-key-briefly) and then
typing "C-x RET r". Or, the other way around, by typing "C-h w" (for
where-is), then "revert-buffer-with-coding-system".

When you set your global keys, the key sequence needs to point at a
_command_, not at more keys. We already know what the command name is,
so it will look like:

(global-set-key (kbd "C-x zx") 'revert-buffer-with-coding-system)

But that doesn't include the utf-8 part: using this key sequence will
still prompt you for a coding system. You could do that in a lambda, but
it probably won't accept a non-interactive function, so you'll likely
want something a little more complicated:

(defun my-set-coding-system-to-utf8 ()
  (interactive)
  (revert-buffer-with-coding-system 'utf-8))

(global-set-key (kbd "C-x zx") 'my-set-coding-system-to-utf8)

Give that a shot!

Note that the coding system specified is the symbol 'utf-8. It needs to
be quoted, and it needs to have the hyphen. I have more than once tried
to set my coding systems to 'utf8, to no avail.

Yours,
Eric

[O] C-x RET r utf-8 RET

[Sharon Kimble]

I'm trying to set this

╭
│C-x RET r utf-8 RET
╰

as "C-x zx" as I'm finding that I need to use this block-quoted
command fairly regularly for some unknown reason.

I have set it as

--8<---cut here---start->8---
#+BEGIN_SRC emacs-lisp
(global-set-key (kbd "C-x zx") 'r utf8)
#+END_SRC
--8<---cut here---end--->8---

but the system rejects it as the "utf8" stage.

How can I set it please?

Thanks
Sharon. 
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.4.1.0


signature.asc
Description: PGP signature

Re: [O] Mistake in org-mode manual

[Amitai Hoze]

Hi, sorry, I opened the page and the mistake is still there.

Amitai

On Mon, Dec 8, 2014 at 12:56 AM, Nicolas Goaziou 
wrote:

> Hello,
>
> Amitai Hoze  writes:
>
> > Hi, when reading
> >
> > http://orgmode.org/manual/Export-settings.html
> >
> > I found a mistake. It says:
> >
> > :
> >
> > Toggle line-break-preservation (org-export-preserve-breaks).
> >
> >
> > And it should say:
> >
> > \n:
> >
> > Toggle line-break-preservation (org-export-preserve-breaks).
>
> Fixed. Thank you.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>

Re: [O] Where should I put the timestamp?

[Eric Abrahamsen]

Marcin Borkowski  writes:

> Hi there,
>
> I vaguely remember someone saying here on the list that putting
> timestamps in the headline is deprecated.  However, I found this in the
> manual:
>
> "A timestamp can appear anywhere in the headline or body of an Org tree
> entry.  Its presence causes entries to be shown on specific dates in the
> agenda [...]"
>
> Which is wrong: my memory or the manual?
>
> TIA,

My understanding of the current state of affairs is that the timestamp
can appear anywhere but *between* a heading and its PROPERTIES drawer.
That's only because nothing is supposed to come between those two.

Someone please correct me if I'm wrong...

Eric

Re: [O] table formula help...

[Eric Abrahamsen]

Thierry Banel  writes:

> Le 07/12/2014 10:40, Michael Brand a écrit :
>>
>> I suggest that orgaggregate lets the user specify a TBLFM to be
>> inserted and updated. Missing target columns are added automatically,
>> it would result in
>>
>> #+BEGIN: aggregate :table "work" :cols "Translator sum(Chars) sum(Lines)"
>> | Translator  | sum(Chars) | sum(Lines) |  |
>> |-+++--|
>> | Austin Woerner  || 84 |   840.00 |
>> | Eric Abrahamsen |   6633 ||  4643.10 |
>> | Canaan Morse|  16984 || 11888.80 |
>> | Lucas Klein || 34 |   340.00 |
>> #+TBLFM: $4 = $2 * 0.7 + $3 * 10; %.2f
>> #+END:
>>
>
> I do agree, Michael, this is probably the way to go.
> Maybe the TBLFM should be taken care of for any kind of dynamic blocks,
> not only aggregate (columnview, clocktable, propview, invoice,
> transpose, and any future dynamic block).
>
> Regards
> Thierry

I thought of the same thing when I first started playing, but my plans
to provide a "quick patch" foundered when I looked at the code. Who knew
that, when I got up in the morning, it would all be implemented and
waiting in Melpa! Thanks so much to you both! I think this really
improves the usefulness of this package.

Eric

Re: [O] How to enhance the agenda output if soome info is only in the parent entry?

[Eric Abrahamsen]

Marcin Borkowski  writes:

> On 2014-12-07, at 22:37, Kyle Meyer wrote:
>
>> What about assigning categories?
>
> Thanks a lot!  I found it in the manual right after sending my email:-(.
>
> It still violates DRY, but I guess it's the best I can come up with; I
> think I'll use it (even though I don't really like it - I prefer my
> categories to be /very/ broad, corresponding to /files/ - think
> "research", "personal", "teaching" etc.  It's just a habit of mine,
> though, and I allow myself to change these from time to time;-).
>
> Best,

If you set `org-agenda-show-outline-path' to t, it will show you the
full path to the TODO in the message line as you move the cursor around.
You still have to move on to it to see the path, but usually for me
that's good enough.

E

[O] org-drill bugs?

[Leu Zhe]

Dear orgers,

Org-drill can set the review time automatically before.
However in recent versions, it always popup calendar buffer to set date
manually.

need help to solve this problem.

Thanks

Re: [O] Warning about section named "Footnotes"

[Arni Magnusson]

Dear Nicolas,

I have revised the paragraph following your suggestion, and prepared the 
patch using the 'git format-patch' command. See below.


In the past, I have signed FSF papers for Emacs and Texinfo contributions. 
Does that cover this contribution as well? If not, I'm happy with the 
TINYCHANGE stamp.


Best regards,

Arni




From 95f8aeead236eb6920fe315d9fe6348fb19ab975 Mon Sep 17 00:00:00 2001

From: Arni Magnusson 
Date: Mon, 8 Dec 2014 01:27:36 +
Subject: [PATCH] Warning about section named "Footnotes"

---
 doc/org.texi  | 8 +++-
 doc/orgguide.texi | 6 +-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index ed2eb5a..8368916 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1209,7 +1209,13 @@ headings indented less then 30 stars.}.  For example:
 * Another top level headline
 @end example

-@noindent Some people find the many stars too noisy and would prefer an
+@vindex org-footnote-section
+@noindent Note that a headline named after @code{org-footnote-section},
+which defaults to @samp{Footnotes}, is considered as special.  A subtree
+with this headline will be silently ignored by exporting functions,
+unless the value of @code{org-footnote-section} is modified.
+
+Some people find the many stars too noisy and would prefer an
 outline that has whitespace followed by a single star as headline
 starters.  @ref{Clean view}, describes a setup to realize this.

diff --git a/doc/orgguide.texi b/doc/orgguide.texi
index e32fa7c..7308d32 100644
--- a/doc/orgguide.texi
+++ b/doc/orgguide.texi
@@ -345,7 +345,11 @@ of @kbd{C-a} and @kbd{C-e} in headlines.}.  For example:
 * Another top level headline
 @end smallexample

-@noindent 
+@noindent Note that a headline named after @code{org-footnote-section},

+which defaults to @samp{Footnotes}, is considered as special.  A subtree
+with this headline will be silently ignored by exporting functions,
+unless the value of @code{org-footnote-section} is modified.
+
 Some people find the many stars too noisy and would prefer an
 outline that has whitespace followed by a single star as headline
 starters.  @ref{Clean view}, describes a setup to realize this.
--
1.9.3

Re: [O] Org-todo-yesterday broken?

[Kyle Meyer]

Nikolay Kudryavtsev  wrote:
> org-todo-yesterday and org-agenda-todo-yesterday do not seem to work
> in all recent versions of org that I've tried.

I'd guess this is because org-use-effective-time is set to nil (based on
this previous issue [1]).  Setting it to non-nil should work, but I
think org-todo-yesterday and org-agenda-todo-yesterday should override
this, as in the attached patch.

>From 10e5dfb5854473fa97b8299a0f059c233c349ef1 Mon Sep 17 00:00:00 2001
From: Kyle Meyer 
Date: Sun, 7 Dec 2014 19:21:42 -0500
Subject: [PATCH 1/1] org-todo-yesterday: Ignore org-use-effective-time

* lisp/org.el (org-todo-yesterday): Ignore global org-use-effective-time
value.

* lisp/org-agenda.el (org-agenda-todo-yesterday): Ignore global
org-use-effective-time value.

Otherwise, if org-use-effective-time being nil, org-extend-today-until
will not be considered, resulting in the current time being used instead
of 23:59 yesterday.

Reported-by: Nikolay Kudryavtsev 

---
 lisp/org-agenda.el | 3 ++-
 lisp/org.el| 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index b2e54e6..5990bbb 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -10143,7 +10143,8 @@ (defun org-agenda-todayp (date)
 (defun org-agenda-todo-yesterday (&optional arg)
   "Like `org-agenda-todo' but the time of change will be 23:59 of yesterday."
   (interactive "P")
-  (let* ((hour (third (decode-time
+  (let* ((org-use-effective-time t)
+	 (hour (third (decode-time
(org-current-time
  (org-extend-today-until (1+ hour)))
 (org-agenda-todo arg)))
diff --git a/lisp/org.el b/lisp/org.el
index 142407c..22a0c17 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -12469,7 +12469,8 @@ (defun org-todo-yesterday (&optional arg)
   (interactive "P")
   (if (eq major-mode 'org-agenda-mode)
   (apply 'org-agenda-todo-yesterday arg)
-(let* ((hour (third (decode-time
+(let* ((org-use-effective-time t)
+	   (hour (third (decode-time
 			 (org-current-time
 	   (org-extend-today-until (1+ hour)))
   (org-todo arg
-- 
2.1.3


[1] https://lists.gnu.org/archive/html/emacs-orgmode/2011-11/msg00320.html

-- 
Kyle

[O] Bug: addt'l multiple property drawers situations when org-log-done set to 'note [8.3beta (release_8.3beta-621-gf212f7) @ /path/to/org-mode/lisp/]

[Bradley M. Kuhn]

Nicolas,

Thanks for fixing that bug so quickly.  I grabbed the lastest master
and it seems the bug is definitely fixed.

I however still have a related bug:  I have many entries where the PROPERTIES
drawer is at the bottom of a long set of TODO notes.  Mine look like this:

** TODO Monthly Accounting: Reconcile Payment report.
   SCHEDULED: <2014-10-07 Tue 08:00 ++1m>
   - State "DONE"   from "TODO"   [2014-09-05 Fri 19:12] \\
 Finished through <2014-09-02 Tue>
   - State "DONE"   from "TODO"   [2014-06-16 Mon 09:28] \\
 Did this through <2014-05-30 Fri>.
   - State "TODO"   from ""   [2014-06-12 Thu 22:40] \\
 The monthly payment report can be downloaded.
   :PROPERTIES:
   :LAST_REPEAT: [2014-09-05 Fri 19:12]
   :END:

I still get a second property drawer when I cycle these repeating TODOs, if I
have:

(setq org-log-done 'note)

Same happens with ones like this, BTW::

* TODO Testing.
  SCHEDULED: <2014-12-28 Sun ++1w>
  - CLOSING NOTE [2014-12-07 Sun 19:25]
  - CLOSING NOTE [2014-12-07 Sun 19:25]
  :PROPERTIES:
  :LAST_REPEAT: [2014-12-07 Sun 19:25]
  :END:

It seems the new code intends to keep properties draw at the top of an entry,
but shouldn't it respect the positioning of the PROPRIETIES draw regardless
of where it is in the entry?

Thanks again for your responsiveness!

   -- bkuhn

Re: [O] [PATCH] org-src: allow `org-babel-edit-prep:.*' to mark region

[Nicolas Goaziou]

Oleh  writes:

> Well, I'm not trying to push my markup or anything, I just want my
> custom `org-babel-edit-prep:elisp' to be able to mark the region.
> Currently I'm not given that option.

Understood.

Would you mind providing a patch with format-patch, and reference the
current thread in the commit message?

Regards,

Re: [O] Bug: multiple property drawers generated for repeated tasks with org-log-done set to 'note [8.3beta (release_8.3beta-621-gf212f7) @ /path/to/org-mode/lisp/]

[Nicolas Goaziou]

Hello,

"Bradley M. Kuhn"  writes:

> I'm running org-mode directly out of master branch.  I updated to
> f212f7cf0d03c8f7abd22ffa6de2e5c46b19a266 (current master at time of
> writing) just to make sure the bug below hadn't been fixed recently.  It
> seems to still be present.  Here it is:
>
> With a minimal org mode setup with 'emacs -Q' and no other
> configuration, set these:
>
>   (setq org-log-done t)
>   (setq org-log-done 'note)
>
> then, in an org file (even an empty one), do this:
>
> * TODO test
>   SCHEDULED: <2014-12-06 Sat +1w>
>
> Then, do C-c C-t (org-todo) to mark as done and let it repeat.
> Then, do C-c C-t (org-todo) again.
>
> You'll end up with something like:
>
> * TODO test
>   SCHEDULED: <2015-01-31 Sat +1w>
>   - CLOSING NOTE [2014-12-06 Sat 21:52]
>   :PROPERTIES:
>   :LAST_REPEAT: [2014-12-06 Sat 21:52]
>   :END:
>   - CLOSING NOTE [2014-12-06 Sat 21:51]
>   :PROPERTIES:
>   :LAST_REPEAT: [2014-12-06 Sat 21:51]
>   :END:

That should be fixed. Thank you for reporting it.

Regards,

-- 
Nicolas Goaziou

[O] Org-todo-yesterday broken?

[Nikolay Kudryavtsev]

Hello.

org-todo-yesterday and org-agenda-todo-yesterday do not seem to work in 
all recent versions of org that I've tried.


Also is there a version of them that allows to input a custom date?

--
Best Regards,
Nikolay Kudryavtsev

Re: [O] Mistake in org-mode manual

[Nicolas Goaziou]

Hello,

Amitai Hoze  writes:

> Hi, when reading
>
> http://orgmode.org/manual/Export-settings.html
>
> I found a mistake. It says:
>
> :
>
> Toggle line-break-preservation (org-export-preserve-breaks).
>
>
> And it should say:
>
> \n:
>
> Toggle line-break-preservation (org-export-preserve-breaks).

Fixed. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: [O] How to enhance the agenda output if soome info is only in the parent entry?

[Kyle Meyer]

Marcin Borkowski  wrote:
> On 2014-12-07, at 22:37, Kyle Meyer wrote:
>
>> What about assigning categories?
>
> Thanks a lot!  I found it in the manual right after sending my email:-(.
>
> It still violates DRY, but I guess it's the best I can come up with; I
> think I'll use it

True.  For a handful of cases, this seems like an ok approach to
distinguish tasks from different subtrees, but it would get tedious if
that pattern occurs frequently across your agenda.

> (even though I don't really like it - I prefer my
> categories to be /very/ broad, corresponding to /files/ - think
> "research", "personal", "teaching" etc.  It's just a habit of mine,
> though, and I allow myself to change these from time to time;-).

Yes, I prefer broad categories too, so that makes sense to me.

--
Kyle

Re: [O] (org-agenda-to-appt) with sexp org-diary-class entry?

[Benjamin Slade]

Thanks, Marco. Well, it at least helps to update me to a non-obsolete
sexp method.

I have no idea how to check what's actually been pushed to `appt` to see
whether the updated org-class really behaves differently to
org-diary-class in this respect.  (So I'll have to see tomorrow how
`appt` behaves.)


~
Dr Benjamin Slade
pgp fingerprint: 21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19
~
{sent by mu4e on Emacs running under GNU/Linux}
(Choose Linux, Choose Freedom)

Re: [O] How to enhance the agenda output if soome info is only in the parent entry?

[Marcin Borkowski]

On 2014-12-07, at 22:37, Kyle Meyer wrote:

> What about assigning categories?

Thanks a lot!  I found it in the manual right after sending my email:-(.

It still violates DRY, but I guess it's the best I can come up with; I
think I'll use it (even though I don't really like it - I prefer my
categories to be /very/ broad, corresponding to /files/ - think
"research", "personal", "teaching" etc.  It's just a habit of mine,
though, and I allow myself to change these from time to time;-).

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] table formula help...

[Thierry Banel]

Le 07/12/2014 10:39, Michael Brand a écrit :
> Hi Thierry
>
> I suggest that orgaggregate leaves such fields empty instead of "NA".
> This way the user gets a choice how to deal with them by adding e. g.
> EN or not as TBLFM format specifier:
>
> | Translator  | sum(Chars) | sum(Lines) |
> |-++|
> | Austin Woerner  || 84 |
> | Eric Abrahamsen |   6633 ||
> | Canaan Morse|  16984 ||
> | Lucas Klein || 34 |
> |-++|
> | |5904.25 | 59 |
> #+TBLFM: @>$2 = vmean(@I..@II); EN :: @>$3 = vmean(@I..@II)
>

Done.
Probably this can be discussed further.
For the time being, there is no longer any "NA".

[O] Where should I put the timestamp?

[Marcin Borkowski]

Hi there,

I vaguely remember someone saying here on the list that putting
timestamps in the headline is deprecated.  However, I found this in the
manual:

"A timestamp can appear anywhere in the headline or body of an Org tree
entry.  Its presence causes entries to be shown on specific dates in the
agenda [...]"

Which is wrong: my memory or the manual?

TIA,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

Re: [O] How to enhance the agenda output if soome info is only in the parent entry?

[Kyle Meyer]

Marcin Borkowski  wrote:
[...]
> * Some person
> ** Some action to be done
> (concerning some_person)
> 
>
> * Some other person
> ** Some action to be done
> (concerning some_other_person)
> 
>
> Now, my (pretty much default) agenda shows only the "Some action to be
> done", which is kind of misleading in this case.
>
> What do I do about this?  I accept the possibility that my workflow
> (i.e., structure of Org entries) is broken - then, how to fix it?

What about assigning categories?

* Some person
  :PROPERTIES:
  :CATEGORY: some person
  :END:
** Some action to be done
   DEADLINE: <2014-12-08 Mon>

* Some other person
  :PROPERTIES:
  :CATEGORY: some other person
  :END:
** Some action to be done
   DEADLINE: <2014-12-08 Mon>

--
Kyle

Re: [O] Export as ASCII whilst respecting current fill column

[Samuel Wales]

interesting that it worked for you.  i am using 8.2.10 and ascii
export does not fill.  it seems to wrap single lines but not fill
entire paragraphs.

On 5/1/14, Miguel Guedes  wrote:
> Charles,
>
> Thanks very much for the tips -- they certainly helped!
>
> Miguel
>
>
> On 02/05/14 00:56, Charles Berry wrote:
>> Miguel Guedes  gmail.com> writes:
>>
>>>
>>> Using org-mode version 7.93f, when exporting to ASCII it doesn't respect
>>> the current fill column. Can this be enforced?
>>>
>>
>> Miguel,
>>
>> Upgrade to current org-mode (version 8.2.6) before you do anything else.
>>
>> Then modify `org-ascii-text-width' to suit your needs.
>>
>> ,
>> |
>> | org-ascii-text-width is a variable defined in `ox-ascii.el'.
>> | Its value is 72
>> |
>> |   Automatically becomes buffer-local when set.
>> |
>> | Documentation:
>> | Maximum width of exported text.
>> | This number includes margin size, as set in
>> | `org-ascii-global-margin'.
>> |
>> | You can customize this variable.
>> `
>>
>>
>>> Also, I've noticed that org doesn't remove verbatim tags (=verbatim=)
>>> but removes BEGIN_EXAMPLE blocks and presumably other BEGIN_xxx blocks;
>>> is this by design?
>>>
>>>
>>
>>
>> Same deal - upgrade. Then =xyz= becomes `xyz' on export.
>>
>> HTH,
>>
>> Chuck
>>
>>
>>
>
>
>
>


-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  And
ANYBODY can get it.

Denmark: free Karina Hansen NOW.

[O] How to enhance the agenda output if soome info is only in the parent entry?

[Marcin Borkowski]

Hello,

here's my problem.  Assume that I have something like this in one of my
agenda files:

* Some person
** Some action to be done
(concerning some_person)


* Some other person
** Some action to be done
(concerning some_other_person)


Now, my (pretty much default) agenda shows only the "Some action to be
done", which is kind of misleading in this case.

What do I do about this?  I accept the possibility that my workflow
(i.e., structure of Org entries) is broken - then, how to fix it?

I realize that tags is a way to do it.  But then, it violates the DRY
principle.  Also, I have org-agenda-tags-column set to -90, though I
guess I should change this, and I'll probably do it - the main reason
for that setting was (setq org-habit-preceding-days 30), and I really
don't use habits anyway.

TIA,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

[O] Mistake in org-mode manual

[Amitai Hoze]

Hi, when reading

http://orgmode.org/manual/Export-settings.html

I found a mistake. It says:

:

Toggle line-break-preservation (org-export-preserve-breaks).


And it should say:

\n:

Toggle line-break-preservation (org-export-preserve-breaks).

Amitai.

Re: [O] table formula help...

[Michael Brand]

Hi Thierry

On Sun, Dec 7, 2014 at 5:13 PM, Thierry Banel  wrote:
> The new features (:formula parameter and TBLFM survival) have been
> pushed to https://github.com/tbanel/orgaggregate. The unittests.org
> file has been updated. The http://melpa.org repository will reflect
> the change shortly.

Cool, thank you. As a hint for the user you could add something like
"@<$4 = string("header") etc. to the TBLFMs in the unittests.org.

Michael

Re: [O] table formula help...

[Thierry Banel]

Le 07/12/2014 11:26, Michael Brand a écrit :
> Hi Thierry
>
> On Sun, Dec 7, 2014 at 11:02 AM, Thierry Banel  wrote:
>> Maybe the TBLFM should be taken care of for any kind of dynamic blocks,
>> not only aggregate (columnview, clocktable, propview, invoice,
>> transpose, and any future dynamic block).
> Yes, see e. g. ":formula" in
> http://orgmode.org/manual/The-clock-table.html
>
> Content of a `#+TBLFM' line to be added and evaluated.
>
> and
>
> If you do not specify a formula here, any existing formula
> below the clock table will survive updates and be evaluated.
>
> Michael
>
The new features (:formula parameter and TBLFM survival) have been pushed to 
https://github.com/tbanel/orgaggregate. The unittests.org file has been 
updated. The http://melpa.org repository will reflect the change shortly.

This was easy to implement following the org-clock.el example.

Thanks, Michael, for this useful improvement.
Thierry

Re: [O] table formula help...

[Thierry Banel]

Le 07/12/2014 11:26, Michael Brand a écrit :
> Hi Thierry
>
> On Sun, Dec 7, 2014 at 11:02 AM, Thierry Banel  wrote:
>> Maybe the TBLFM should be taken care of for any kind of dynamic blocks,
>> not only aggregate (columnview, clocktable, propview, invoice,
>> transpose, and any future dynamic block).
> Yes, see e. g. ":formula" in
> http://orgmode.org/manual/The-clock-table.html
>
> Content of a `#+TBLFM' line to be added and evaluated.
>
> and
>
> If you do not specify a formula here, any existing formula
> below the clock table will survive updates and be evaluated.
>
> Michael
>

Excellent!
I've looked at org-clock.el, and understood the handling of TBLFMT.
I will mimic it in aggregate.

Thanks, Michael, for pointing to this relevant spot.
Thierry

Re: [O] How to trigger the clockcheck in an agenda view.

[Rainer Stengele]

Am 06.12.2014 16:29, schrieb Bernt Hansen:
> Rainer Stengele  writes:
>
>> Am 20.11.2014 um 13:51 schrieb Rainer Stengele:
>>> Am 27.09.2013 um 15:00 schrieb Carsten Dominik:
>>> Hello Carsten,
>>>
>>> thank you for that. clockcheck is working. But as soon as I get the 
>>> clockcheck view the scheduled items to disappear in my agenda view.
>>> I only can get scheduled items or all items in clockchecked view, not both 
>>> features.
>>> Any idea?
>>> Thanks!
>>> - Rainer
>>>
>>>
>> Hi again!
>> Any hint is much appreciated, even a "does not work right now" would be 
>> welcome although disappointing.
>> Thank you.
>> Regards, Rainer
> Hi Ranier,
>
> I think that is working as designed.  In clock check mode you only get
> clock details and gap and overlap reporting.  You can show clocks inline
> with C-u l but that will not give you clock check mode.
>
> Regards,
> Bernt
>
Hi Bernt,

thank you for your answer. I was hoping that this would be possible: seeing the 
clocked entries, the scheduled
ones and at the same time display the warnings about clockcheck gaps or 
overlaps.
That way I would not need to explicitly work through the clockcheck issues 
every day or at the end of the month by
changing the view, having forgotten to do that regularly.

Thanks again,
Rainer

[O] [PATCH] Second proposal for ":session" doc

[Thierry Pellé]

Hi, here is a proposal for some change on the ":session" header doc.

Comments are welcome!
Thierry


diff --git a/doc/org.texi b/doc/org.texi
index c1e84d4..45e177e 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -15566,7 +15566,9 @@ execution.
 @cindex @code{:session}, src header argument
 
 The @code{:session} header argument starts a session for an interpreted
-language where state is preserved.  By default, a session is not started.
+language.  All code block of this langage is executed into the same
+interpreter process, the state of the session being preserved as long as Emacs
+runs.  By default, a session is not started.
 
 @itemize @bullet
 @item @code{none}
@@ -15574,9 +15576,9 @@ The default.  Each block is evaluated in its own 
session.  The session is
 not preserved after the evaluation.
 @item @code{other}
 Any other string passed to the @code{:session} header argument will give the
-session a name.  All blocks with the same session name share the same
-session.  Using different session name enables concurrent sessions (even for
-the same interpreted language).  E.g., @code{:session mysession}.
+session a name (possibly empty).  All blocks with the same session name share
+the same session.  Using different session name enables concurrent sessions
+(for the same interpreted language).  E.g., @code{:session mysession} or 
@code{:session}.
 @end itemize
 
 @node noweb

[O] Noweb (named blocks) reference name

[abonnements]

Hi,
   what do you think of allowing spaces in Noweb reference name or 
named blocks? It seems (to me) to be more natural than remplacing spaces 
by minus for instance.



Example :
1) With named block
#+name: first variable
: 30

2) With noweb
#+name: step 1
#+begin_src 

#+name: step 2
#+begin_src 

#+begin src ... :noweb yes
<<>>
<<>>
#+end_src

Is it possible? (at least using "..." to group words.

Thanks.
Thierry

Re: [O] table formula help...

[Michael Brand]

Hi Thierry

On Sun, Dec 7, 2014 at 11:02 AM, Thierry Banel  wrote:
> Maybe the TBLFM should be taken care of for any kind of dynamic blocks,
> not only aggregate (columnview, clocktable, propview, invoice,
> transpose, and any future dynamic block).

Yes, see e. g. ":formula" in
http://orgmode.org/manual/The-clock-table.html

Content of a `#+TBLFM' line to be added and evaluated.

and

If you do not specify a formula here, any existing formula
below the clock table will survive updates and be evaluated.

Michael

Re: [O] table formula help...

[Thierry Banel]

Le 07/12/2014 10:40, Michael Brand a écrit :
>
> I suggest that orgaggregate lets the user specify a TBLFM to be
> inserted and updated. Missing target columns are added automatically,
> it would result in
>
> #+BEGIN: aggregate :table "work" :cols "Translator sum(Chars) sum(Lines)"
> | Translator  | sum(Chars) | sum(Lines) |  |
> |-+++--|
> | Austin Woerner  || 84 |   840.00 |
> | Eric Abrahamsen |   6633 ||  4643.10 |
> | Canaan Morse|  16984 || 11888.80 |
> | Lucas Klein || 34 |   340.00 |
> #+TBLFM: $4 = $2 * 0.7 + $3 * 10; %.2f
> #+END:
>

I do agree, Michael, this is probably the way to go.
Maybe the TBLFM should be taken care of for any kind of dynamic blocks,
not only aggregate (columnview, clocktable, propview, invoice,
transpose, and any future dynamic block).

Regards
Thierry

Re: [O] table formula help...

[Thierry Banel]

Le 07/12/2014 10:39, Michael Brand a écrit :
> Hi Thierry
>
>
> I suggest that orgaggregate leaves such fields empty instead of "NA".
> This way the user gets a choice how to deal with them by adding e. g.
> EN or not as TBLFM format specifier:
>
> | Translator  | sum(Chars) | sum(Lines) |
> |-++|
> | Austin Woerner  || 84 |
> | Eric Abrahamsen |   6633 ||
> | Canaan Morse|  16984 ||
> | Lucas Klein || 34 |
> |-++|
> | |5904.25 | 59 |
> #+TBLFM: @>$2 = vmean(@I..@II); EN :: @>$3 = vmean(@I..@II)
>

I didn't knew about the EN specifier. Thanks Michael for pointing to it.
Your suggestion is quite interesting. I will take a look.
We could also handle empty fields as zero.
Let us think about the best to do.

Re: [O] table formula help...

[Michael Brand]

Hi Thierry

On Sun, Dec 7, 2014 at 10:20 AM, Thierry Banel  wrote:
> Le 07/12/2014 04:25, Eric Abrahamsen a écrit :
>> [...]
>> (sum(prod($2 0.7) prod($3 10))
>>
>> Where $2 and $3 refer to cells in the aggregated table.
>
> It would be great of course. However I don't know how to do that
> cleanly. If we want total flexibility for the formulas, we will end up
> duplicating the native features of Org spreadsheet.

I suggest that orgaggregate lets the user specify a TBLFM to be
inserted and updated. Missing target columns are added automatically,
it would result in

#+BEGIN: aggregate :table "work" :cols "Translator sum(Chars) sum(Lines)"
| Translator  | sum(Chars) | sum(Lines) |  |
|-+++--|
| Austin Woerner  || 84 |   840.00 |
| Eric Abrahamsen |   6633 ||  4643.10 |
| Canaan Morse|  16984 || 11888.80 |
| Lucas Klein || 34 |   340.00 |
#+TBLFM: $4 = $2 * 0.7 + $3 * 10; %.2f
#+END:

Re: [O] table formula help...

[Michael Brand]

Hi Thierry

On Sun, Dec 7, 2014 at 4:25 AM, Eric Abrahamsen  wrote:
> Thierry Banel  writes:
>> [...]
>>   #+BEGIN: aggregate :table "work" :cols "Translator sum(Chars) sum(Lines)"
>>   | Translator  | sum(Chars) | sum(Lines) |
>>
>>   |-++|
>>   | Austin Woerner  | NA | 84 |
>>   | Eric Abrahamsen | 6633   | NA |
>>   | Canaan Morse| 16984  | NA |
>>   | Lucas Klein | 2 NA   | 34 |
>>   #+END:
>> [...]
> I've changed blank fields to "0" so that I don't get the "NA" strings.
>> [...]

I suggest that orgaggregate leaves such fields empty instead of "NA".
This way the user gets a choice how to deal with them by adding e. g.
EN or not as TBLFM format specifier:

| Translator  | sum(Chars) | sum(Lines) |
|-++|
| Austin Woerner  || 84 |
| Eric Abrahamsen |   6633 ||
| Canaan Morse|  16984 ||
| Lucas Klein || 34 |
|-++|
| |5904.25 | 59 |
#+TBLFM: @>$2 = vmean(@I..@II); EN :: @>$3 = vmean(@I..@II)

Re: [O] table formula help...

[Thierry Banel]

Le 07/12/2014 04:25, Eric Abrahamsen a écrit :
>
> Okay, having fun! This seems like exactly what I was after. A couple of
> things:
>
> I've attached a patch replacing some [a-z] regexps with [:word:], so
> that column names can be written in scripts other than ascii (my tables
> above are actually all in Chinese). I hope that's acceptable.

Not only it is acceptable, it is also very welcome!
Your patch has been pushed to GitHub along with an updated unittests.org
(https://github.com/tbanel/orgaggregate).
Wait for a couple of hours for Melpa to refresh
(http://melpa.org).

> I've changed blank fields to "0" so that I don't get the "NA" strings.
>
> Now I'd like to do more calculations based on the rows in the sum(Chars)
> and sum(Lines) columns.
>
> Ideally I could add a fourth column to the aggregate table, calculated
> from rows in the previous two. Is there any way to make a column
> specification that refers to columns in the same table? The fourth
> column would be defined as:
>
> (sum(prod($2 0.7) prod($3 10))
>
> Where $2 and $3 refer to cells in the aggregated table.

It would be great of course. However I don't know how to do that
cleanly. If we want total flexibility for the formulas, we will end up
duplicating the native features of Org spreadsheet.

> I made that up -- I don't even know if it's valid calc syntax. But
> that's the idea. Or perhaps I should be making a third table based on
> this second one?

This would be the easiest for the time being.

You can also add columns and formulas to the 2nd table in the usual way
(Alt-Shift-RightArrow, then C-c =). But beware that those additions will
be cleared by an aggregate refresh.

> Thanks again!
>
> Eric
>

You are welcome
Thierry

Re: [O] [RFC/PATCH] Fixes for org-timer

[Kyle Meyer]

Nicolas Goaziou  wrote:
> Kyle Meyer  writes:
>
>> Do you prefer to add fixes for the current design, or just move
>> directly to merging the two APIs?
>
> The latter sounds better.

I've attached updated patches.

>From da0454ea110de0b4effb59ec220d8e15960fbf84 Mon Sep 17 00:00:00 2001
From: Kyle Meyer 
Date: Mon, 1 Dec 2014 02:02:19 -0500
Subject: [PATCH 1/2] org-timer.el (org-timer): Recognize double prefix

* lisp/org-timer.el (org-timer): Follow the behavior described in the
docstring for a double prefix argument.
---
 lisp/org-timer.el | 12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/lisp/org-timer.el b/lisp/org-timer.el
index d02362c..c9710ca 100644
--- a/lisp/org-timer.el
+++ b/lisp/org-timer.el
@@ -177,11 +177,13 @@ (defun org-timer (&optional restart no-insert-p)
 If NO-INSERT-P is non-nil, return the string instead of inserting
 it in the buffer."
   (interactive "P")
-  (when (or (equal restart '(4)) (not org-timer-start-time))
-(org-timer-start))
-  (if no-insert-p
-  (org-timer-value-string)
-(insert (org-timer-value-string
+  (if (equal restart '(16))
+  (org-timer-start restart)
+(when (or (equal restart '(4)) (not org-timer-start-time))
+  (org-timer-start))
+(if no-insert-p
+	(org-timer-value-string)
+  (insert (org-timer-value-string)
 
 (defun org-timer-value-string ()
   "Set the timer string."
-- 
2.1.3

>From 981cee236e91cd40a006eb5eef43095e449b6cc9 Mon Sep 17 00:00:00 2001
From: Kyle Meyer 
Date: Sun, 7 Dec 2014 02:24:54 -0500
Subject: [PATCH 2/2] org-timer.el: Merge API for the two timers

* lisp/org-timer.el (org-timer-stop): Support countdown timers in addition
to relative timers.

* lisp/org-timer.el (org-timer-cancel-timer): Remove function.

* lisp/org-timer.el (org-timer-pause-or-continue): Support countdown
timers in addition to relative timers.

* testing/lisp/test-org-timer.el: New file.

* doc/org.texi: Merge relative and countdown timer nodes.

Several previous issues are fixed with these changes.

- org-timer-set-timer and org-timer-cancel-timer did not reset
  org-timer-start-time after countdown completed.

- Because org-timer-start did not return org-timer-pause-time to nil,
  the modeline remained stuck at the paused time.

- When org-timer-start was called with a countdown timer, the modeline
  was updated for the new relative timer, but the countdown timer
  remained scheduled.

- When org-timer-pause-or-continue was called with a countdown timer
  running, the modeline was put in a paused state, but the countdown
  timer remained scheduled.

- When org-timer-stop was called with a countdown timer running, the
  timer was removed from the modeline, but the countdown timer remained
  scheduled.

- When org-timer-set-timer was called with a paused relative timer, the
  relative timer was not reset properly (org-timer-pause-time was still
  non-nil) and the modeline remained in the paused state of the relative
  timer, even though the countdown timer was scheduled with
  run-with-timer.

- Running org-timer-set-timer at the beginning of an empty buffer
  resulted in an args-out-of-range error (due to the org-get-at-eol
  call).
---
 doc/org.texi   |  84 ++---
 etc/ORG-NEWS   |   5 +
 lisp/org-timer.el  | 207 ++-
 testing/lisp/test-org-timer.el | 273 +
 4 files changed, 438 insertions(+), 131 deletions(-)
 create mode 100644 testing/lisp/test-org-timer.el

diff --git a/doc/org.texi b/doc/org.texi
index f9436b3..f7444ce 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -462,8 +462,7 @@ Dates and times
 * Deadlines and scheduling::Planning your work
 * Clocking work time::  Tracking how long you spend on a task
 * Effort estimates::Planning work effort in advance
-* Relative timer::  Notes with a running timer
-* Countdown timer:: Starting a countdown timer for a task
+* Timers::  Notes with a running timer
 
 Creating timestamps
 
@@ -5790,8 +5789,7 @@ is used in a much wider sense.
 * Deadlines and scheduling::Planning your work
 * Clocking work time::  Tracking how long you spend on a task
 * Effort estimates::Planning work effort in advance
-* Relative timer::  Notes with a running timer
-* Countdown timer:: Starting a countdown timer for a task
+* Timers::  Notes with a running timer
 @end menu
 
 
@@ -6794,60 +6792,56 @@ with the @kbd{/} key in the agenda (@pxref{Agenda commands}).  If you have
 these estimates defined consistently, two or three key presses will narrow
 down the list to stuff that fits into an available time slot.
 
-@node Relative timer
-@section Taking notes with a relative timer
+@node Timers
+@section Taking notes with a timer
 @cindex relative timer
+@cindex countdown timer
+@kindex ;
+
+Org provides provides two types of t