[O] encrypted items, but not timestamp

2014-02-20 Thread David Belohrad

Dear all,

I have followed this:

http://orgmode.org/worg/org-tutorials/encrypting-files.html

to encrypt subtree of my journal. So e.g. something like this:

 testing subree encryption :crypt:
this text should be encrypted when saved on the disk using my private
key. will see if this works
Entered on 2014-02-20 Thu 09:05


it works, however it encrypts entire subtree including 'entered on
timestamp'. This puts a little issue on this, as when in journal,
these timestamps are used in agenda buffer to display the heading. And I
want this heading to be displayed in my agenda, including all the tags
it exhibits.

Is there any way how to achieve this? For the moment the only thing
coming into my mind is to make a timestamp part of heading, which is not
what I really want.


Thanks

.d.




Re: [O] org-export-latex-hyperref-options-format

2014-02-20 Thread Nicolas Goaziou
Hello,

Joe Hirn joseph.h...@gmail.com writes:

 Hi just sat down to code this up. I assume the keywords are so we can use
 data within the plist argument (info) passed to `org-latex-template'. But
 I'm not exactly sure what you mean by %k for keywords.

 Are you suggesting we could do something like:

 \\hypersetup{\n  pdfkeywords={%kkeywords},\n
  pdfsubject={%kdescription},\n  pdfcreator={%kcreator}}\n

 If that's the idea, is there a more powerful construct than regex matching
 for achieving this? Otherwise, can you give me an example of what you had
 in mind for the keyword placeholders.

I'm suggesting to use `format-spec', e.g., something like:

  (and org-latex-hyperref-template
   (format-spec org-latex-hyperref-template
(format-spec-make
 ?k (or (plist-get info :keywords) )
 ?d (or (plist-get info :description) )
 ?c (if (not (plist-get info :with-creator)) 
  (plist-get info :creator)

Thus, when `org-latex-hyperref-template' is nil, no \hyperref command
is inserted, otherwise, it is a format string where %k is replaced with
KEYWORDS, %d with DESCRIPTION and %c with CREATOR.

Default value for the variable would be:

  \\hypersetup{\n  pdfkeywords={%k},\n  pdfsubject={%d},\n  pdfcreator={%c}}\n

A (require 'format-spec) will be needed in the beginning of
ox-latex.el.


Regards,

-- 
Nicolas Goaziou



Re: [O] for your amusement

2014-02-20 Thread Nicolas Richard
[fu2 gmane.emacs.bbdb.user]

Eric Abrahamsen e...@ericabrahamsen.net writes:
 Incidentally, I'm using `ido-everywhere', and would like to write this
 function so that it didn't _rely_ on ido, but made use of ido when
 `ido-everywhere' was true. Ie, I'd like to replace the
 `ido-completing-read' calls with something more generic that still made
 use of ido when it was turned on. Any suggestions?

ido-everywhere is only meant for buffer/file (see its docstring). People
who really want ido everywhere should probably use ido-ubiquitous which
sets completing-read-function to ido-completing-read (in fact, a wrapper
around it because it cannot handle all cases that completing-read should
handle).

Hence, my suggestion would be to use completing-read instead of
ido-completing-read in your code, and configure ido-ubiquitous
(available from marmalade and melpa) for controlling what to use.

Related package : ido-hacks (which also enables ido in more places)

I *guess* it'll then also work automagically with icomplete-mode
(shipped with recent emacs) if that is what the user enable instead of
ido-ubiquitous.

-- 
Nico.




Re: [O] for your amusement

2014-02-20 Thread Eric Abrahamsen
Nicolas Richard theonewiththeevill...@yahoo.fr writes:

 [fu2 gmane.emacs.bbdb.user]

 Eric Abrahamsen e...@ericabrahamsen.net writes:
 Incidentally, I'm using `ido-everywhere', and would like to write this
 function so that it didn't _rely_ on ido, but made use of ido when
 `ido-everywhere' was true. Ie, I'd like to replace the
 `ido-completing-read' calls with something more generic that still made
 use of ido when it was turned on. Any suggestions?

 ido-everywhere is only meant for buffer/file (see its docstring). People
 who really want ido everywhere should probably use ido-ubiquitous which
 sets completing-read-function to ido-completing-read (in fact, a wrapper
 around it because it cannot handle all cases that completing-read should
 handle).

 Hence, my suggestion would be to use completing-read instead of
 ido-completing-read in your code, and configure ido-ubiquitous
 (available from marmalade and melpa) for controlling what to use.

 Related package : ido-hacks (which also enables ido in more places)

 I *guess* it'll then also work automagically with icomplete-mode
 (shipped with recent emacs) if that is what the user enable instead of
 ido-ubiquitous.

Gosh, where did you guys dig this thread up from? :)

Thanks for the refinements on the original function, and for the tips on
ido related packages in elpa repos -- I hadn't been aware of that. I've
been a tiny bit annoyed with this function ever since I wrote it
(obviously not annoyed enough, since that was years ago), as progressive
narrowing didn't work the way I wanted it to. Kevin, I'll give your
version a whack, and maybe come back with some more refinements in a
bit.

Thanks!
E




Re: [O] for your amusement

2014-02-20 Thread Nicolas Richard
Eric Abrahamsen e...@ericabrahamsen.net writes:
 Gosh, where did you guys dig this thread up from? :)

Oops, I didn't notice the date of your original message. I answered
because of Kevin's answer.

-- 
Nico.




Re: [O] org-export-latex-hyperref-options-format

2014-02-20 Thread Joseph Hirn
Ok. I was hesitant to require anything additional but I should be able
to knock this out.

Thx again.

Sent from my iPhone

 On Feb 20, 2014, at 4:22 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:

 Hello,

 Joe Hirn joseph.h...@gmail.com writes:

 Hi just sat down to code this up. I assume the keywords are so we can use
 data within the plist argument (info) passed to `org-latex-template'. But
 I'm not exactly sure what you mean by %k for keywords.

 Are you suggesting we could do something like:

 \\hypersetup{\n  pdfkeywords={%kkeywords},\n
 pdfsubject={%kdescription},\n  pdfcreator={%kcreator}}\n

 If that's the idea, is there a more powerful construct than regex matching
 for achieving this? Otherwise, can you give me an example of what you had
 in mind for the keyword placeholders.

 I'm suggesting to use `format-spec', e.g., something like:

  (and org-latex-hyperref-template
   (format-spec org-latex-hyperref-template
(format-spec-make
 ?k (or (plist-get info :keywords) )
 ?d (or (plist-get info :description) )
 ?c (if (not (plist-get info :with-creator)) 
  (plist-get info :creator)

 Thus, when `org-latex-hyperref-template' is nil, no \hyperref command
 is inserted, otherwise, it is a format string where %k is replaced with
 KEYWORDS, %d with DESCRIPTION and %c with CREATOR.

 Default value for the variable would be:

  \\hypersetup{\n  pdfkeywords={%k},\n  pdfsubject={%d},\n  
 pdfcreator={%c}}\n

 A (require 'format-spec) will be needed in the beginning of
 ox-latex.el.


 Regards,

 --
 Nicolas Goaziou



Re: [O] [RFC] Move ox-koma-letter into core?

2014-02-20 Thread Rasmus
Viktor Rosenfeld listuse...@gmail.com writes:

 Hi Tom,

 Am 17.02.14 22:56, schrieb Thomas S. Dye:

 FWIW, as a small businessman, the indemnification clause looks fairly
 standard to me.  The contracts for archaeological services that we
 routinely sign typically have a clause like this, usually coupled with a
 request for a certificate of insurance that specifies the levels of
 liability insurance that the business carries.

 As I read the clause, FSF is in the position of accepting 1) a code
 contribution from a developer, and 2) the developer's assurance that the
 contributed code can't be claimed as property by a third party.  It
 seems prudent that, in the event of a successful property claim by a
 third party to a piece of code contributed by a developer, the developer
 who gave the false assurance should be held responsible. Otherwise, FSF
 might be brought down by copyleft opponents who knowingly contribute
 code to which others have property rights in order to create a basis for
 lawsuits.

 Thanks for your reply. I was hoping to get some feedback on how other
 Orgmode contributors see this issue (although this list is obviously
 self-selective). The problem I have is that I'm not a lawyer or a
 businessman and not a native English speaker. I do know enough though
 not to lightly sign documents I don't fully understand.

Perhaps FSFE would be able to shed some light on the issue (EU-based).
Or Software Freedom Conservancy (US-based).  I don't have further
insights.

—Rasmus

-- 
May contains speling mistake




Re: [O] for your amusement

2014-02-20 Thread Eric Abrahamsen
Nicolas Richard theonewiththeevill...@yahoo.fr writes:

 Eric Abrahamsen e...@ericabrahamsen.net writes:
 Gosh, where did you guys dig this thread up from? :)

 Oops, I didn't notice the date of your original message. I answered
 because of Kevin's answer.

If we're still using (and improving) the snippet, it's still a relevant thread!




Re: [O] Does org export have something like Lisp quasiquote and unquote?

2014-02-20 Thread Eric Schulte
Oleh ohwoeo...@gmail.com writes:

 The following will do what you want.

 set the value
 #+begin_src lisp :results silent
 (defvar foo '(defun square (x)  (* x x)))
 #+end_src

 #+begin_src lisp :results output pp code
 foo
 #+end_src

 #+RESULTS:
 #+BEGIN_SRC lisp

 (DEFUN SQUARE (X) (* X X))
 #+END_SRC

 Best,

 --
 Eric Schulte
 https://cs.unm.edu/~eschulte
 PGP: 0x614CA05D

 Thanks, Eric,

 but this isn't what I had in mind.  I want the org-mode file to remain
 unchanged while behaving as if it was changed, something like C
 macros: C compiler is not aware of macros and I'm not aware of the
 expanded code, but we get along nicely anyway.


Think of code blocks as macros with optional interactive expansion.  If
you don't execute the code block you need not ever see the results,
however with an additional :exports results header argument the code
block will be executed and replaced with it's results on export.

Take a look at the (info (org) Working With Source Code) portion of
the Org-mode manual.

Hope this helps,


 First use-case is that I'm writing documentation for a library of
 functions, so some of them are mentioned a few times. I'd like to
 refer to them not by name, which can be subjected to change but by a
 file local variable.  For instance, I've got a link in a table
 referring to a heading. They both have the same name and I'd like to
 keep them consistent, but I don't want to do it manually.

 Second use-case is that I'm generating a HTML block with
 `htmlize-buffer' that I want to include in the document. I'd prefer
 not to have hundreds of lines of HTML that correspond to 3 lines of
 code that they're supposed to represent. I'd rather generate this HTML
 via this macro mechanism that I hope exists in some form, maybe in
 conjunction with a makefile-like mechanism.

 Here's the org file that I'm working on:
 https://raw.github.com/abo-abo/lispy/gh-pages/index.org.
 As you see a lot of redundancy there and also several huge ugly HTML blocks.
 Btw, is there a way to #include HTML blocks?
 Here's the export result: http://abo-abo.github.io/lispy/.

 regards,
 Oleh

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D



Re: [O] Does org export have something like Lisp quasiquote and unquote?

2014-02-20 Thread Oleh

 Think of code blocks as macros with optional interactive expansion.  If
 you don't execute the code block you need not ever see the results,
 however with an additional :exports results header argument the code
 block will be executed and replaced with it's results on export.

 Take a look at the (info (org) Working With Source Code) portion of
 the Org-mode manual.


Thanks, I'll look there.
Is it possible to have a code block that evals to a string wrapped in
#+BEGIN_HTML, #+END_HTML and be treated as a HTML block on export?

regards,
Oleh



Re: [O] org-export-latex-hyperref-options-format

2014-02-20 Thread Joe Hirn
Hi Nicholas.

I was able to test this on my local machine and it seems to work as we
discussed.

If there are any other changes to the patch you'd like to see, please let
me know.

Thanks for your help. I really appreciate it.


BEGIN PATCH**
diff --git a/ox-latex.el b/ox-latex.el
index 19f055e..9ed6372 100644
--- a/ox-latex.el
+++ b/ox-latex.el
@@ -103,7 +103,7 @@
(:latex-class-options LATEX_CLASS_OPTIONS nil nil t)
(:latex-header LATEX_HEADER nil nil newline)
(:latex-header-extra LATEX_HEADER_EXTRA nil nil newline)
-   (:latex-hyperref-p nil texht org-latex-with-hyperref t)
+   (:latex-hyperref-p nil texht (if org-latex-hyperref-template t) t)
;; Redefine regular options.
(:date DATE nil \\today t)))

@@ -341,10 +341,11 @@ the toc:nil option, not to those generated with #+TOC
keyword.
   :group 'org-export-latex
   :type 'string)

-(defcustom org-latex-with-hyperref t
-  Toggle insertion of \\hypersetup{...} in the preamble.
+
+(defcustom org-latex-hyperref-template \\hypersetup{\n
 pdfkeywords={%k},\n  pdfsubject={%d},\n  pdfcreator={%c}}\n
+  The value of \\hyperrefsetup{...} in the preamble. String is a
format-spec which accepts keywords for %k (pdfkeywords), %d
(pdfdescription) and %c (pdfcreator). Set to nil for no \\hyperrefsetup.
   :group 'org-export-latex
-  :type 'boolean)
+  :type 'string)

  Headline

@@ -1119,11 +1120,13 @@ holding export options.
  (format \\title{%s}\n title)
  ;; Hyperref options.
  (when (plist-get info :latex-hyperref-p)
-   (format \\hypersetup{\n  pdfkeywords={%s},\n  pdfsubject={%s},\n
 pdfcreator={%s}}\n
-   (or (plist-get info :keywords) )
-   (or (plist-get info :description) )
-   (if (not (plist-get info :with-creator)) 
- (plist-get info :creator
+   (format-spec org-latex-hyperref-template
+(format-spec-make
+ ?k (or (plist-get info :keywords) )
+ ?d (or (plist-get info :description))
+ ?c (if (plist-get info :with-creator)
+(plist-get info :creator)
+  
  ;; Document start.
  \\begin{document}\n\n
  ;; Title command.
END  PATCH**


On Thu, Feb 20, 2014 at 6:34 AM, Joseph Hirn joseph.h...@gmail.com wrote:

 Ok. I was hesitant to require anything additional but I should be able
 to knock this out.

 Thx again.

 Sent from my iPhone

  On Feb 20, 2014, at 4:22 AM, Nicolas Goaziou n.goaz...@gmail.com
 wrote:
 
  Hello,
 
  Joe Hirn joseph.h...@gmail.com writes:
 
  Hi just sat down to code this up. I assume the keywords are so we can
 use
  data within the plist argument (info) passed to `org-latex-template'.
 But
  I'm not exactly sure what you mean by %k for keywords.
 
  Are you suggesting we could do something like:
 
  \\hypersetup{\n  pdfkeywords={%kkeywords},\n
  pdfsubject={%kdescription},\n  pdfcreator={%kcreator}}\n
 
  If that's the idea, is there a more powerful construct than regex
 matching
  for achieving this? Otherwise, can you give me an example of what you
 had
  in mind for the keyword placeholders.
 
  I'm suggesting to use `format-spec', e.g., something like:
 
   (and org-latex-hyperref-template
(format-spec org-latex-hyperref-template
 (format-spec-make
  ?k (or (plist-get info :keywords) )
  ?d (or (plist-get info :description) )
  ?c (if (not (plist-get info :with-creator)) 
   (plist-get info :creator)
 
  Thus, when `org-latex-hyperref-template' is nil, no \hyperref command
  is inserted, otherwise, it is a format string where %k is replaced with
  KEYWORDS, %d with DESCRIPTION and %c with CREATOR.
 
  Default value for the variable would be:
 
   \\hypersetup{\n  pdfkeywords={%k},\n  pdfsubject={%d},\n
  pdfcreator={%c}}\n
 
  A (require 'format-spec) will be needed in the beginning of
  ox-latex.el.
 
 
  Regards,
 
  --
  Nicolas Goaziou



Re: [O] Does org export have something like Lisp quasiquote and unquote?

2014-02-20 Thread Eric Schulte
Oleh ohwoeo...@gmail.com writes:


 Think of code blocks as macros with optional interactive expansion.  If
 you don't execute the code block you need not ever see the results,
 however with an additional :exports results header argument the code
 block will be executed and replaced with it's results on export.

 Take a look at the (info (org) Working With Source Code) portion of
 the Org-mode manual.


 Thanks, I'll look there.
 Is it possible to have a code block that evals to a string wrapped in
 #+BEGIN_HTML, #+END_HTML and be treated as a HTML block on export?


Yes, see (info (org) results).


 regards,
 Oleh

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D



[O] iCal-Export: Strange Results

2014-02-20 Thread G. Martin Butz

Hi,

today I tried to setup iCal-Export of one org file contributing to my 
agenda. As I use Mozilla Sunbird (resp. Iceowl) to keep track of my 
company dates synchronizing with a remote ical file, it seemed to be a 
good idea to have also my org dates available in Iceowl.


While importing and viewing one of my org files, I do get strange results:

+ I only see dates from DONE-entries
+ There might be e.g. an entry in the ical file/Iceowl dated to
  09:57, 2nd of December 2013
+ The body of the calendar entry in ical file/Iceowl contains:
  • State DONE from TODO [2013-12-02 Mo 09:57] meaning
  the entry is dated to the date and time I set the entry to DONE
+ I do not see any active TODO-entries at all

I tried the export using the default values of the export function (C-c 
C-e c f) described in http://orgmode.org/manual/iCalendar-export.html


I then set (org-icalendar-store-UID t) thinking it had something to do 
with it.


After some googling without any definite results I I scanned the 
org-icaendar-group an set some further variables. My setup now looks as 
following:


(org-combined-agenda-icalendar-file ~/ical/org.ics)
(org-icalendar-categories (quote (todo-state)))
(org-icalendar-include-todo t)
(org-icalendar-store-UID t)
(org-icalendar-use-plain-timestamp nil)

My org-mode-version is 8.2.4 with Emacs 24.3.1

Can anyone provide a hint, what am I doing wrong?

Best Regards
Martin

--

| G. Martin Butz, m...@mkblog.org, 0421 98749324, www.mkblog.org |




[O] Simple question re: use of conditional in cell formula

2014-02-20 Thread Subhan Tindall
Here's my clockreport setup:

'(org-agenda-clockreport-parameter-plist (quote (:link t :maxlevel 3
:formula $9=$2-$6;t::$8=$2-$5;t::$7=$2-$4;t :properties (\
Effort

portion of table output follows (as you can see my effort estimates are
sporadic, and vary in level

What I'd like to do, but can't seem to find the proper syntax for, is use a
conditional assignment so that
when there is no Effort value only a blank, or ***, or similar is in the
destination cell.
SImilarly, when there is no value in one of the time sub-columns the
corresponding cell is left blank

IE
instead of
|  |   0:15 | \_ DONE 2014-02-12 Wed email to david...  |
|   |  0:10 |   0.25 |   0.25 |   0.08 |
Id like to see:
|  |   0:15 | \_ DONE 2014-02-12 Wed email to david...  |
|   |  0:10 |  |  |   0.08 |
And instead of
|  || \__ Todos   |
|  0:45 |   |   0.00 |  -0.75 |   0.00 |
I'd like to see

|  || \__ Todos   |
|  0:45 |   |     | *   |     |

I have searched mightily and can't seem to find any syntax that will work
in my table.
Any ideas or help will be much appreciated!


And, while I'm on the topic, is there anyway way to get a column in the
clocktable to display the sum of all
Effort estimates for it's displayed subtrees?  IE like this:
|  | 0:45 | JWRK PPTDEV-389 VBA macros  |
30:55 |   |   | -30.92 |   0.00 |   0.00 |   this is sum of
the two efforts below
|  || \__ Notes   |
| 30:10 |   |   0.00 | -30.17 |   0.00 |
|  || \_ NOTES Directions to Estimate Redbox...   |
|   | 30:10 |   0.00 |   0.00 | -30.17 |
|  || \__ Todos   |
|  0:45 |   |   0.00 |  -0.75 |   0.00 |
|  |   0:15 | \_ DONE 2014-02-12 Wed email to david...  |
|   |  0:10 |   0.25 |   0.25 |   0.08 |
|  || \_ DONE 2014-02-12 Wed update...  |
|   |  0:25 |   0.00 |   0.00 |  -0.42 |
|  |   0:30 | \_ DONE 2014-02-12 Wed change...  |
|   |  0:10 |   0.50 |   0.50 |   0.33 |



| File | Effort | Headline|
   Time |   |   ||||
|--++-+-+---+---+++|
|  |ALL | *Total time*|
*38:28* |   |   | -38.47 |   0.00 |   0.00 |
|--++-+-+---+---+++|
| Work-log.org || *File time* |
*38:28* |   |   | -38.47 |   0.00 |   0.00 |
|  || RECURING PPTDEV-514 Miscellaneous   |
   3:12 |   |   |  -3.20 |   0.00 |   0.00 |
|  || \__ W07 email, morning  |
|  3:12 |   |   0.00 |  -3.20 |   0.00 |
|  || RECURING PPTDEV-513 smt 2014 Meetings   |
   2:38 |   |   |  -2.63 |   0.00 |   0.00 |
|  |   0:45 | \__ DONE 2014-02-18 Tue meeting w/Miriam  |
|  0:40 |   |   0.75 |   0.08 |   0.75 |
|  || \__ Standup |
|  1:12 |   |   0.00 |  -1.20 |   0.00 |
|  || \__ pers. meeting w/steve re:floats, time...|
|  0:46 |   |   0.00 |  -0.77 |   0.00 |
|  || JWRK PPTDEV-318 HVE Industry - Feed...  |
   1:43 |   |   |  -1.72 |   0.00 |   0.00 |
|  |0.5 | \__ SPEC redo spec with RDE |
|  0:42 |   |   0.00 |  -0.70 |   0.00 |
|  |   0:30 | \_ TODO setup coding evironment  review... |
|   |  0:42 |   0.50 |   0.50 |  -0.20 |
|  || \__ TODO Modify...  |
|  1:01 |   |   0.00 |  -1.02 |   0.00 |
|  |4.5 | \_ NOTES developement notes from Rob|
|   |  1:01 |   0.00 |   0.00 |  -1.02 |
|  || JWRK PPTDEV-389 VBA macros  |
  30:55 |   |   | -30.92 |   0.00 |   0.00 |
|  || \__ Notes   |
| 30:10 |   |   0.00 | -30.17 |   0.00 |
|  || \_ NOTES Directions to Estimate Redbox...   |
|   | 30:10 |   0.00 |   0.00 | -30.17 |
|  || \__ Todos   |
|  0:45 |   |   0.00 |  -0.75 |   0.00 |
|  |   0:15 | 

Re: [O] org-export-latex-hyperref-options-format

2014-02-20 Thread Nicolas Goaziou
Hello,

Joe Hirn joseph.h...@gmail.com writes:

 I was able to test this on my local machine and it seems to work as we
 discussed.

 If there are any other changes to the patch you'd like to see, please let
 me know.

Thank you for the patch. Here are a few comments.

 -   (:latex-hyperref-p nil texht org-latex-with-hyperref t)
 +   (:latex-hyperref-p nil texht (if org-latex-hyperref-template t) t)

I think we can drop the -p suffix since this is no longer a predicate.
So the property can be named :latex-hyperref.

Also we can replace texht with nil since it doesn't make much sense to
specify a full template from the OPTIONS line.

Eventually, the default value should be `org-latex-hyperref-template'.

This boils down to the following line:

  (:latex-hyperref nil nil org-latex-hyperref-template t)

 -(defcustom org-latex-with-hyperref t
 -  Toggle insertion of \\hypersetup{...} in the preamble.
 +
 +(defcustom org-latex-hyperref-template \\hypersetup{\n
  pdfkeywords={%k},\n  pdfsubject={%d},\n  pdfcreator={%c}}\n
 +  The value of \\hyperrefsetup{...} in the preamble. String is a
 format-spec which accepts keywords for %k (pdfkeywords), %d
 (pdfdescription) and %c (pdfcreator). Set to nil for no \\hyperrefsetup.
:group 'org-export-latex
 -  :type 'boolean)
 +  :type 'string)

The first line of the docstring should contain complete sentences only.
I would say something along the lines:

  Template for hyperref package options.

Value is a format string, which can contain the following placeholders:

  %k for KEYWORDS line
  %d for DESCRIPTION line
  %c for CREATOR line

An empty string disables the setup.

Since you specify :type as 'string, it is wrong to expect a nil value in
the variable. Note that nil is not an absolute necessity. We can allow
to disable the template with an empty string instead.

 +   (format-spec org-latex-hyperref-template
 +(format-spec-make
 + ?k (or (plist-get info :keywords) )
 + ?d (or (plist-get info :description))
 + ?c (if (plist-get info :with-creator)
 +(plist-get info :creator)
 +  

You are not using the :latex-hyperref property. This should be:

  (format-spec (plist-get info :latex-hyperref)
   ...)


Regards,

-- 
Nicolas Goaziou



Re: [O] Simple question re: use of conditional in cell formula

2014-02-20 Thread Michael Brand
Hi Subhan

On Thu, Feb 20, 2014 at 9:05 PM, Subhan Tindall
subhan.tind...@rentrakmail.com wrote:
 What I'd like to do, but can't seem to find the proper syntax for,
 is use a conditional assignment so that when there is no Effort
 value only a blank, or ***, or similar is in the destination cell.
 SImilarly, when there is no value in one of the time sub-columns the
 corresponding cell is left blank

Are you looking for this?:

In the manual:
http://orgmode.org/manual/Formula-syntax-for-Calc.html

if($1 == nan || $2 == nan, string(), $1 + $2); E

Sum of the first two columns. When at least one of the input
fields is empty the Org table result field is set to empty.

In action: Look at the page with the Worg tutorials and in the
spreadsheet section follow the link to the Emacs Regression Test
(ERT) for Org tables with example use cases for TBLFM:
http://orgmode.org/worg/org-tutorials/index.html#Spreadsheet
In the ERT it is test-org-table/empty-field, specifically Test if
several fields are empty, else do a calculation.

 And, while I'm on the topic, is there anyway way to get a column in
 the clocktable to display the sum of all Effort estimates for it's
 displayed subtrees? IE like this:

I can't follow, maybe because I don't use clocking. Maybe you want to
use the hierarchical sum of a property in column view, here the
property Effort. See
http://orgmode.org/manual/Column-attributes.html
and
http://orgmode.org/manual/Capturing-column-view.html

Michael



Re: [O] Does org export have something like Lisp quasiquote and unquote?

2014-02-20 Thread Alan Schmitt
Eric Schulte schulte.e...@gmail.com writes:

 Oleh ohwoeo...@gmail.com writes:


 Think of code blocks as macros with optional interactive expansion.  If
 you don't execute the code block you need not ever see the results,
 however with an additional :exports results header argument the code
 block will be executed and replaced with it's results on export.

 Take a look at the (info (org) Working With Source Code) portion of
 the Org-mode manual.


 Thanks, I'll look there.
 Is it possible to have a code block that evals to a string wrapped in
 #+BEGIN_HTML, #+END_HTML and be treated as a HTML block on export?


 Yes, see (info (org) results).

As Eric suggested, the simplest is something like :results value html
or :results output html. But if you need something more involved,
please keep reading.

I recently had to use something similar, where the result of a code
block would need to be wrapped in #+begin_src / #+end_src. After much
help from this list, I ended up with this solution:
http://orgmode.org/worg/org-hacks.html#sec-1-10-4

You can ignore / replace the fetchsrc bit with the code you want to
evaluate, and adapt the wrap-coq to your setting.

Alan



Re: [O] org-export-latex-hyperref-options-format

2014-02-20 Thread Joe Hirn
I really appreciate your review. Sorry for the pedestrian code submission.
I don't get candid critical feedback on my e-lisp, so it's great to learn
more about its idioms and conventions.

I'll incorporate your feedback into a new patch.


On Thu, Feb 20, 2014 at 2:51 PM, Nicolas Goaziou n.goaz...@gmail.comwrote:

 Hello,

 Joe Hirn joseph.h...@gmail.com writes:

  I was able to test this on my local machine and it seems to work as we
  discussed.
 
  If there are any other changes to the patch you'd like to see, please let
  me know.

 Thank you for the patch. Here are a few comments.

  -   (:latex-hyperref-p nil texht org-latex-with-hyperref t)
  +   (:latex-hyperref-p nil texht (if org-latex-hyperref-template t) t)

 I think we can drop the -p suffix since this is no longer a predicate.
 So the property can be named :latex-hyperref.

 Also we can replace texht with nil since it doesn't make much sense to
 specify a full template from the OPTIONS line.

 Eventually, the default value should be `org-latex-hyperref-template'.

 This boils down to the following line:

   (:latex-hyperref nil nil org-latex-hyperref-template t)

  -(defcustom org-latex-with-hyperref t
  -  Toggle insertion of \\hypersetup{...} in the preamble.
  +
  +(defcustom org-latex-hyperref-template \\hypersetup{\n
   pdfkeywords={%k},\n  pdfsubject={%d},\n  pdfcreator={%c}}\n
  +  The value of \\hyperrefsetup{...} in the preamble. String is a
  format-spec which accepts keywords for %k (pdfkeywords), %d
  (pdfdescription) and %c (pdfcreator). Set to nil for no \\hyperrefsetup.
 :group 'org-export-latex
  -  :type 'boolean)
  +  :type 'string)

 The first line of the docstring should contain complete sentences only.
 I would say something along the lines:

   Template for hyperref package options.

 Value is a format string, which can contain the following placeholders:

   %k for KEYWORDS line
   %d for DESCRIPTION line
   %c for CREATOR line

 An empty string disables the setup.

 Since you specify :type as 'string, it is wrong to expect a nil value in
 the variable. Note that nil is not an absolute necessity. We can allow
 to disable the template with an empty string instead.

  +   (format-spec org-latex-hyperref-template
  +(format-spec-make
  + ?k (or (plist-get info :keywords) )
  + ?d (or (plist-get info :description))
  + ?c (if (plist-get info :with-creator)
  +(plist-get info :creator)
  +  

 You are not using the :latex-hyperref property. This should be:

   (format-spec (plist-get info :latex-hyperref)
...)


 Regards,

 --
 Nicolas Goaziou



[O] [ANN] Lazy cache synchronization

2014-02-20 Thread Nicolas Goaziou
Hello,

I just pushed an update for parser cache.

Until then, synchronization was the weak spot of the cache mechanism, as
it happened in one row after each buffer change, with a linear
complexity by the number of elements in cache after point. In other
words, editing a very large buffer near its end was fast, but slow at
its beginning.

Now, synchronization happens lazily, which means the cache is only
updated when and where needed, or during idle time. Therefore the cache
mechanism scales a lot better.

Obviously, the more functions use it, the more it is profitable. Hence,
it would be nice to rewrite core functions so they use the parser (i.e,
`org-element-at-point' and `org-element-context'). For example,
functions like `org-in-clocktable-p', `org-in-commented-line',
`org-in-indented-comment-line' (which should be merged with the previous
one) or `org-in-verbatim-emphasis' are good starting points.

If you feel adventurous, synchronization can be controlled with the
following variables:

  - `org-element-cache-sync-idle-time'
  - `org-element-cache-sync-duration'
  - `org-element-cache-sync-break'

Feedback (or benchmarks) welcome.


Regards,

-- 
Nicolas Goaziou



[O] Non-interactive export

2014-02-20 Thread Simon Thum

Hi all,

I have a server over which I sync my Org files and provide drops for 
other clients, chiefly iCal and vCard. Therefore I need non-interactive 
export.


Things recently stopped working however, and although I acknowledge it 
is likely not Org's fault maybe here I can find somewone more into lisp 
to help me out a bit.


In my logs I find, since it stopped working:

 Evaluate this gnuplot code block on your system? (yes or no)


Which stops the show, waiting for input. Emacs is started with -batch 
and is given an export script. This so far avoided such questions (from 
org-babel?) successfully. I have maxima blocks since ages and do not 
remember having seen this behaviour.


Does naybody have an idea what could be going on?

The machine does not even have gnuplot.

Thanks in advance,

Simon



Re: [O] [RFC] Move ox-koma-letter into core?

2014-02-20 Thread Alan L Tyree


On 21/02/14 00:29, Rasmus wrote:

Viktor Rosenfeld listuse...@gmail.com writes:


Hi Tom,

Am 17.02.14 22:56, schrieb Thomas S. Dye:


FWIW, as a small businessman, the indemnification clause looks fairly
standard to me.  The contracts for archaeological services that we
routinely sign typically have a clause like this, usually coupled with a
request for a certificate of insurance that specifies the levels of
liability insurance that the business carries.

As I read the clause, FSF is in the position of accepting 1) a code
contribution from a developer, and 2) the developer's assurance that the
contributed code can't be claimed as property by a third party.  It
seems prudent that, in the event of a successful property claim by a
third party to a piece of code contributed by a developer, the developer
who gave the false assurance should be held responsible. Otherwise, FSF
might be brought down by copyleft opponents who knowingly contribute
code to which others have property rights in order to create a basis for
lawsuits.

Thanks for your reply. I was hoping to get some feedback on how other
Orgmode contributors see this issue (although this list is obviously
self-selective). The problem I have is that I'm not a lawyer or a
businessman and not a native English speaker. I do know enough though
not to lightly sign documents I don't fully understand.

Perhaps FSFE would be able to shed some light on the issue (EU-based).
Or Software Freedom Conservancy (US-based).  I don't have further
insights.

—Rasmus

FWIW, most book publishing contracts that I have seen have something 
similar. An example:


The Authors warrant to the Publishers that the Work will in no way
whatever violate any existing Copyright (except as notified under Clause
7(b)), and that it will contain nothing of a libellous or scandalous
character. The Authors shall indemnify the Publishers against any claims,
actions, loss or damage including costs and expenses incurred by the
Publishers as a result of any breach of the present warranty.

I imagine that quite a few members of this list have signed something 
similar.


Cheers,
Alan


--
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:typh...@iptel.org




Re: [O] org-export-latex-hyperref-options-format

2014-02-20 Thread Joe Hirn
With recommended changes.

 BEGIN PATCH *
diff --git a/ox-latex.el b/ox-latex.el
index 19f055e..f6e5a09 100644
--- a/ox-latex.el
+++ b/ox-latex.el
@@ -103,7 +103,7 @@
(:latex-class-options LATEX_CLASS_OPTIONS nil nil t)
(:latex-header LATEX_HEADER nil nil newline)
(:latex-header-extra LATEX_HEADER_EXTRA nil nil newline)
-   (:latex-hyperref-p nil texht org-latex-with-hyperref t)
+   (:latex-hyperref nil nil org-latex-hyperref-template t)
;; Redefine regular options.
(:date DATE nil \\today t)))

@@ -341,10 +341,18 @@ the toc:nil option, not to those generated with #+TOC
keyword.
   :group 'org-export-latex
   :type 'string)

-(defcustom org-latex-with-hyperref t
-  Toggle insertion of \\hypersetup{...} in the preamble.
+(defcustom org-latex-hyperref-template \\hypersetup{\n
pdfkeywords={%k},\n  pdfsubject={%d},\n  pdfcreator={%c}}\n
+  Template for hyperref package options.
+
+Value is a format string, which can contain the following placeholders:
+
+  %k for KEYWORDS line
+  %d for DESCRIPTION line
+  %c for CREATOR line
+
+An empty string disables the setup.
   :group 'org-export-latex
-  :type 'boolean)
+  :type 'string)

  Headline

@@ -1118,12 +1126,13 @@ holding export options.
  ;; Title
  (format \\title{%s}\n title)
  ;; Hyperref options.
- (when (plist-get info :latex-hyperref-p)
-   (format \\hypersetup{\n  pdfkeywords={%s},\n  pdfsubject={%s},\n
 pdfcreator={%s}}\n
-   (or (plist-get info :keywords) )
-   (or (plist-get info :description) )
-   (if (not (plist-get info :with-creator)) 
- (plist-get info :creator
+ (format-spec (plist-get info :latex-hyperref)
+  (format-spec-make
+   ?k (or (plist-get info :keywords) )
+   ?d (or (plist-get info :description))
+   ?c (if (plist-get info :with-creator)
+  (plist-get info :creator)
+)))
  ;; Document start.
  \\begin{document}\n\n
  ;; Title command.
 END PATCH *


On Thu, Feb 20, 2014 at 3:52 PM, Joe Hirn joseph.h...@gmail.com wrote:

 I really appreciate your review. Sorry for the pedestrian code submission.
 I don't get candid critical feedback on my e-lisp, so it's great to learn
 more about its idioms and conventions.

 I'll incorporate your feedback into a new patch.


 On Thu, Feb 20, 2014 at 2:51 PM, Nicolas Goaziou n.goaz...@gmail.comwrote:

 Hello,

 Joe Hirn joseph.h...@gmail.com writes:

  I was able to test this on my local machine and it seems to work as we
  discussed.
 
  If there are any other changes to the patch you'd like to see, please
 let
  me know.

 Thank you for the patch. Here are a few comments.

  -   (:latex-hyperref-p nil texht org-latex-with-hyperref t)
  +   (:latex-hyperref-p nil texht (if org-latex-hyperref-template t) t)

 I think we can drop the -p suffix since this is no longer a predicate.
 So the property can be named :latex-hyperref.

 Also we can replace texht with nil since it doesn't make much sense to
 specify a full template from the OPTIONS line.

 Eventually, the default value should be `org-latex-hyperref-template'.

 This boils down to the following line:

   (:latex-hyperref nil nil org-latex-hyperref-template t)

  -(defcustom org-latex-with-hyperref t
  -  Toggle insertion of \\hypersetup{...} in the preamble.
  +
  +(defcustom org-latex-hyperref-template \\hypersetup{\n
   pdfkeywords={%k},\n  pdfsubject={%d},\n  pdfcreator={%c}}\n
  +  The value of \\hyperrefsetup{...} in the preamble. String is a
  format-spec which accepts keywords for %k (pdfkeywords), %d
  (pdfdescription) and %c (pdfcreator). Set to nil for no
 \\hyperrefsetup.
 :group 'org-export-latex
  -  :type 'boolean)
  +  :type 'string)

 The first line of the docstring should contain complete sentences only.
 I would say something along the lines:

   Template for hyperref package options.

 Value is a format string, which can contain the following placeholders:

   %k for KEYWORDS line
   %d for DESCRIPTION line
   %c for CREATOR line

 An empty string disables the setup.

 Since you specify :type as 'string, it is wrong to expect a nil value in
 the variable. Note that nil is not an absolute necessity. We can allow
 to disable the template with an empty string instead.

  +   (format-spec org-latex-hyperref-template
  +(format-spec-make
  + ?k (or (plist-get info :keywords) )
  + ?d (or (plist-get info :description))
  + ?c (if (plist-get info :with-creator)
  +(plist-get info :creator)
  +  

 You are not using the :latex-hyperref property. This should be:

   (format-spec (plist-get info :latex-hyperref)
...)


 Regards,

 --
 Nicolas Goaziou





[O] orgstruct-mode and strange keybindings

2014-02-20 Thread Bart Bunting
Good morning,

I have just started to use orgstruct-mode and have a very strange thing
happening.

I have built from the org-mode git repo as of just now.

Org-struct mode works but appears to have taken over the m and c keys.
Stranger than that it looks like meta and control is a prefix.  I mean
as in typing meta space space. gives this error:

OrgStruct mode enabled
 m e t a SPACE  is undefined

I can't find anything in my config that suggests I'm binding any keys in
a strange way.  In fact I can't find any reference to orgstruct in my
.emacs customize.

Has anyone seen this and or can suggest how I should go about tracking
it down?



Kind regards

Bart
-- 


Kind regards

Bart



Re: [O] Non-interactive export

2014-02-20 Thread John Hendy
On Thu, Feb 20, 2014 at 4:12 PM, Simon Thum simon.t...@gmx.de wrote:
 Hi all,

 I have a server over which I sync my Org files and provide drops for other
 clients, chiefly iCal and vCard. Therefore I need non-interactive export.

 Things recently stopped working however, and although I acknowledge it is
 likely not Org's fault maybe here I can find somewone more into lisp to help
 me out a bit.

 In my logs I find, since it stopped working:

 Evaluate this gnuplot code block on your system? (yes or no)


 Which stops the show, waiting for input. Emacs is started with -batch and is
 given an export script. This so far avoided such questions (from org-babel?)
 successfully. I have maxima blocks since ages and do not remember having
 seen this behaviour.

 Does naybody have an idea what could be going on?

 The machine does not even have gnuplot.

I don't think the machine matters so much as the source of Org/babel
thinking gnuplot *code* exists in one of your files.

Can you try something like this from the directory containing the
exported files?

grep -r #+begin_src gnuplot *

I would have suggested just tweaking the variable
=org-confirm-babel-evaluate=, but I think it's more important to track
the source of this down, as turning the inquiries off implies that we
all know exactly what's going to be evaluated, and this sounds like an
instance of something not only unknown, but a change on what you
believe to be a rather unchanged system, which is definitely
concerning.

Good luck,
John


 Thanks in advance,

 Simon




Re: [O] [export] Tables in ox-reveal export

2014-02-20 Thread Yujie Wen
Hi, Alexander,

  You can specify the appearance of tables in an extra .css file and tell
ox-reveal to use that .css file by specifying #+REVEAL_EXTRA_CSS. For
example, say I have a table.org and a table.css in the same directory. The
contents of the two files are:

table.org
-
#+REVEAL_EXTRA_CSS: ./table.css
* Head1
  The paragraph.

| Col0 | Col1   | Col2 |
|--++--|
| Cell | Something long | Cell |
| Cell | xx | Cell |



table.css

.reveal table {
margin-left: auto;
margin-right: auto;
}


  Then the table is rendered automatically by the browser in center.

Regards,
Yujie


2014-02-19 23:43 GMT+08:00 Alexander Vorobiev alexander.vorob...@gmail.com
:

 Hi,
 Is it possible to control appearance of tables in reveal.js
 presentations created with ox-reveal? The resulting html tables appear
 on the left and I want to be able to have them centered.

 There is a comment at

 http://stackoverflow.com/questions/20583341/tables-and-div-elements-are-not-centred-in-reveal-js
 that defining tables with table class=reveal would produce
 centered tables. Is it possible to have ox-reveal use that additional
 attribute and/or other table-formatting directives?

 Thanks,
 Alex




[O] Weaving a budget with Org ledger

2014-02-20 Thread Erik Hetzner
Hi,

Users of ledger and Org may be interested in this tutorial on how I
manage an envelope style budget with those two excellent tools.

  http://orgmode.org/worg/org-tutorials/weaving-a-budget.html

Thanks!

best, Erik

-- 
Sent from my free software system http://fsf.org/.



[O] Conditional in table formula with times

2014-02-20 Thread Loris Bennett
Hi,

I'm trying to keep track of total time spend at work, but I am having
trouble with a conditional in table formula:

| *Day*| *Came* | *Went* | *Worked* | *Required* |   *Diff* |
|--+++--++--|
| [2014-01-06 Mon] |   8:00 |  17:00 | 09:00:00 |   00:00:00 | 09:00:00 |
| [2014-01-07 Tue] ||| 00:00:00 |   00:00:00 | 00:00:00 |
| [2014-01-08 Wed] |   8:10 |  16:30 | 08:20:00 |   00:00:00 | 08:20:00 |
| [2014-01-09 Thu] |   7:55 |  17:05 | 09:10:00 |   00:00:00 | 09:10:00 |
| [2014-01-10 Fri] |   8:00 |  17:05 | 09:05:00 |   00:00:00 | 09:05:00 |
#+TBLFM: $4=$3-$2;T::$5=if($4  0,8:18:00,00:00:00);T::$6=$4-$5;T

Debugging the formula gives me for @2$5:

,-
| Substitution history of formula
| Orig:   if($4  0,8:18:00,00:00:00);T
| $xyz-  if($4  0,8:18:00,00:00:00)
| @r$c-  if($4  0,8:18:00,00:00:00)
| $1-if((32400)  0,8:18:00,00:00:00)
| Result: 00:00:00
| Format: NONE
| Final:  00:00:00
`-

and for @3$5:

,--
| Substitution history of formula
| Orig:   if($4  0,8:18:00,00:00:00);T
| $xyz-  if($4  0,8:18:00,00:00:00)
| @r$c-  if($4  0,8:18:00,00:00:00)
| $1-if((0)  0,8:18:00,00:00:00)
| Result: 00:00:00
| Format: NONE
| Final:  00:00:00
`--

Can anyone enlighten me as to why I get 00:00:00 in the first case?

Cheers,

Loris

-- 
This signature is currently under construction.




Re: [O] Weaving a budget with Org ledger

2014-02-20 Thread Alan Schmitt
Erik Hetzner e...@e6h.org writes:

 Users of ledger and Org may be interested in this tutorial on how I
 manage an envelope style budget with those two excellent tools.

   http://orgmode.org/worg/org-tutorials/weaving-a-budget.html

Thank you very much for this! My current setup (using Moneywell) is
starting to crack at the seams, and this will be most helpful to help me
migrate.

Alan