Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Nick Dokos]

Ilya Shlyakhter ilya_...@alum.mit.edu wrote:

 A corrected patch is attached.
 

One more thing that you'll need to do is put your patches in attachments
of a type that will allow patchwork to snag the patch:
application/octet-stream does not. And if they don't end up in
patchwork, they might get lost. See the Patches get caught on patchwork
section at

   http://orgmode.org/worg/org-contribute.html#sec-4-3

Nick

Re: [O] Mail composed using emacs --- saving a copy in an org file.

[Karl Voit]

* Alan E. Davis lngn...@gmail.com wrote:

 An emacs FAQ suggests sending a BCC or FCC to oneself.  What I want is a
 copy stored in an org-mode subtree, with a convenient headline indicating
 the name of the recipient and the date.

Hi!

Maybe Memacs[1] can get you what you want. Fully automatically,
without manual action (after initial setup).

If you got your emails stored in IMAP or maildir format you can use
the corresponding Memacs modules. They periodically index all your
emails and derive an Org-mode archive file containing header
information and an Org-mode timestamp which appears on your agenda
as well.

Drop me a line if it works for your requirements!

  1. https://github.com/novoid/Memacs
-- 
Karl Voit

[O] entering inactive timestamp 7.2.12 results in [2012-03-16 Fr]

[Rainer Stengele]

Hi all,

Entering 7.2.12 as an incative timestamp (C-c !)

I get [2012-03-16 Fr].

Entering 7.2.2012 results in [2012-02-07 Di].

I have german settings in my emacs.
Is there a chance to get wanted behaviour?

dd.mm.yy seems to be a standard calendar date format.


- Rainer

Re: [O] entering inactive timestamp 7.2.12 results in [2012-03-16 Fr]

[suvayu ali]

Hi Rainer,

On Fri, Mar 16, 2012 at 11:12, Rainer Stengele
rainer.steng...@online.de wrote:
 Hi all,

 Entering 7.2.12 as an incative timestamp (C-c !)

 I get [2012-03-16 Fr].

 Entering 7.2.2012 results in [2012-02-07 Di].

 I have german settings in my emacs.
 Is there a chance to get wanted behaviour?

 dd.mm.yy seems to be a standard calendar date format.


You could try customising `calendar-date-style'.

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Carsten Dominik]

Hi Ilya, hi Nick,

thanks for looking into this.  I am amazed by the deep
understanding of Org's internals that shows in this
thread.

Both patches seem to be OK as far as I can see and
can be applied without adverse effects.
The patch for org-clock.el will at most achieve a factor
of two (because org-get-tags-at is called anyway), but
indeed, the patch in org.el can potentially have even
more significant effects, when properties are tested
in the matcher.

Cheers and thanks!

- Carsten

On 16.3.2012, at 05:34, Ilya Shlyakhter wrote:

 Here is a similar patch for org-clock's use of tags/properties matcher.
 
 On Fri, Mar 16, 2012 at 12:31 AM, Ilya Shlyakhter ilya_...@alum.mit.edu 
 wrote:
 ,
 | If your function needs to retrieve the tags including inherited tags
 | at the *current* entry, 
 
 'Function' here refers to the FUNC parameter of org-map-entries, not the 
 MATCHER parameter.
 The matcher is constructed by org-make-tags-matcher, so we know everything it 
 does --
 it does not move around and only asks about the current entry's tags and 
 properties.
 org-scan-tags only invokes the matcher at the current entry, and sets 
 org-scanner-tags
 correctly for that call.
 
 But, you're right that there is a problem: while org-scan-tags sets 
 org-scanner-tags correctly
 before (eval matcher), other users of the matcher -- e.g. 
 org-clock-get-table-data -- might not.
 So, org-trust-scanner-tags should be set not in the matcher, but in the 
 function that calls
 the matcher.  A corrected patch is attached.
 
 thanks,
 
 ilya
 
 
 On Thu, Mar 15, 2012 at 11:13 PM, Nick Dokos nicholas.do...@hp.com wrote:
 Ilya Shlyakhter ilya_...@alum.mit.edu wrote:
 
 The attached patch speeds up tags matching ( 50s -- 5s for my most
 common search ), by turning on org-trust-scanner-tags within the
 matcher.
 
 (When it's off, getting a non-inherited property's value causes a call
 to org-entry-properties to fetch all properties into a cache,
 including ALLTAGS; fetching ALLTAGS involves calling
 (org-get-tags-at), which is slow when org-trust-scanner-tags is off.)
 
 Can this cause problems / was this off for a reason?
 
 
 I haven't looked at your patch carefully enough to know if it will or
 will not cause problems, but check the doc for org-map-entries: it has
 some guidelines about where the technique can be used and where it
 cannot:
 
 ,
 | If your function needs to retrieve the tags including inherited tags
 | at the *current* entry, you can use the value of the variable
 | `org-scanner-tags' which will be much faster than getting the value
 | with `org-get-tags-at'.  If your function gets properties with
 | `org-entry-properties' at the *current* entry, bind `org-trust-scanner-tags'
 | to t around the call to `org-entry-properties' to get the same speedup.
 | Note that if your function moves around to retrieve tags and properties at
 | a *different* entry, you cannot use these techniques.
 `
 
 
 There are warnings that this variable is for internal dynamical scoping only,
 so I suspect you should not mess with the default. If your search can make
 the needed guarantees, then you can just wrap it in a let to get the speedup.
 Otherwise, it probably should be left alone.
 
 Nick
 
 
 
 0003-Clocking-work-time-faster-filtering-of-clock-entries.patch

Re: [O] exporting org to html using an external css stylesheet

[Christian Moe]

1. Does the link .../ show up in the HTML source of the exported 
document? Is the relative URL correct?


2. Wild guess: Are you perhaps expecting the default org-mode 
stylesheet to go away? It doesn't; default styles will still be shown 
if they are not specifically superseded by those you add. To turn off 
the defaults altogether, customize org-export-html-style-include-default.


Yours,
Christian

On 3/16/12 12:19 AM, Zachary Jones wrote:

I am trying to set up a website using org-mode and would like to use
an external css stylesheet. I am currently using the #+STYLE: option
with the argument link rel=stylesheet type=text/css
href=./stylesheet.css /. The exported html documents seem to be
using the default org-mode styling though. I can't seem to get the
exported html documents to recognize and use the css. Help!

--
Zachary M. Jones

Re: [O] Mail composed using emacs --- saving a copy in an org file.

[brian powell]

* Wow! That looks like great software!  Looks like it very well might
do what Alan was looking for--and a whole lot more.

Just out of curiosity: Have you, Karl, looked into linking into doing
a mashup with GNOWSYS:

http://en.wikipedia.org/wiki/GNOWSYS

** Maybe GNOWSYS would be used after using/applying MEMACS.


 Drop me a line if it works for your requirements!

  1. https://github.com/novoid/Memacs
 --
 Karl Voit

Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Ilya Shlyakhter]

On 3/16/2012 2:10 AM, Nick Dokos wrote:
 One more thing that you'll need to do is put your patches in attachments
 of a type that will allow patchwork to snag the patch:

Thanks, I was wondering why they're not showing up.
Here is another try (attached) for the org.el patch.

ilya
From 95c38b06803aec0787bc2eaab3d0062221390292 Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter ilya_...@alum.mit.edu
Date: Fri, 16 Mar 2012 00:10:25 -0400
Subject: [PATCH 2/2] Tags/properties matcher: faster matching by trusting
 org-scanner-tags

* lisp/org.el (org-scan-tags): Bind org-trust-scanner-tags to t
while evaluating the matcher, since the matcher is always evaluated
at the current entry.

TINYCHANGE
---
 lisp/org.el |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lisp/org.el b/lisp/org.el
index ad63213..951f692 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -12906,7 +12906,8 @@ headlines matching this string.
 
 ;; eval matcher only when the todo condition is OK
 (and (or (not todo-only) (member todo org-not-done-keywords))
- (let ((case-fold-search t)) (eval matcher)))
+ (let ((case-fold-search t) (org-trust-scanner-tags t))
+  (eval matcher)))
 
 ;; Call the skipper, but return t if it does not skip,
 ;; so that the `and' form continues evaluating
-- 
1.7.9.3

Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Ilya Shlyakhter]

On 3/16/2012 2:10 AM, Nick Dokos wrote:

One more thing that you'll need to do is put your patches in attachments
of a type that will allow patchwork to snag the patch:


And here is the org-clock.el patch again.

From 4f7f91ae62d425f7a89738b28006b1743a6bea4d Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter ilya_...@alum.mit.edu
Date: Fri, 16 Mar 2012 00:25:18 -0400
Subject: [PATCH 3/3] Clocking work time: faster filtering of clock entries by
 trusting  org-scanner-tags

* lisp/org-clock.el (org-clock-get-table-data): Bind org-scanner-tags
to tags-list and org-trust-scanner-tags to t
while evaluating the matcher, since the matcher is always evaluated
at the current entry.

TINYCHANGE
---
 lisp/org-clock.el |4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index 9206608..46d9af8 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -2463,7 +2463,9 @@ TIME:  The sum of all time spend in this tree, in 
minutes.  This time
   (org-clock-sum ts te
 (unless (null matcher)
   (lambda ()
-(let ((tags-list (org-get-tags-at)))
+(let* ((tags-list (org-get-tags-at))
+   (org-scanner-tags tags-list)
+   (org-trust-scanner-tags t))
   (eval matcher)
   (goto-char (point-min))
   (setq st t)
-- 
1.7.9.3

Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Nick Dokos]

Carsten Dominik carsten.domi...@gmail.com wrote:

 Hi Ilya, hi Nick,
 
 thanks for looking into this.  I am amazed by the deep
 understanding of Org's internals that shows in this
 thread.
 

On Ilya's part, certainly - for my part, I have only the vaguest clue
about what Ilya did - I just saw a possible red flag. I still have not
looked into his patches, but now, thanks to you, I don't have to :-)
I can just enjoy the speedup!

Nick

 Both patches seem to be OK as far as I can see and
 can be applied without adverse effects.
 The patch for org-clock.el will at most achieve a factor
 of two (because org-get-tags-at is called anyway), but
 indeed, the patch in org.el can potentially have even
 more significant effects, when properties are tested
 in the matcher.
 
 Cheers and thanks!
 
 - Carsten

[O] [PATCH] Fixed compiler warnings including one small bug in ob-lilypond

[Ilya Shlyakhter]

Re-sending the patch as a correct attachment type.
One of the warnings indicated an actual (small) bug.
From d0579b6e104b82ec7d3255086384ff8dee0d4e0e Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter ilya_...@alum.mit.edu
Date: Fri, 16 Mar 2012 01:52:03 -0400
Subject: [PATCH] Fixed compiler warnings, including one small bug in ob-lilypond

* lisp/ob-lilypond.el (ly-compile-lilyfile): Fixed misplaced comma in a
quoting expression.

* lisp/org-pcomplete.el: added missing defvar definitions for org vars

* lisp/org-src.el: added declare-function line for org-babel-tangle

* lisp/ob.el (org-scan-tags): protected the variable tags-list with a let
(other) added missing defvar declarations.

TINYCHANGE
---
 lisp/ob-lilypond.el   |2 +-
 lisp/org-pcomplete.el |5 +
 lisp/org-src.el   |2 ++
 lisp/org.el   |9 +++--
 4 files changed, 15 insertions(+), 3 deletions(-)

diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el
index a008b2d..0e9b0c6 100644
--- a/lisp/ob-lilypond.el
+++ b/lisp/ob-lilypond.el
@@ -223,7 +223,7 @@ FILE-NAME is full path to lilypond (.ly) file
 (arg-11 file-name))
 (if test
 `(,arg-1 ,arg-2 ,arg-3 ,arg-4 ,arg-5 ,arg-6
- ,arg-7 ,arg-8 ,arg-9 ,arg-10, arg-11)
+ ,arg-7 ,arg-8 ,arg-9 ,arg-10 ,arg-11)
   (call-process
arg-1 arg-2 arg-3 arg-4 arg-5 arg-6
arg-7 arg-8 arg-9 arg-10 arg-11
diff --git a/lisp/org-pcomplete.el b/lisp/org-pcomplete.el
index c475bcc..7a4dc0d 100644
--- a/lisp/org-pcomplete.el
+++ b/lisp/org-pcomplete.el
@@ -50,6 +50,9 @@
   :tag Org
   :group 'org)
 
+(defvar org-drawer-regexp)
+(defvar org-property-re)
+
 (defun org-thing-at-point ()
   Examine the thing at point and let the caller know what it is.
 The return value is a string naming the thing at point.
@@ -247,6 +250,8 @@ This needs more work, to handle headings with lots of 
spaces in them.
 lst))
(substring pcomplete-stub 1)))
 
+(defvar org-drawers)
+
 (defun pcomplete/org-mode/drawer ()
   Complete a drawer name.
   (let ((spc (save-excursion
diff --git a/lisp/org-src.el b/lisp/org-src.el
index 88217cd..cc5a6ca 100644
--- a/lisp/org-src.el
+++ b/lisp/org-src.el
@@ -686,6 +686,8 @@ the language, a switch telling if the content should be in 
a single line.
   (interactive)
   (org-src-in-org-buffer (save-buffer)))
 
+(declare-function org-babel-tangle ob-tangle (optional only-this-block 
target-file lang))
+
 (defun org-src-tangle (arg)
   Tangle the parent buffer.
   (interactive)
diff --git a/lisp/org.el b/lisp/org.el
index 951f692..7f8eddb 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -76,6 +76,7 @@
   (require 'gnus-sum))
 
 (require 'calendar)
+(require 'format-spec)
 
 ;; Emacs 22 calendar compatibility:  Make sure the new variables are available
 (when (fboundp 'defvaralias)
@@ -4930,6 +4931,8 @@ sure that we are at the beginning of the line.)
   Matches an headline, putting stars and text into groups.
 Stars are put in group 1 and the trimmed body in group 2.)
 
+(defvar bidi-paragraph-direction)
+
 ;;;###autoload
 (define-derived-mode org-mode outline-mode Org
   Outline-based notes management and organizer, alias
@@ -12854,7 +12857,7 @@ headlines matching this string.
   (buffer-name (buffer-base-buffer)))
 (case-fold-search nil)
 (org-map-continue-from nil)
- lspos tags
+ lspos tags tags-list
 (tags-alist (list (cons 0 org-file-tags)))
 (llast 0) rtn rtn1 level category i txt
 todo marker entry priority)
@@ -14986,6 +14989,7 @@ So these are more for recording a certain time/date.
 (defvar org-read-date-final-answer nil)
 (defvar org-read-date-analyze-futurep nil)
 (defvar org-read-date-analyze-forced-year nil)
+(defvar org-read-date-inactive)
 
 (defun org-read-date (optional with-time to-time from-string prompt
default-time default-input inactive)
@@ -15185,7 +15189,6 @@ user.
 (defvar def)
 (defvar defdecode)
 (defvar with-time)
-(defvar org-read-date-inactive)
 (defun org-read-date-display ()
   Display the current date prompt interpretation in the minibuffer.
   (when org-read-date-display-live
@@ -17008,6 +17011,8 @@ Some of the options can be changed using the variable
  (error Unknown conversion type %s for latex fragments
 processing-type)
 
+(declare-function format-spec format-spec (format specification))
+
 (defun org-create-math-formula (latex-frag optional mathml-file)
   Convert LATEX-FRAG to MathML and store it in MATHML-FILE.
 Use `org-latex-to-mathml-convert-command'.  If the conversion is
-- 
1.7.9.3

Re: [O] [PATCH] Fixed compiler warnings including one small bug in ob-lilypond

[Eric Schulte]

Applied, Thanks!

Ilya Shlyakhter ilya_...@alum.mit.edu writes:

 Re-sending the patch as a correct attachment type.
 One of the warnings indicated an actual (small) bug.

 From d0579b6e104b82ec7d3255086384ff8dee0d4e0e Mon Sep 17 00:00:00 2001
 From: Ilya Shlyakhter ilya_...@alum.mit.edu
 Date: Fri, 16 Mar 2012 01:52:03 -0400
 Subject: [PATCH] Fixed compiler warnings, including one small bug in 
 ob-lilypond

 * lisp/ob-lilypond.el (ly-compile-lilyfile): Fixed misplaced comma in a
 quoting expression.

 * lisp/org-pcomplete.el: added missing defvar definitions for org vars

 * lisp/org-src.el: added declare-function line for org-babel-tangle

 * lisp/ob.el (org-scan-tags): protected the variable tags-list with a let
 (other) added missing defvar declarations.

 TINYCHANGE
 ---
  lisp/ob-lilypond.el   |2 +-
  lisp/org-pcomplete.el |5 +
  lisp/org-src.el   |2 ++
  lisp/org.el   |9 +++--
  4 files changed, 15 insertions(+), 3 deletions(-)

 diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el
 index a008b2d..0e9b0c6 100644
 --- a/lisp/ob-lilypond.el
 +++ b/lisp/ob-lilypond.el
 @@ -223,7 +223,7 @@ FILE-NAME is full path to lilypond (.ly) file
  (arg-11 file-name))
  (if test
  `(,arg-1 ,arg-2 ,arg-3 ,arg-4 ,arg-5 ,arg-6
 - ,arg-7 ,arg-8 ,arg-9 ,arg-10, arg-11)
 + ,arg-7 ,arg-8 ,arg-9 ,arg-10 ,arg-11)
(call-process
 arg-1 arg-2 arg-3 arg-4 arg-5 arg-6
 arg-7 arg-8 arg-9 arg-10 arg-11
 diff --git a/lisp/org-pcomplete.el b/lisp/org-pcomplete.el
 index c475bcc..7a4dc0d 100644
 --- a/lisp/org-pcomplete.el
 +++ b/lisp/org-pcomplete.el
 @@ -50,6 +50,9 @@
:tag Org
:group 'org)
  
 +(defvar org-drawer-regexp)
 +(defvar org-property-re)
 +
  (defun org-thing-at-point ()
Examine the thing at point and let the caller know what it is.
  The return value is a string naming the thing at point.
 @@ -247,6 +250,8 @@ This needs more work, to handle headings with lots of 
 spaces in them.
lst))
 (substring pcomplete-stub 1)))
  
 +(defvar org-drawers)
 +
  (defun pcomplete/org-mode/drawer ()
Complete a drawer name.
(let ((spc (save-excursion
 diff --git a/lisp/org-src.el b/lisp/org-src.el
 index 88217cd..cc5a6ca 100644
 --- a/lisp/org-src.el
 +++ b/lisp/org-src.el
 @@ -686,6 +686,8 @@ the language, a switch telling if the content should be 
 in a single line.
(interactive)
(org-src-in-org-buffer (save-buffer)))
  
 +(declare-function org-babel-tangle ob-tangle (optional only-this-block 
 target-file lang))
 +
  (defun org-src-tangle (arg)
Tangle the parent buffer.
(interactive)
 diff --git a/lisp/org.el b/lisp/org.el
 index 951f692..7f8eddb 100644
 --- a/lisp/org.el
 +++ b/lisp/org.el
 @@ -76,6 +76,7 @@
(require 'gnus-sum))
  
  (require 'calendar)
 +(require 'format-spec)
  
  ;; Emacs 22 calendar compatibility:  Make sure the new variables are 
 available
  (when (fboundp 'defvaralias)
 @@ -4930,6 +4931,8 @@ sure that we are at the beginning of the line.)
Matches an headline, putting stars and text into groups.
  Stars are put in group 1 and the trimmed body in group 2.)
  
 +(defvar bidi-paragraph-direction)
 +
  ;;;###autoload
  (define-derived-mode org-mode outline-mode Org
Outline-based notes management and organizer, alias
 @@ -12854,7 +12857,7 @@ headlines matching this string.
  (buffer-name (buffer-base-buffer)))
(case-fold-search nil)
(org-map-continue-from nil)
 - lspos tags
 + lspos tags tags-list
(tags-alist (list (cons 0 org-file-tags)))
(llast 0) rtn rtn1 level category i txt
todo marker entry priority)
 @@ -14986,6 +14989,7 @@ So these are more for recording a certain time/date.
  (defvar org-read-date-final-answer nil)
  (defvar org-read-date-analyze-futurep nil)
  (defvar org-read-date-analyze-forced-year nil)
 +(defvar org-read-date-inactive)
  
  (defun org-read-date (optional with-time to-time from-string prompt
   default-time default-input inactive)
 @@ -15185,7 +15189,6 @@ user.
  (defvar def)
  (defvar defdecode)
  (defvar with-time)
 -(defvar org-read-date-inactive)
  (defun org-read-date-display ()
Display the current date prompt interpretation in the minibuffer.
(when org-read-date-display-live
 @@ -17008,6 +17011,8 @@ Some of the options can be changed using the variable
 (error Unknown conversion type %s for latex fragments
processing-type)
  
 +(declare-function format-spec format-spec (format specification))
 +
  (defun org-create-math-formula (latex-frag optional mathml-file)
Convert LATEX-FRAG to MathML and store it in MATHML-FILE.
  Use `org-latex-to-mathml-convert-command'.  If the conversion is

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

[O] can competing table headers: #+BEGIN #+ORGTBL #+TBLNAME be resolved?

[Myles English]

Hi,

My aim is to have a document that can that can be updated via the
command line batch command.  What prevents this the need to rearrange
the header lines on a table that has multiple uses:

- to capture the columnview, the #+BEGIN line must be the first line
  above the table

- to export to latex, the #+ORGTBL line must be the first line above the
  table

- to name the table so that it may be - referred to in a source blocks,
  the #+TBLNAME line much be the first - one

All three scenarios may be investigated using the table in the attached
file.  It would be nice if the #+ lines did not need to be reordered
before accessing each feature so I am wondering if it would be feasible
to unify these header lines or at least make them ignore any subsequent
lines starting #+ ?

Thanks,

Myles

#+STARTUP: indent
#+COLUMNS: %50ITEM %5Effort(Time est. [H:M]){:}
#+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:nil
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport

* Competition between table header lines
** Introduction
The aim is to have a document that can that can be updated via the command
line batch command.  What prevents this the need to rearrange the header lines
on a table that has multiple uses:

- to capture the columnview, the #+BEGIN line must be the first line above the 
table
- to export to latex, the #+ORGTBL line must be the first line above the table
- to name the table so that it may be referred to in a source blocks,
  the #+TBLNAME line much be the first one

All three scenarios may be investigated using the table below.  It would be
nice if the #+ lines did not need to be reordered before accessing each
feature.

** Table
:PROPERTIES:
:Effort: 0:30
:END:

#+BEGIN: columnview :hlines 5 :id local
#+TBLNAME: cvtblname
#+ORGTBL: SEND cvtbl orgtbl-to-latex :fmt (1 padStr)
| ITEM | Time est. [H:M] |
|--+-|
| ** Table |0:30 |
#+END:

#+BEGIN_LATEX
\begin{landscape}
% BEGIN RECEIVE ORGTBL cvtbl
\begin{tabular}{lr}
ITEM  Time est. [H:M] \\
\hline
** Table  0:30 \\
\end{tabular}
% END RECEIVE ORGTBL cvtbl
\end{landscape}
#+END_LATEX

#+NAME: calcblk
#+BEGIN_SRC emacs-lisp :var data=cvtblname[-1,1] :exports none
data
#+END_SRC

#+RESULTS: calcblk
: 0:30

[O] Memacs and Gnowsis (was: Mail composed using emacs --- saving a copy in an org file.)

[Karl Voit]

* brian powell briangpowel...@gmail.com wrote:
 * Wow! That looks like great software!  
  1. https://github.com/novoid/Memacs

It *is* :-) I enjoy using it every day!

 Looks like it very well might
 do what Alan was looking for--and a whole lot more.

Yes, a *lot* more than this. You realize the real beauty of Memacs
only when you already set up the system. With a Memacs-filled agenda
you get a cool overview of your digital (and analog) life :-)

 Just out of curiosity: Have you, Karl, looked into linking into doing
 a mashup with GNOWSYS:
 http://en.wikipedia.org/wiki/GNOWSYS

Sorry, I do not see a point in combining Memacs with Gnowsis. The
technical layer of Memacs is fairly simple. If Gnowsis wants to
include external data into their system, they can implement their
own parsers as well.

Or they implement an Org-mode-parser and include the resulting files
of Memacs.

Either way: Memacs does nothing else than generating condensed views
on the data you already got.

Or do you mean Memacs should provide a module that parses Gnowsis
data set?

-- 
Karl Voit

Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

[Karl Voit]

Since no followup reaction occured: is this a but that requires much
work? Or did my email just got lost in overfull inboxes? :-)

* Karl Voit devn...@karl-voit.at wrote:

 I verified the behavior below with the most current git version of
 Org-mode.

 Whenever I call my function to export the current agenda, it
 «converts» events that do have a beginning and end time to events
 that span the whole day (without begin and end times at all).

 ,[ my LISP command to export ]
| (defun vk-export-agenda()
|   Exports monthly Org-mode agenda to agenda.ics file
|   (interactive)
|   (org-agenda-list nil nil 60)
|   (org-agenda-write ~/org/agenda.ics)
| )
 `

 I traced down the problem to this:

 * 2012-03-05 Mon 08:00-09:00 works fine
 * 2012-03-05 Mon 8:00-9:00 works fine too

 * 2012-03-05 08:00-09:00 Wrong: ends up as full day event

 Unfortunately, I do have certain mechanisms that generate parts of
 my Org-mode files where I skip the day of the week. Org-mode in
 general is able to handle date stamps without day of week pretty
 well. But whenever I export it to ics (in order to send it to
 Google), I end up with a messed up online agenda.

 I guess that org-agenda-write is the one to blame. It would be very
 handy to me if somebody could fix that issue.

 Let me know, if you need any further information!

 Thank you very much!

-- 
Karl Voit

[O] Omit todo pre-warning one day ahead

[Karl Voit]

Hi!

In my (daily) agenda, I see tomorrows tasks like this 

orgfile:   In   1 d.: NEXT Foo bar

How can I remove those pre-warning entries from my agenda? I could
not spot such a switch in the manual so far :-(

Thank you!

-- 
Karl Voit

Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Carsten Dominik]

Applied, thanks!

- Carsten

On Mar 16, 2012, at 3:13 PM, Ilya Shlyakhter wrote:

 On 3/16/2012 2:10 AM, Nick Dokos wrote:
  One more thing that you'll need to do is put your patches in attachments
  of a type that will allow patchwork to snag the patch:
 
 Thanks, I was wondering why they're not showing up.
 Here is another try (attached) for the org.el patch.
 
 ilya
 0002-Tags-properties-matcher-faster-matching-by-trusting-.patch

- Carsten

Re: [O] [PATCH] tags search: faster tags matcher by trusting scanner tags

[Carsten Dominik]

This one again did not make it to patchwork, but I have applied it anyway, 
thanks.

- Carsten

On Mar 16, 2012, at 3:20 PM, Ilya Shlyakhter wrote:

 On 3/16/2012 2:10 AM, Nick Dokos wrote:
 One more thing that you'll need to do is put your patches in attachments
 of a type that will allow patchwork to snag the patch:
 
 And here is the org-clock.el patch again.
 
 0003-Clocking-work-time-faster-filtering-of-clock-entries.patch

- Carsten

[O] org-table-recalculate-buffer-tables

[Aitor]

Hi,

I don't manage to use the 'org-table-recalculate-buffer-tables' function within
org-mode (version 7.8.03). It just doesn't show up when I do M-x

In fact, if I want to use it I have to apply the following patch: 

Modified   lisp/org.el
diff --git a/lisp/org.el b/lisp/org.el
index 3b06347..0bbb119 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -3839,7 +3839,7 @@ This works for both table types.)
org-table-move-column-right org-table-move-row
org-table-move-row-down org-table-move-row-up
org-table-next-field org-table-next-row org-table-paste-rectangle
-   org-table-previous-field org-table-recalculate
+   org-table-previous-field org-table-recalculate
org-table-recalculate-buffer-tables
org-table-rotate-recalc-marks org-table-sort-lines org-table-sum
org-table-toggle-coordinate-overlays
org-table-toggle-formula-debugger org-table-wrap-region


Is there something I am doing wrong ?

best,
  aitor

Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

[Nick Dokos]

Karl Voit devn...@karl-voit.at wrote:

 Since no followup reaction occured: is this a but that requires much
 work? Or did my email just got lost in overfull inboxes? :-)
 

For me, it was a no time to work on org - stash it...

 * Karl Voit devn...@karl-voit.at wrote:
 
  I verified the behavior below with the most current git version of
  Org-mode.
 
  Whenever I call my function to export the current agenda, it
  converts that do have a beginning and end time to events
  that span the whole day (without begin and end times at all).
 
  ,[ my LISP command to export ]
 | (defun vk-export-agenda()
 |   Exports monthly Org-mode agenda to agenda.ics file
 |   (interactive)
 |   (org-agenda-list nil nil 60)
 |   (org-agenda-write ~/org/agenda.ics)
 | )
  `
 
  I traced down the problem to this:
 
  * 2012-03-05 Mon 08:00-09:00 works fine
  * 2012-03-05 Mon 8:00-9:00 works fine too
 
  * 2012-03-05 08:00-09:00 Wrong: ends up as full day event
 
  Unfortunately, I do have certain mechanisms that generate parts of
  my Org-mode files where I skip the day of the week. Org-mode in
  general is able to handle date stamps without day of week pretty
  well. But whenever I export it to ics (in order to send it to
  Google), I end up with a messed up online agenda.
 
  I guess that org-agenda-write is the one to blame. It would be very
  handy to me if somebody could fix that issue.

org-agenda-write calls org-export-icalendar which calls 
org-print-icalendar-entries
which loops over all the entries and parses them, decomposing them into 
timestamps.
Each timestamp is then passed to org-parse-time-string. It's this one that 
cannot
handle non-standard formats: it uses a regexp and assumes that all the matched 
parts
are going to be in fixed places:

,
| (defun org-parse-time-string (s optional nodefault)
|   Parse the standard Org-mode time string.
| This should be a lot faster than the normal `parse-time-string'.
| If time is not given, defaults to 0:00.  However, with optional NODEFAULT,
| hour and minute fields will be nil if not given.
|   (if (string-match org-ts-regexp0 s)
|   (list 0
|   (if (or (match-beginning 8) (not nodefault))
|   (string-to-number (or (match-string 8 s) 0)))
|   (if (or (match-beginning 7) (not nodefault))
|   (string-to-number (or (match-string 7 s) 0)))
|   (string-to-number (match-string 4 s))
|   (string-to-number (match-string 3 s))
|   (string-to-number (match-string 2 s))
|   nil nil nil)
| (error Not a standard Org-mode time string: %s s)))
`

You can evaluate the following in your *scratch* buffer to verify:

--8---cut here---start-8---
(org-parse-time-string 2012-03-05 Mon 08:00)
(0 0 8 5 3 2012 nil nil nil)

(org-parse-time-string 2012-03-05 08:00)
(0 0 0 5 3 2012 nil nil nil)
--8---cut here---end---8---

As you can see, the time has disappeared.

As to how to fix it, there are several possibilities:

1. fix your scripts that produce time stamps to include day-of-week.
2. change the callers of org-parse-time-string to make sure that DOW is 
included.
3. change just one caller: org-print-icalendar-entries to make sure that DOW is 
included.
4. change org-parse-time-string to handle a missing DOW.

There are roughly three dozen callers, so 2. is possible but a pain.
3. is simple but ugly as sin, 4. is the best way to handle it within org.

I vote for 1. where *you* have to do all the work ;-)

Nick

Re: [O] entering inactive timestamp 7.2.12 results in [2012-03-16 Fr]

[Rainer Stengele]

Hi Ali,

I already have european style configured but that does not accept dd.mm.yy
Seems I have to stick with dd.mm. - no major problem, I just thought this 
could be configured a little bit more detailled.

Thanks,
Rainer

Am 16.03.2012 11:22, schrieb suvayu ali:
 Hi Rainer,
 
 On Fri, Mar 16, 2012 at 11:12, Rainer Stengele
 rainer.steng...@online.de wrote:
 Hi all,

 Entering 7.2.12 as an incative timestamp (C-c !)

 I get [2012-03-16 Fr].

 Entering 7.2.2012 results in [2012-02-07 Di].

 I have german settings in my emacs.
 Is there a chance to get wanted behaviour?

 dd.mm.yy seems to be a standard calendar date format.

 
 You could try customising `calendar-date-style'.
 

Re: [O] Bug: columnview times don't accumulate properly [7.8.03 (release_7.8.03.576.gbeb02)]

[Achim Gratz]

Myles English mylesengl...@gmail.com writes:
 I am an elisp novice so please would someone check this before I tag it
 as a [PATCH].  In particular, something I am not sure about is the
 (require 'org-inlinetask) which obviously introduces a dependency.

What problem were you trying to solve when you added it?  It doesn't
appear to be needed at runtime (org-inlinetask-min-level is an
autoloaded symbol).  If you need it during compilation, it should be
wrapped into an eval-when-compile at the beginning of the source file.


HTH,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

Waldorf MIDI Implementation  additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

Re: [O] [Bug] Regression w/ insert into tables in overwrite-mode

[Achim Gratz]

Achim Gratz strom...@nexgo.de writes:
 Commit 00040e7 by David Maus has introduced a regression when inserting
 into org tables while overwrite mode is on.  For each character inserted
 into a table cell, the cell (and the whole table row) gets shortened by
 one character.

 If the change can not be reverted, the deletion must not
 happen when overwrite mode is on, maybe through something like this:

   (if (not overwrite-mode) (delete-char -1))

 Emacs24 actually does not have the doc string that admonishes not to use
 the function delete-backward-char in non-interactive mode, so the point
 of the commit may actually be moot (although neither the doc string of
 delete-char nor delete-backward char make much mention of overwrite
 mode).  Interestingly, even though I am inside the table,
 org-self-insert-command gets called and not orgtbl-self-insert-command,
 so I can't really say if both changes would need to be fixed in the same
 way.

 Additionally, it appears that the implementation and the doc string for
 orgtbl-self-insert-command don't match, there doesn't seem to be any use
 of overwrite mode in its implementation.

*Bump*


Regards,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] org-table-recalculate-buffer-tables

[Nick Dokos]

Aitor aitors2...@gmail.com wrote:

 
 Hi,
 
 I don't manage to use the 'org-table-recalculate-buffer-tables' function 
 within
 org-mode (version 7.8.03). It just doesn't show up when I do M-x
 
 In fact, if I want to use it I have to apply the following patch: 
 
 Modified   lisp/org.el
 diff --git a/lisp/org.el b/lisp/org.el
 index 3b06347..0bbb119 100644
 --- a/lisp/org.el
 +++ b/lisp/org.el
 @@ -3839,7 +3839,7 @@ This works for both table types.)
 org-table-move-column-right org-table-move-row
 org-table-move-row-down org-table-move-row-up
 org-table-next-field org-table-next-row org-table-paste-rectangle
 -   org-table-previous-field org-table-recalculate
 +   org-table-previous-field org-table-recalculate
 org-table-recalculate-buffer-tables
 org-table-rotate-recalc-marks org-table-sort-lines org-table-sum
 org-table-toggle-coordinate-overlays
 org-table-toggle-formula-debugger org-table-wrap-region
 
 
 Is there something I am doing wrong ?
 

This is a general problem with autoloads in emacs and there will be
differing opinions on how far org (or whatever other package you are
trying to use) should go in order to solve it.

In my opinion, org just has to provide enough autoloads/requires/etc to
satisfy whatever dependencies *it* has, in order to initialize itself
fully. From that point on, any requirements *you* have are best
addressed by you in your environment.  You can do that by adding
something like this to your .emacs:

 (autoload org-table 'org-table-recalculate-buffer-tables)

or

 (require 'org-table)

The first one is quicker during initialization and pays the penalty to
load the file the first time that you use the function. The second pays
the penalty up front, but if you know you are going to use a bunch of
table function in every emacs instance you start, it might make more
sense since you don't have to provide individual autoloads. Take your
pick.

Either way, the function will be there when *you* need it.

Nick

Re: [O] patch

[Bastien]

Hi Uwe,

Uwe Brauer o...@mat.ucm.es writes:

 Here comes the patch (I tested it with Xemacs 21.5 and GNU
 emacs 23.1); I used the 
 diff -u option and hope this is ok.

Applied, thanks for the patch.

-- 
 Bastien

Re: [O] [PATCH] Fix org-agenda-skip-if bug

[Bastien]

Hi Toby,

Toby Cubitt ts...@cantab.net writes:

 There appears to be a bug in how org-agenda-skip-if parses the list of
 CONDITIONS supplied to it.

Applied, thanks.  

 The combination '(nottodo todo) is a valid condition, matching todo items
 whose state isn't a todo-type keyword (according to the keyword types
 defined in `org-todo-keywords'). But `org-agenda-skip-if' tests first for
 conditions of the form '(todo x) using (memq 'todo conditions), which
 mistakenly picks up '(nottodo todo) as well.

 Simply reversing the order of the memq tests for 'todo and 'nottodo fixes
 this particular case, which is what the attached patch does.

Thanks for the explanations.

 Note that there's still a slightly different issue with combinations of
 multiple todo tests, which this patch does not fix. The docstring
 suggests that CONDITIONS is allowed to be a list of multiple
 tests. E.g. '(nottodo CANCELLED todo done) should match any done state
 except CANCELLED. But, faced with this combination,
 `organ-agenda-skip-if' will only apply the first '(nottodo CANCELLED)
 test, and ignores the second.

 However, it's not clear to me whether this is a problem with the code or
 the docstring. Perhaps it was never intended to support combinations of
 multiple todo tests.

I don't know.  If someone can digg this issue further and report what
should be fixed, that'd help.

Thanks!

-- 
 Bastien

Re: [O] bugfix for org-agenda-follow-indirect

[Bastien]

Hi Dave,

Dave Abrahams d...@boostpro.com writes:

 Please try/apply enclosed patch:

I applied the last part of the patch, as the rest didn't apply
correctly.

Thanks.

-- 
 Bastien

Re: [O] [PATCH] org-store-link: Fixed a bug where source block edit buffers were not recognized

[Bastien]

Hi Ilya,

Ilya Shlyakhter ilya_...@alum.mit.edu writes:

 attached.

Applied, thanks a lot.

-- 
 Bastien

Re: [O] Bug: Habit consistency graph redisplay bug involving filters [7.8.03 (release_7.4.2711.gc2c5.dirty)]

[Bastien]

Hi Thomas,

Thomas Morgan t...@ziiuu.com writes:

 I've been noticing that some habit consistency graphs get wiped out
 by clocking in; I'd like to offer this minimal test case and patch.

I can reproduce the problem and I confirm your patch fixes it.

Applied, thanks!

-- 
 Bastien

Re: [O] [PATCH] Fixed compiler warnings including one small bug in ob-lilypond

[Achim Gratz]

Ilya Shlyakhter ilya_...@alum.mit.edu writes:

 +(require 'format-spec)
[...]
 +(declare-function format-spec format-spec (format specification))

Only one of these two lines should be necessary?


Regards,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: [O] [bug] org-agenda-write does not handle date stamps without day of week

[Karl Voit]

* Nick Dokos nicholas.do...@hp.com wrote:
 Karl Voit devn...@karl-voit.at wrote:

 For me, it was a no time to work on org - stash it...

OK. I just wanted to make sure that it *is* on someone's todo list
:-)

 * Karl Voit devn...@karl-voit.at wrote:
 
  * 2012-03-05 08:00-09:00 Wrong: ends up as full day event

 org-agenda-write calls org-export-icalendar which calls 
 org-print-icalendar-entries
 which loops over all the entries and parses them, decomposing them into 
 timestamps.
 Each timestamp is then passed to org-parse-time-string. It's this one that 
 cannot
 handle non-standard formats: it uses a regexp and assumes that all the 
 matched parts
 are going to be in fixed places:

 As to how to fix it, there are several possibilities:

 1. fix your scripts that produce time stamps to include day-of-week.

Sorry, deriving DOW from an arbitrary timestamps from arbitrary data
sources is either pretty time consuming (calendar calculations) or
simply hard to calculate.

Outside Org-mode, DOW is seldom part of time-stamp data :-(

 2. change the callers of org-parse-time-string to make sure that DOW is 
 included.
 There are roughly three dozen callers, so 2. is possible but a pain.

Ack.

 3. change just one caller: org-print-icalendar-entries to make sure that DOW 
 is included.
 3. is simple but ugly as sin, 

Ouch, ack :-)

 4. change org-parse-time-string to handle a missing DOW.
 4. is the best way to handle it within org.

Full ack.

 I vote for 1. where *you* have to do all the work ;-)

YMMD :-)

If my brain would be compatible to ELISP, I'd send a patch.
Promised.

But I'll take my chance and wait for someone else (you?)
implementing 4. to resolve this issue for everybody. I really
appreciate every second you guys invest in maintaining Org-mode!

-- 
Karl Voit

Re: [O] Omit todo pre-warning one day ahead

[Enrico Schumann]

Hi Karl,

does this what you want?

* TODO test
  DEADLINE: 2012-03-17 Sa -0d

(see 
http://orgmode.org/manual/Deadlines-and-scheduling.html#Deadlines-and-scheduling)


Regards,
Enrico


Am 16.03.2012 17:22, schrieb Karl Voit:
 Hi!

 In my (daily) agenda, I see tomorrows tasks like this

  orgfile:   In   1 d.: NEXT Foo bar

 How can I remove those pre-warning entries from my agenda? I could
 not spot such a switch in the manual so far :-(

 Thank you!


--
Enrico Schumann
Lucerne, Switzerland
http://nmof.net/

Re: [O] Omit todo pre-warning one day ahead

[Karl Voit]

Hi Enrico!

* Enrico Schumann enricoschum...@yahoo.de wrote:

 does this what you want?
 * TODO test
DEADLINE: 2012-03-17 Sa -0d

Absolutely. I completely forgot about this feature :-(

Thanks for reminding!

-- 
Karl Voit

[O] Error 500 with org2blog with wordpress

[Alvar Maciel]

Hi to all,
I'm a begginer so... be nice with me please. I manage to use org-mode
for almost all my daily work. I'm trying to post to my blog (worpdtess
3.3.1) from org-mode using org2blog. But when I try to post something
I get an 500 error. this is the output of emacs mini-buffer
progn: Error during request: 500
Can you give me any clue to solve this
Regards
Alvar

-- 
Identi.ca:@amaciel
Twitter:@amaciel
Blogs: http://acercadelaeducacion.com.ar

[O] Org release 7.8.04 (BUGFIX-only release)

[Bastien]

Hi all,

I have just released Org 7.8.04 -- a BUGFIX-only release.

This is the version that we will merge into Emacs' trunk,
and the one that will probably be shipped with Emacs 24.1
(soon to be released.)

Org 7.8.04 does not contains the latest git version of 
the master branch, only that of the maint branch.

If there are critical bugs that need to be fixed before
Emacs 24.1, please point to them right now -- I will do
the merge tomorrow at noon.

Thanks to everyone who contributed to this release.

And special thanks to Eric who did all the maintainance
work behind the scene.

Enjoy!

  http://orgmode.org/org-7.8.04.zip
  http://orgmode.org/org-7.8.04.tar.gz
  http://orgmode.org/org-mode-download.html

-- 
 Bastien

Re: [O] Error 500 with org2blog with wordpress

[Achim Gratz]

Alvar Maciel alvarmac...@gmail.com writes:
 I'm a begginer so... be nice with me please. I manage to use org-mode
 for almost all my daily work. I'm trying to post to my blog (worpdtess
 3.3.1) from org-mode using org2blog. But when I try to post something
 I get an 500 error. this is the output of emacs mini-buffer
 progn: Error during request: 500
 Can you give me any clue to solve this

HTTP error 500 is an internal server error (due to misconfiguration or
other problems).  You have to solve the problem on the server, not the
client.


Regards,
Achim.
-- 
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

[O] ical export not respecting tags

[Sample Hampton]

Users,

I am fairly new to org, but I am getting a pretty good handle on it.  I 
am having an issue with ical export.  When I export to html my tags (the 
only one of which I am using is :export:) is respected.  In the 
resultant html file only those entries and trees with the :export: tag 
are displayed.


When I export to ical, however, everything in the .org file is 
displayed.  From looking at the manual it would appear that I need to 
configure the variable org-icalendar-categories, but I do not know 
what that piece of language would look like.


I would immensely appreciate the help of the list with this issue.

Thank you,
Sample

[O] latex export R code syntax highlighting with minted

[Ista Zahn]

Hi all,

I'm having trouble modifying the example at
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
to highlight R code blocks. The trouble seems to be that org-mode
identifies R blocks using uppercase R, while pygments looks for
lowercase r.

For example, org exports

\begin{minted}{R}
 2+2
\end{minted}

but pygments doesn't know how to highlight R. If I change to

\begin{minted}{r}
 2+2
\end{minted}

(note the lower case r) then it works, but of course I don't want to
have to perform a find-and-replace every time.

Do you know how to either a) make org-mode identify R blocks with a
lowercase r, or b) make pygments recognize uppercase R, or c) some
other solution I've overlooked?

Thanks!
Ista

Re: [O] latex export R code syntax highlighting with minted

[Christophe Pouzat]

Ista Zahn istaz...@gmail.com writes:

 Hi all,

 I'm having trouble modifying the example at
 http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
 to highlight R code blocks. The trouble seems to be that org-mode
 identifies R blocks using uppercase R, while pygments looks for
 lowercase r.

 For example, org exports

 \begin{minted}{R}
  2+2
 \end{minted}

 but pygments doesn't know how to highlight R. If I change to

 \begin{minted}{r}
  2+2
 \end{minted}

 (note the lower case r) then it works, but of course I don't want to
 have to perform a find-and-replace every time.

 Do you know how to either a) make org-mode identify R blocks with a
 lowercase r, or b) make pygments recognize uppercase R, or c) some
 other solution I've overlooked?

 Thanks!
 Ista



Hi Ista,

Put the following expression:

(add-to-list 'org-export-latex-minted-langs '(R r))  

in an emacs-lisp code block at the beginning of your org file (or in the
*scratch* buffer) and evaluate it.

Christophe
  
-- 

Président, Nicolas Sarkozy représente une sorte de triomphe bouffon de 
l'égalitarisme français ; pour la première fois de notre histoire, nous avons 
un chef de l'État qui se comporte comme s'il ne valait pas mieux que les 
citoyens. C'est en réalité toujours le cas, mais cette vérité doit être cachée 
pour que les institutions et le système social tournent de façon, si ce n'est 
harmonieuse, du moins raisonnable.

E. Todd, Après la démocratie. 
--

Christophe Pouzat
MAP5 - Mathématiques Appliquées à Paris 5
CNRS UMR 8145
45, rue des Saints-Pères
75006 PARIS
France

tel: +33142863828
mobile: +33662941034
web: http://www.biomedicale.univ-paris5.fr/physcerv/C_Pouzat.html

[O] [PATCH] documentation patch clarifying ITEM special property

[Ilya Shlyakhter]

Documentation patch clarifying that ITEM refers to the headline not the 
contents of an entry, and that it currently isn't supported for 
tags/property searchers.  Added a footnote pointing to a partial

workaround using org-agenda-skip-entry-if.

From 33ccb4f2d3dc352e54c18b7bb88b1be90f6067cf Mon Sep 17 00:00:00 2001
From: Ilya Shlyakhter ilya_...@alum.mit.edu
Date: Fri, 16 Mar 2012 17:33:36 -0400
Subject: [PATCH 2/2] Documentation: Clarified current role of ITEM special 
 property

doc/org.texi (section on Special Properties) Clarified that ITEM refers
to the headline of the entry not the whole entry text.
(section on Matching Tags and Properties) Clarified that matching on
the value of ITEM special property is not currently supported,
and added a footnote about a partial workaround.
Also added missing -if suffix to references to org-agenda-skip-entry-if.

TINYCHANGE
---
 doc/org.texi |   10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 181ccd9..2c6168a 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4953,7 +4953,7 @@ TIMESTAMP_IA @r{The first inactive timestamp in the 
entry.}
 CLOCKSUM @r{The sum of CLOCK intervals in the subtree.  
@code{org-clock-sum}}
  @r{must be run first to compute the values in the current buffer.}
 BLOCKED  @r{t if task is currently blocked by children or siblings}
-ITEM @r{The content of the entry.}
+ITEM @r{The headline of the entry.}
 FILE @r{The filename the entry is located in.}
 @end example
 
@@ -7536,6 +7536,9 @@ So a search @samp{+LEVEL=3+boss-TODO=DONE} lists all 
level three headlines
 that have the tag @samp{boss} and are @emph{not} marked with the TODO keyword
 DONE.  In buffers with @code{org-odd-levels-only} set, @samp{LEVEL} does not
 count the number of stars, but @samp{LEVEL=2} will correspond to 3 stars etc.
+The ITEM special property cannot currently be used in tags/property
+searches@footnote{But @pxref{x-agenda-skip-entry-regexp,
+,skipping entries based on regexp}.}.
 
 Here are more examples:
 @table @samp
@@ -15876,9 +15879,10 @@ Skip current entry if the TODO keyword is TODO or 
WAITING.
 Skip current entry if the TODO keyword marks a DONE state.
 @item (org-agenda-skip-entry-if 'timestamp)
 Skip current entry if it has any timestamp, may also be deadline or scheduled.
-@item (org-agenda-skip-entry 'regexp regular expression)
+@anchor{x-agenda-skip-entry-regexp}
+@item (org-agenda-skip-entry-if 'regexp regular expression)
 Skip current entry if the regular expression matches in the entry.
-@item (org-agenda-skip-entry 'notregexp regular expression)
+@item (org-agenda-skip-entry-if 'notregexp regular expression)
 Skip current entry unless the regular expression matches.
 @item (org-agenda-skip-subtree-if 'regexp regular expression)
 Same as above, but check and skip the entire subtree.
-- 
1.7.9.3

Re: [O] latex export R code syntax highlighting with minted

[Ista Zahn]

Ah, perfect! Thank you.

On Fri, Mar 16, 2012 at 5:13 PM, Christophe Pouzat
christophe.pou...@gmail.com wrote:
 (add-to-list 'org-export-latex-minted-langs '(R r))

Re: [O] latex export R code syntax highlighting with minted

[Nick Dokos]

Ista Zahn istaz...@gmail.com wrote:

 Hi all,
 
 I'm having trouble modifying the example at
 http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
 to highlight R code blocks. The trouble seems to be that org-mode
 identifies R blocks using uppercase R, while pygments looks for
 lowercase r.
 
 For example, org exports
 
 \begin{minted}{R}
  2+2
 \end{minted}
 
 but pygments doesn't know how to highlight R. If I change to
 
 \begin{minted}{r}
  2+2
 \end{minted}
 
 (note the lower case r) then it works, but of course I don't want to
 have to perform a find-and-replace every time.
 
 Do you know how to either a) make org-mode identify R blocks with a
 lowercase r, or b) make pygments recognize uppercase R, or c) some
 other solution I've overlooked?
 

Christophe provided the org solution a) and obviously that's the way to go
(maybe one of you could provide a patch to change the default value of
org-export-latex-minted-langs to add the R setting?)

For completeness, and of theoretical interest only, here's how to do b).

o Find the directory where pygments is installed. I just started python
  imported pygments and asked for help:

,
| $ python
| Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53) 
| [GCC 4.5.2] on linux2
| Type help, copyright, credits or license for more information.
|  import pygments
|  help(pygments)
| Help on package pygments:
| 
| NAME
| pygments
| 
| FILE
| /usr/lib/python2.7/dist-packages/pygments/__init__.py
| ...  
`

o cd /path/to/pygments/lexers, edit the file math.py (you probably have
  to be root) and add the 'R' alias for 'S':

,
| ...
| name = 'S'
| aliases = ['splus', 's', 'r', 'R']
| filenames = ['*.S', '*.R']
| mimetypes = ['text/S-plus', 'text/S', 'text/R']
| ...
`

o run (as root) the _mapping.py script to regenerate stuff:

,
| $ sudo python _mapping.py
`

Nick





  

[O] meaning of body-only in org-export-as-html

[Chris Gray]

Hello,

I am using org-export-as-html with the body-only parameter set to t
in the org plugin for ikiwiki that I'm working on.  It works almost
perfectly, but I recently had a user point out that it's not possible to
get a table of contents, even when one is explicitly asked for in the
#+OPTIONS line of the org file.

Since the table of contents is part of the body (at least in the sense
that it is between the body tags), I found this surprising.  So would
it cause problems to change the line

(if (and org-export-with-toc (not body-only))
...)

to

(if org-export-with-toc
...)

in org-export-as-html?  

Cheers,
Chris

Re: [O] entering inactive timestamp 7.2.12 results in [2012-03-16 Fr]

[Frank Haun]

Rainer Stengele rainer.steng...@online.de writes:

 Entering 7.2.12 as an incative timestamp (C-c !)

 I get [2012-03-16 Fr].

 Entering 7.2.2012 results in [2012-02-07 Di].

 I have german settings in my emacs.
 Is there a chance to get wanted behaviour?

 dd.mm.yy seems to be a standard calendar date format.

I think its not possible, from org.el:

#v+
  (defconst org-time-stamp-formats '(%Y-%m-%d %a . %Y-%m-%d %a %H:%M)
Formats for `format-time-string' which are used for time stamps.
It is not recommended to change this constant.)
#v-


One solution is to customize `org-time-stamp-custom-formats'.

Use `#+STARTUP: customtime' in your file or/and set
`org-display-custom-times' to `t'. Hm, and you should read this
http://orgmode.org/manual/Custom-time-format.html.

Frank
-- 
http://fhaun.blogspot.com/