date:20130703

Hi Gustav,

Gustav Wikström  writes:

> I haven't confirmed latex blocks but I trust your words.
>
> I have been using C-c ' for quote blocks in the past and there is a
> change as it's not working any more. I'm not against it though, just
> curious. From what I understand now only source-blocks (including
> example-blocks) and latex-blocks are (can be) edited by C-c '.  other
> blocks (verse, center, quote) are not.

... and example blocks.

This can be revisited, of course, but I think the current state
makes sense.

> Now I know, thanks!
>
> As a side-note: I like the ability to abort an edit now, small but
> nice addition!)

Org is just made of this: small and nice tricks :)

-- 
 Bastien

Re: [O] "Special Properties" when matching for Properties in a search

Hi Gustav,

Gustav Wikström  writes:

> As I brought this up, I might just as well provide a way of clarifying
> this for the manual.

Applied, thanks.

-- 
 Bastien

Re: [O] Sort check lists by checked status

Hi Carsten,

Carsten Dominik  writes:

> On 3.7.2013, at 15:10, Bastien  wrote:
>
>> I just pushed a change in master: you can now sort check lists
>> by the "checked" status.  `C-c ^ c' on a check list will put the
>> checked item at the end.  I've been using this quite heavily, I
>> hope other will find this useful.
>
> This is useful, thanks!
>  Maybe "x" would be a more memorable character to use?

Yes, better, done.  Thanks!

-- 
 Bastien

Re: [O] [babel] feature request: debug messages

2013-07-03 Thread Eric Schulte

Hi Andreas,

This should be easy to turn on or off using the newly introduced
:prologue and :epilogue header arguments.  See the manual and the
following example.

#+Title: debug messages
#+Property: session *R*
#+Property: prologue (format "print(\"entering %s\")" (get-current-name))

An elisp block to simplify the =:prologue= definition.
#+begin_src emacs-lisp
  (defun get-current-name ()
(save-excursion
  (goto-char org-babel-current-src-block-location)
  (while (and (forward-line -1)
  (looking-at org-babel-multi-line-header-regexp)))
  (when (looking-at org-babel-src-name-w-name-regexp)
(org-no-properties (match-string 3)
#+end_src

Two blocks with simple assignments.

#+name: block-1
#+begin_src R
  x <- 2 + 2
#+end_src

#+name: block-2
#+begin_src R
  y <- x + x
#+end_src

Execute the whole buffer =C-c C-v b= to see the prologue in action.

Andreas Leha  writes:

> Hi all,
>
> I would love to see messages like 'entering block foo...' and
> '...leaving block foo' printed to my R console.  This would be very
> handy when I evaluate a subtree (C-c C-v s) with a lot of #+call lines
> and some lengthy ones.
>
> I know that
> (1) I could implement that myself at in the source blocks.  But I would
> love if orgmode did that for me
> (2) Such messages are already printed to the emacs *Messages* buffer.
> But that buffer might not be visible and I can not switch to it,
> without interrupting the evaluation.  Anyway it would be much nicer
> to see that output together with the other output, that my code
> generates.
>
>
> In essence it would be very helpful, if there was a variable
> org-babel-print-debug-messages (or org-babel-debug-level...) which if
> non-nil would cause that messages to be printed.  Or is there somewhere
> already?
>
> Regards,
> Andreas
>
>
>
>

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

Re: [O] Org file to generate both beamer and standard LaTeX file

2013-07-03 Thread Suvayu Ali

Hi,

On Wed, Jul 03, 2013 at 11:32:15PM +0200, Julien Cubizolles wrote:
> I've been an newbie org user for a while now: in particular, I've never
> played with export much and all my LaTeX work as been done with AucTeX
> in a .tex file. I'm considering switching to an Org-based setup if I
> could get the following, mainly for courses I'm preparing for which I
> would need beamer / handouts / normal LaTeX / maybe odt export
> 
> * sectioning (\section et al commands in LaTeX) done with first and
>   second/third level heading, common to all exporters
> 
> * some common LaTeX code for all exports (definitions/theorems)
> 
> * manual specification of individual frames for the Beamer export. I
>   guess I would need LaTeX blocks for that, would AucTeX be available in
>   the edit buffer ?
> 
> * manual LaTeX code for normal LaTeX
> 
> * some python/pgfplots/tikz source blocks generating images, used in the
>   different export modes.
> 
> Can it be done ? Even better, did one of you already implemented
> something similar ?

All of what you list above is supported.  You just need to learn the
syntax.  To get started please look at the ox-beamer tutorial on Worg.
It is a little outdated by now, but it should provide a good starting
point for you.  And of course all the features are very nicely
documented in the manual, take a look there.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

[O] [PATCH] ox-html: Allow "Figure %d:", etc. to be styled

2013-07-03 Thread Kodi Arfer

 >From a873d204b2c4f3facf2d8658f69764acbd063246 Mon Sep 17 00:00:00 2001
From: Kodi Arfer 
Date: Wed, 3 Jul 2013 17:51:56 -0400
Subject: [PATCH] ox-html: Allow "Figure %d:", etc. to be styled

* lisp/ox-html.el (org-html-paragraph): Wrap "Figure %d:" in
  .
  (org-html-list-of-tables, org-html-table): Wrap "Table %d:" in
   .
  (org-html-list-of-listings): Wrap "Listing %d:" in
  .
* doc/org.text (CSS support): Mention .figure-number,
  .listing-number, and .table-number.

I didn't change org-html-style-default, so these labels won't
appear special by default.

TINYCHANGE
---
 doc/org.texi|  3 +++
 lisp/ox-html.el | 14 +-
 2 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index 4eb9a45..ce4f715 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11337,6 +11337,9 @@ p.creator   @r{creator info, about org mode version}
 div.outline-N   @r{div for outline level N (headline plus text))}
 div.outline-text-N  @r{extra div for text at outline level N}
 .section-number-N   @r{section number in headlines, different for each level}
+.figure-number  @r{label like "Figure 1:"}
+.table-number   @r{label like "Table 1:"}
+.listing-number @r{label like "Listing 1:"}
 div.figure  @r{how to format an inlined image}
 pre.src @r{formatted source code}
 pre.example @r{normal example}
diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 9ce73c4..b0417e8 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -2009,7 +2009,8 @@ of listings as a string, or nil if it is empty."
 		  org-html-toplevel-hlevel)
 	  "\n\n"
 	  (let ((count 0)
-		(initial-fmt (org-html--translate "Listing %d:" info)))
+		(initial-fmt (format "%s"
+	 (org-html--translate "Listing %d:" info
 		(mapconcat
 		 (lambda (entry)
 		   (let ((label (org-element-property :name entry))
@@ -2043,7 +2044,8 @@ of tables as a string, or nil if it is empty."
 		  org-html-toplevel-hlevel)
 	  "\n\n"
 	  (let ((count 0)
-		(initial-fmt (org-html--translate "Table %d:" info)))
+		(initial-fmt (format "%s"
+	 (org-html--translate "Table %d:" info
 		(mapconcat
 		 (lambda (entry)
 		   (let ((label (org-element-property :name entry))
@@ -2790,12 +2792,13 @@ the plist used as a communication channel."
 		'org-html--has-caption-p))
 	   (if (not (org-string-nw-p raw)) raw
 		 (concat
+  ""
 		  (format (org-html--translate "Figure %d:" info)
 			  (org-export-get-ordinal
 			   (org-element-map paragraph 'link
 			 'identity info t)
 			   info nil 'org-html-standalone-image-p))
-		  " " raw
+		  " " raw
 	(label (org-element-property :name paragraph)))
 	(org-html--wrap-image contents info caption label)))
  ;; Regular paragraph.
@@ -3204,8 +3207,9 @@ contextual information."
 			 "%s"
 			   "%s")
 			 (concat
-			  (format (org-html--translate "Table %d:" info) number)
-			  " " (org-export-data caption info
+			  ""
+  (format (org-html--translate "Table %d:" info) number)
+			  " " (org-export-data caption info
 	   (funcall table-column-specs table info)
 	   contents)
 
-- 
1.8.1.2

Re: [O] advice needed: how do you guys sync org files between devices?

2013-07-03 Thread Julien Cubizolles

Alan Schmitt  writes:

> devn...@karl-voit.at writes:
>
>> Unison does not offer any merge functionality. However, you can
>> easily use third party tools to handle merge conflicts (Emacs, vim,
>> ...).
>
> (Disclaimer, I participate in Unison's development). Just to clarify
> what I think Karl is saying: one can plug in external tools to handle
> merge into unison, these tools can be specialized depending on the file
> name (for instance the file extension) or the file path. Getting the
> correct configuration line may be tricky, but I, or people on the
> unison-users mailing list, are ready to help.


For me, this line in unison configuration file

merge = Name {,.}* -> emacs --eval '(ediff-merge-files "CURRENT1" "CURRENT2" 
nil "NEW")'

opens a new emacs frame with ediff for merging. You should change the
"Name {,.}$" part though (I should too...) to only use this on the files
you want to.

[O] Org file to generate both beamer and standard LaTeX file

2013-07-03 Thread Julien Cubizolles

I've been an newbie org user for a while now: in particular, I've never
played with export much and all my LaTeX work as been done with AucTeX
in a .tex file. I'm considering switching to an Org-based setup if I
could get the following, mainly for courses I'm preparing for which I
would need beamer / handouts / normal LaTeX / maybe odt export

* sectioning (\section et al commands in LaTeX) done with first and
  second/third level heading, common to all exporters

* some common LaTeX code for all exports (definitions/theorems)

* manual specification of individual frames for the Beamer export. I
  guess I would need LaTeX blocks for that, would AucTeX be available in
  the edit buffer ?

* manual LaTeX code for normal LaTeX

* some python/pgfplots/tikz source blocks generating images, used in the
  different export modes.

Can it be done ? Even better, did one of you already implemented
something similar ?

Julien.

Re: [O] Process diagrams with dot and some glue using Org-mode

Karl Voit  writes:

> * Karl Voit  wrote:
>>
>> I would be happy to document this method and provide it on Worg. In
>> my opinion, this would be very handy for many Org-mode users.
>
> I summarized the method on Worg[1].
>
> Can someone please proof read the page? I am not a native speaker
> and it's always good to let someone else check my weird flow of
> thoughts :-)
>

It's all good I think - thanks for putting it together!

> And there is a small issue I have got: I was not able to include the
> resulting image files. I looked at [2] and did it like with [3].
> However, my [4] results in a 404 Not Found message. Do I have to
> register any new folder somewhere?
>

Well, I pulled worg and there is an images/org-dot directory and it has
two png files in it. AFAICT, it should work: nginx obviously
disagrees. But from this distance, it seems like a small problem: Jason
or Bastien (or somebody with access to the server logs) should be able to
fix it in a jiffy.

> Thanks!
>
>   1. http://orgmode.org/worg/org-tutorials/org-dot-diagrams.html
>   2. http://orgmode.org/worg/org-tutorials/org-plot.html
>   3. http://orgmode.org/worg/images/org-plot/example-1.png
>   4. http://orgmode.org/worg/images/org-dot/example-diagram.png

-- 
Nick

Re: [O] advice needed: how do you guys sync org files between devices?

"G. Martin Butz"  writes:

> I wrote a blog entry about the issue [1], but it's in German. If you
> interested I can give further information in English.
>

The Chromium browser did an OK job of translating it: I think the
translation is rough but readable.

>
> [1]
> 
>

-- 
Nick

[O] [babel] feature request: debug messages

2013-07-03 Thread Andreas Leha

Hi all,

I would love to see messages like 'entering block foo...' and
'...leaving block foo' printed to my R console.  This would be very
handy when I evaluate a subtree (C-c C-v s) with a lot of #+call lines
and some lengthy ones.

I know that
(1) I could implement that myself at in the source blocks.  But I would
love if orgmode did that for me
(2) Such messages are already printed to the emacs *Messages* buffer.
But that buffer might not be visible and I can not switch to it,
without interrupting the evaluation.  Anyway it would be much nicer
to see that output together with the other output, that my code
generates.


In essence it would be very helpful, if there was a variable
org-babel-print-debug-messages (or org-babel-debug-level...) which if
non-nil would cause that messages to be printed.  Or is there somewhere
already?

Regards,
Andreas

Re: [O] fill paragraph: math and latex environments

2013-07-03 Thread Nicolas Goaziou

Hello,

Paul Stansell  writes:

> I'm sorry, but I don't fully understand your explanation as I don't
> know what you mean by an "element" in this context?

See: http://orgmode.org/worg/dev/org-syntax.html

> Also, am I missing something about the latex?  Do you want to be able
> to use display style maths inside a sentence (ie. avoid placing the
> maths on a new line but have it formatted in display style)?  That
> would seem strange as that's not what it's for.  I don't, therefore,
> see why anyone would want to write
>
>   Some text \[1+1\] and some other text

I do sometimes. I like compact text in my Org file, even though I know
the output will be different (and intend it to) when exported.

Let me try again with another example:

  Some text...

  \[1+1\]

  Some other text...

will not be possible anymore either. I like to use \[...\] for one
liners and \begin{equation*} ... \end{equation*} for more complicated
formulas. 

> I agree with you there.  It's not a big deal type, but I do think
>
> \[
> 1+1
> \[
>
> looks a lot nicer and cleaner in the org file than
>
> \begin{displaymath}
> 1+1
> \end{displaymath}

Of course but

  \[1+1\]

is a lot nicer than

  \[
  1+1
  \]

and

  \begin{equation*}
   u(x) =
\begin{cases}
 \exp{x} & \text{if } x \geq 0 \\
 1   & \text{if } x < 0
\end{cases}
  \end{equation*}

is (arguably) nicer than

  \[
   u(x) =
\begin{cases}
 \exp{x} & \text{if } x \geq 0 \\
 1   & \text{if } x < 0
\end{cases}
  \]

Anyway, it's a matter of taste. And currently, we can have both. We
won't anymore if we want to treat \[...\] as an element.

Regards,

-- 
Nicolas Goaziou

Re: [O] org-create-formula--latex-header does not respect latex_header in included file

2013-07-03 Thread Nicolas Goaziou

Hello,

Bing Sun  writes:

> I have a separate org file for a rather complicated latex preamble and
> then include it when needed. It works well for latex exporting but it
> appears that org-create-formula--latex-header just ignores the
> latex_header properties in the included org file when previewing latex
> fragments.
>
> Is this intended or am I missing anything?

Yes, this is intended. Including files, or expanding Babel blocks, which
may create additional #+latex_header lines, would be too costly for
a simple preview.

OTOH, have you tried to use #+setupfile: instead of #+include:?

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org-edit-special won't let me edit a latex snippet

2013-07-03 Thread Gustav Wikström

I haven't confirmed latex blocks but I trust your words.

I have been using C-c ' for quote blocks in the past and there is a
change as it's not working any more. I'm not against it though, just
curious. From what I understand now only source-blocks (including
example-blocks) and latex-blocks are (can be) edited by C-c '.  other
blocks (verse, center, quote) are not.

Now I know, thanks!

As a side-note: I like the ability to abort an edit now, small but
nice addition!)

Regards
Gustav

On Mon, Jul 1, 2013 at 12:29 AM, Bastien  wrote:
> Hi Gustav,
>
> Gustav Wikström  writes:
>
>> It seems to me that in 8.0.3 this is still an issue. Both latex and
>> quote blocks gives the response:
>>
>> "user-error: No special environment to edit here"
>
> I can use C-c ' in #+begin_latex environments correctly with latest
> Org (release_8.0.3-309), but I don't think C-c ' was ever supported
> for quote blocs.  Does the manual suggest otherwise?
>
> Best,
>
> --
>  Bastien

Re: [O] Process diagrams with dot and some glue using Org-mode

2013-07-03 Thread Karl Voit

* Karl Voit  wrote:
>
> I would be happy to document this method and provide it on Worg. In
> my opinion, this would be very handy for many Org-mode users.

I summarized the method on Worg[1].

Can someone please proof read the page? I am not a native speaker
and it's always good to let someone else check my weird flow of
thoughts :-)

And there is a small issue I have got: I was not able to include the
resulting image files. I looked at [2] and did it like with [3].
However, my [4] results in a 404 Not Found message. Do I have to
register any new folder somewhere?

Thanks!

  1. http://orgmode.org/worg/org-tutorials/org-dot-diagrams.html
  2. http://orgmode.org/worg/org-tutorials/org-plot.html
  3. http://orgmode.org/worg/images/org-plot/example-1.png
  4. http://orgmode.org/worg/images/org-dot/example-diagram.png
-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: [O] "Special Properties" when matching for Properties in a search

2013-07-03 Thread Gustav Wikström

Ok thanks!

As I brought this up, I might just as well provide a way of clarifying
this for the manual.

On Mon, Jul 1, 2013 at 12:04 AM, Bastien  wrote:
> Hi Gustav,
>
> Gustav Wikström  writes:
>
>> When matching for tags and properties using C-c / m there is the
>> option to match for Special Properties. Is there a complete list of
>> these special properties somewhere?
>>
>> I was thinking that "7.2 Special Properties" in the manual would be
>> that list, but then noticed a property possible to use for searches,
>> but not available in that list (the LEVEL-property). Is that property
>> just missing from there?
>
> Mhhh... no, AFAIK the "LEVEL" property is a special-special property:
> you can use it in search constructs, but not in column view (which is
> the primary context for the 7.2 manual section.)
>
> But I'd say that's the only property missing here.  I'm short of good
> ideas on how to improve the manual here.
>
> --
>  Bastien
Modified   doc/org.texi
diff --git a/doc/org.texi b/doc/org.texi
index 5f50ef6..64553e1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -8045,15 +8045,18 @@ You may also test for properties (@pxref{Properties and 
Columns}) at the same
 time as matching tags.  The properties may be real properties, or special
 properties that represent other metadata (@pxref{Special properties}).  For
 example, the ``property'' @code{TODO} represents the TODO keyword of the
-entry.  Or, the ``property'' @code{LEVEL} represents the level of an entry.
-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
+entry and the ``propety'' @code{PRIORITY} represents the PRIORITY keyword of
+the entry.  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}.}.

+Except the @pxref{Special properties}, one other ``property'' can also be
+used. @code{LEVEL} represents the level of an entry. 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.
+
 Here are more examples:

 @table @samp

Re: [O] Sort check lists by checked status

2013-07-03 Thread Carsten Dominik


On 3.7.2013, at 15:10, Bastien  wrote:

> I just pushed a change in master: you can now sort check lists
> by the "checked" status.  `C-c ^ c' on a check list will put the
> checked item at the end.  I've been using this quite heavily, I
> hope other will find this useful.

This is useful, thanks!
 Maybe "x" would be a more memorable character to use?

- Carsten

Re: [O] refile cache and auto-save files

2013-07-03 Thread Samuel Wales

Somehow this code needs integrating.

  (file-newer-than-file-p (or buffer-auto-save-file-name
  (make-auto-save-file-name))
  buffer-file-name)

Or Emacs needs a solution that makes it so that you get notified when
you first edit?

On 7/2/13, Samuel Wales  wrote:
> It is probably common to refresh the refile cache at times when one is
> not watching.  This has the effect of loading files that are refile
> targets.  If there is auto-save data in one of those files, the
> message will likely often go unnoticed.
>
> I don't know the best solution.
>
> Samuel
>
> --
> The Kafka Pandemic: http://thekafkapandemic.blogspot.com
>
> The disease DOES progress.  MANY people have died from it.  ANYBODY can get
> it.
>
> Denmark: free Karina Hansen NOW.
>


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

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

Denmark: free Karina Hansen NOW.

Re: [O] org-clock-is-active

Hi Łukasz,

l.stelm...@samsung.com (Łukasz Stelmach) writes:

> (defun org-clock-is-active ()
>   "Return non-nil if clock is currently running.
> The return value is actually the clock marker."
>   (marker-buffer org-clock-marker))
>
> Either the docstring is lying or the code does not do what it is said
> to. (Or it is too late for me?)

I don't understand, what is the problem exactly?

-- 
 Bastien

Re: [O] Copying/pasting org html export into IBM Community Wiki

2013-07-03 Thread John Hendy

I'll look at the wiki export format. Unfortunately, Communities is not
wiki markup style, so html would be best. Org seems to rely on css and
spans/divs, which don't appear to cooperate with Communities raw html
edit mode. I'd need something with all the formatting specified
in-line, I think.


John

On Fri, Jun 21, 2013 at 11:14 PM, Srinivas  wrote:
>
> John Hendy  gmail.com> writes:
>
>>
>> Greetings,
>>
>> My company uses a few different social media platforms, including IBM
>> Communities, Wiki Enterprise, and Sharepoint. IBM Communities are what
>> I'm using to manage a project, and would like to use the Wiki feature
>> to keep a dashboard on tasks and a timeline.
>
>>
>>
>
> John,
>
> I don't know if there is a generic exporter in Org 8.0. In versions prior to
> Org 8.0, there was a generic exporter which could be tailored for your
> flavor of wiki output. Will the wiki export format work for you? The down
> side is the styles will be inherited from IBM Communities and not your own
> style.
>
> - Srinivas
>
>

Re: [O] [BUG] Two problems with defcustom of org-structure-template-alist

Hi Nick,

Nick Dokos  writes:

> That's the first problem, but even after doing this, I still get a
> (mismatch).
>
> I think the (second) problem now is that the Muse Template is not
> optional as far as defcustom is concerned, but there are entries in the
> list above with only two elements. If I add a third element (an empty
> string) to those entries missing it, I can customize to my heart's
> content.

Thanks, I pushed this fix:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=a42c09

> The question is: is the Muse Template optional? If so, how does one
> tell defcustom that? I did a cursory reading of the customization
> chapter in the elisp manual but my brain refuses to cooperate.

Well, mine refuses too :)

-- 
 Bastien

Re: [O] advice needed: how do you guys sync org files between devices?

2013-07-03 Thread G. Martin Butz


Hi Itai,

you have been given a lot of detailed advice, so I do not know, if my 
contribution will add anything.


I have made good experiences with a combination of unison and git. I 
currently synchonise my netbook and my laptop; it is a rather simple and 
homebrew setup but it works for my pupose.


I wrote a blog entry about the issue [1], but it's in German. If you 
interested I can give further information in English.


For my android phone and org I do not use dropbox, because I do not want 
my org-files on a public server. I do not have the newest android 
version so I can not easily encrypt the content. I am a bit ancious to 
put all my org content on my phone (in case of loss), so I export one 
org-file with important dates via USB to have the dates in the phone's 
calendar.


Thanks
Martin

[1] 



Am 01.07.2013 14:06, schrieb Xebar Saram:

Hi all

I have been using dropbox since i started using orgmode a few weeks ago
(yeah im a neewb :)), which kinda works but i find it very annoying as it
keeps creating conflicted copies, isnt reliable on my Linux main machine
etc etc..

I was wondering what you guys do for syncing org files between PC's, Os's,
devices (android etc)..

Best

Itai




--
~~
| G. Martin Butz | m.b...@hfk-bremen.de | www.mkblog.org |
~~

Re: [O] [BUG] :colnames not applied to #+call input

2013-07-03 Thread Eric Schulte

Currently colnames are not used for emacs-lisp code blocks (for
historical reasons).  Unfortunately, call lines are executed by
expanding first to a trivial emacs-lisp code block, which is then run to
collect and possibly re-package the results of the called function.
Thus colnames do not work well in call lines.

I think the best solution here is to add colnames support to Emacs Lisp
code blocks.  I can put this on my Org-mode queue, but can't promise to
get to it any time soon.

Cheers,

Rick Frankel  writes:

> On 2013-06-30 19:21, Eric Schulte wrote:
>> Rick Frankel  writes:
>> 
>> it seems that the :colnames header is not being respected on parsing 
>> the
>> input
>> to a `#+call:' line containing arguments, but is being applied to the
>> output!
>> 
>> For example:
>> 
>> #+BEGIN_SRC org
>> * Identity
>> #+name: table
>> | a | b | c |
>> |---+---+---|
>> | 1 | 2 | 3 |
>> 
>> #+name: identity
>> #+BEGIN_SRC emacs-lisp :var table=table :colnames yes
>> (mapcar 'identity table)
>> #+END_SRC
>> 
>> Emacs Lisp handles the :colnames header argument differently than other
>> languages, hence the "Note that the behavior of the ':colnames' header
>> argument may differ across languages." phrase in the manual.  If you
>> remove ":colnames yes" from the emacs-lisp code block in your example
>> everything should work fine.
>
> I understand the differing handling of ':colnames' in different
> langauages, but you "solution" does not address the issue of not being
> able to call the block. It would mean handling the header and
> hline in the called block in all cases. The problem i am addressing is
> that the :colnames argument to the original source block is being
> applied on the reassembly of the output regardless of the value of the
> :colnames argument to the call line. This is a regresssion since 7.9
> (see the 7.9 example at the end of this message). Let's try a
> different example to make the issue clearer.
>
>
> Given the same table, and the method:
>
> #+name: map
> #+BEGIN_SRC emacs-lisp :var table=table :colnames yes
> (mapcar (lambda (row) (mapcar '1+ row)) table)
> #+END_SRC
>
> The results are:
>
> #+RESULTS: map
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
>
>
> If I call the function w/o a table argument i get the same results.
> However, if i try to pass the table argument, i get the following
> errors:
>
> /mapcar: Wrong type argument: number-or-marker-p, "a"/ on:
>
> #+call: map(table=table)
> #+call: map(table=table) :colnames yes
> #+call: map[:colnames yes](table=table) :colnames yes
>
> /Wrong type argument: sequencep, 1/ on:
>
> #+call: map(table=table[2:-1])
>
> (since the (now one row) table is turned into a list.
>
> So there is no way to call this function with a single-row table as an
> argument.
>
> If we have the following table instead:
>
> #+name: table2
> | a | b | c |
> |---+---+---|
> | 1 | 2 | 3 |
> | 4 | 5 | 6 |
>
> we get:
>
> #+name: map2
> #+BEGIN_SRC emacs-lisp :var table=table2 :colnames yes
> (mapcar (lambda (row) (mapcar '1+ row)) table)
> #+END_SRC
>
> #+RESULTS: map2
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
> #+call: map2(x="")
>
> #+RESULTS: map2(x="")
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
> #+call: map(table=table2[2:-1])
>
> #+RESULTS: map(table=table2[2:-1])
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
>
> which looks right, but we shouldn't have any header on the above
> results as we have (supposedly) stripped it from the input with the
> slice).
>
> Here' are the results from 7.9.3f. Note that calling the source block
> with a single row table is still impossible in 7.9, as the slice is
> still turned into a list, and the :colnames argument is also not being
> applied to the input (but is only being applied to the output if
> specified in the call line):
>
> #+name: map2
> #+BEGIN_SRC emacs-lisp :var table=table2 :colnames yes
> (mapcar (lambda (row) (mapcar '1+ row)) table)
> #+END_SRC
>
> #+RESULTS: map2
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
> #+call: map2(x="")
>
> #+RESULTS: map2(x="")
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
> #+call: map2(x="") :colnames yes
>
> #+RESULTS: map2(x=""):colnames yes
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
> #+call: map(table=table2[2:-1])
>
> #+RESULTS: map(table=table2[2:-1])
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
> #+call: map(table=table2[2:-1]) :colnames yes
>
> #+RESULTS: map(table=table2[2:-1]):colnames yes
> | a | b | c |
> |---+---+---|
> | 2 | 3 | 4 |
> | 5 | 6 | 7 |
>
>
>
>

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

Re: [O] HTML export and info: links

2013/7/3 Bastien :
> Sebastian Wiesner  writes:
>
>> Is there a single assignment for just one specific patch?  I am not
>> going to assign the FSF copyright for any and every future change to
>> Emacs I might create.
>
> The FSF policy is that you cannot assign your copyright for just one
> patch, you assign it for future changes too.

This is unfortunate.  I am sorry, but under this circumstances I won't
contribute to Org mode.  I may still implement support for Info links,
but it's won't become part of Org mode, as long as I am required to
sign an assignment of such broad and unlimited scope.  I am not going
to get myself into legal trouble for such a comparatively small thing.

Re: [O] HTML export and info: links

Sebastian Wiesner  writes:

> Is there a single assignment for just one specific patch?  I am not
> going to assign the FSF copyright for any and every future change to
> Emacs I might create.

The FSF policy is that you cannot assign your copyright for just one
patch, you assign it for future changes too.

-- 
 Bastien

Re: [O] HTML export and info: links

2013/7/3 Bastien :
> Sebastian Wiesner  writes:
>
>> 2013/7/3 Bastien :
>>> Well, that's too much work for me now.  Hopefully someone who needs
>>> this can help too.
>>
>> I'll probably give it a shot, depending on how much free time I can
>> find in the next weeks.
>
> Great, thanks.

Don't thank me yet, I can't promise anything :)

>> You said, you might incorporate such an extension into Org, but isn't
>> Org covered by Copyright Assignments?
>
> Yes, see this:
> http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt

Is there a single assignment for just one specific patch?  I am not
going to assign the FSF copyright for any and every future change to
Emacs I might create.

Re: [O] Break a line in org-mode

Søren Mikkelsen  iha.dk> writes:

> 
> On 2013-07-03 10:21, Nick Dokos wrote:
> > Søren Mikkelsen  iha.dk> writes:
> > 
> >> I usually have some #+LaTeX_HEADER: entries in my org-mode files where
> >> some of them are macros. These lines can be rather long so I have to
> >> type in #+LaTeX_HEADER: multiple times for breaking the line to a 
decent
> >> level.
> >>
> >> Is there a way of breaking a line when it is export options (or a
> >> regular comment in org-mode)?
> >>
> > Wouldn't it be better to put the macros in a separate file (say
> > mymacros.sty) and use
> > 
> > #+LATEX_HEADER: \usepackage{mymacros}
> > 
> > ? Less clutter in the org file and if the macros are more generally 
useful,
> > you can make it available, say by moving it to your personal texmf
> > directory (mine is at ~/.texmf-var/tex/latex but ymmv) and running 
texhash.
> > 
> 
> Well, I would like it to be in one file. If I, for instance, want to
> have long author list, it is not possible to do without having all the
> names on one line.
> 
> I through maybe that there was a newline symbol, like in python or matlab.
> 
> --
> Søren
> 
> 

In that case, you might want to use a template mechanism to enter the 
#+LATEX_HEADER with a minimum of pain. Org comes with an "easy template" 
system of its own:

  (info "(org) Easy templates")

but I had some trouble with the customization as detailed in another 
posting. Note by the way that you can use a string as a key: you are not 
limited to a single character. There are other abbrev/template systems also
if you find you don't like the org one. 
--
Nick

[O] org-create-formula--latex-header does not respect latex_header in included file

2013-07-03 Thread Bing Sun

hello list,

I have a separate org file for a rather complicated latex preamble and
then include it when needed. It works well for latex exporting but it
appears that org-create-formula--latex-header just ignores the
latex_header properties in the included org file when previewing latex
fragments.

Is this intended or am I missing anything?

BTW, I find it painful to maintain the latex preamble as the
latex_header properties, say
#+LATEX_HEADER: \newcommand{\mathd}{\mathrm{d}}
#+LATEX_HEADER: \newcommand{\mathbf}[1]{\ensuremath{\boldsymbol{#1}}}
#+LATEX_HEADER: \newcommand{\op}[1]{\ensuremath{\operatorname{#1}}}

I'd like something like this,
#+BEGIN_SRC latex :preamble
 \newcommand{\mathd}{\mathrm{d}}
 \newcommand{\mathbf}[1]{\ensuremath{\boldsymbol{#1}}}
 \newcommand{\op}[1]{\ensuremath{\operatorname{#1}}}
#+END_SRC

Does that make any sense?

Regards.

Re: [O] HTML export and info: links

Sebastian Wiesner  writes:

> 2013/7/3 Bastien :
>> Well, that's too much work for me now.  Hopefully someone who needs
>> this can help too.
>
> I'll probably give it a shot, depending on how much free time I can
> find in the next weeks.

Great, thanks.

> You said, you might incorporate such an extension into Org, but isn't
> Org covered by Copyright Assignments?

Yes, see this:
http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt

-- 
 Bastien

Re: [O] HTML export and info: links

2013/7/3 Bastien :
> Well, that's too much work for me now.  Hopefully someone who needs
> this can help too.

I'll probably give it a shot, depending on how much free time I can
find in the next weeks.

You said, you might incorporate such an extension into Org, but isn't
Org covered by Copyright Assignments?

Re: [O] HTML export and info: links

Sebastian Wiesner  writes:

> It's not actually located there at all.  

It is for me (ArchLinux).

> My Texinfo is installed via
> Homebrew into "~/.homebrew", hence my "htmlxref.cnf" is  at
> "~/.homebrew/share/texinfo/htmlxref.cnf".  There is no
> "/usr/share/texinfo/htmlxref.cnf".
>
> Texinfo doesn't read a single file anyway, but all of these, and
> merges them into a single file.  For my manual, I use an additional
> "htmlxref.cnf" right next to the ".texi" source to add some missing
> links.
>
> The Org exporter should take all of these files, and merge them by the
> same rules.  For system-wide configuration files, it should either try
> to get the right prefix out of the "makeinfo" executable in
> "exec-path" (as returned by "executable-find"), or take the list of
> files from a customization option.  The latter is probably easier, and
> more predictable to the user.

Well, that's too much work for me now.  Hopefully someone who needs
this can help too.

> Implementing this likely amounts to a fair bit of work, which I was
> somewhat disappointed to learn that Org doesn't do it already :)

Me too ;)

-- 
 Bastien

Re: [O] HTML export and info: links

2013/7/3 Bastien :
> Sebastian Wiesner  writes:
>
>> Ideally the HTML exporter would consult this database when exporting
>> info links, to find out where the corresponding HTML manual is
>> published.
>
> I see, thanks.  Is it safe to assume that htmlxref.cnf will always
> be located in /usr/share/texinfo/?  E.g. is it for you?

It's not actually located there at all.  My Texinfo is installed via
Homebrew into "~/.homebrew", hence my "htmlxref.cnf" is  at
"~/.homebrew/share/texinfo/htmlxref.cnf".  There is no
"/usr/share/texinfo/htmlxref.cnf".

Texinfo doesn't read a single file anyway, but all of these, and
merges them into a single file.  For my manual, I use an additional
"htmlxref.cnf" right next to the ".texi" source to add some missing
links.

The Org exporter should take all of these files, and merge them by the
same rules.  For system-wide configuration files, it should either try
to get the right prefix out of the "makeinfo" executable in
"exec-path" (as returned by "executable-find"), or take the list of
files from a customization option.  The latter is probably easier, and
more predictable to the user.

Implementing this likely amounts to a fair bit of work, which I was
somewhat disappointed to learn that Org doesn't do it already :)

[O] [BUG] Two problems with defcustom of org-structure-template-alist

There seem to be two problem in the defcustom of
org-structure-template-alist. It looks like this:

--8<---cut here---start->8---
  :type '(repeat
  (string :tag "Key")
  (string :tag "Template")
  (string :tag "Muse Template")))
--8<---cut here---end--->8---

and afaict, this is not well-formed, so when I try to customize it,
I get a (mismatch). I believe it should look like this:

--8<---cut here---start->8---
  :type '(repeat
  (list
   (string :tag "Key")
   (string :tag "Template")
   (string :tag "Muse Template"
--8<---cut here---end--->8---

That's the first problem, but even after doing this, I still get a
(mismatch).

I think the (second) problem now is that the Muse Template is not
optional as far as defcustom is concerned, but there are entries in the
list above with only two elements. If I add a third element (an empty
string) to those entries missing it, I can customize to my heart's
content.

The question is: is the Muse Template optional? If so, how does one
tell defcustom that? I did a cursory reading of the customization
chapter in the elisp manual but my brain refuses to cooperate.

GNU Emacs 24.3.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of
2013-06-17 on pierrot
Org-mode version 8.0.3 (release_8.0.3-358-gb0174f @
/home/nick/elisp/org-mode/lisp/)

Thanks!
-- 
Nick

Re: [O] possible org-insert-heading bug?

2013-07-03 Thread Robert Horn


Erik Iverson writes:

> Robert,
>
> I noticed that behavior, too. But that does seem documented under M-:
>
> "When this command is used in the middle of a line, the line is split
> and the rest of the line becomes the new item or headline".
>
> Footnote 10 is referenced, which says:
>
> "If you do not want the line to be split, customize the variable
> org-M-RET-may-split-line."
>

That's what I wanted and expected.  That's not what happened.  The line
was not split.  The whole line became a new headline.  What I wanted was
the line to be split and the tail end to be the new headline.

>> I've noticed a probably related bug.  In a file like
>>
>> * before
>>   break between
>>
>> If I put the cursor between break and between, M-ret causes the result
>>
>> * before
>> * break between
>>
>> rather than what I expected:
>>
>> * before
>>   break
>> * between
>>
>> With the holiday coming I might look at it also and figure out what is
>> happening.
>>
>> R Horn
>>
>> Carsten Dominik writes:
>>
>>> Hi,
>>>
>>> yes, org-insert-heading is broken - nad I am trying to find time
>>> to rewrite it.  My top Org priority.
>>>
>>> - Carsten
>>>
>>> On 3.7.2013, at 00:11, John Hendy  wrote:
>>>
 Hi Erik,


 Glad to see you around :)

 These all may be quite related. I haven't seen activity on those
 threads suggesting whether a) the documentation is, in fact, right or
 wrong or b) whether anyone has taken action to fix or adjust the
 behavior of M-RET or C-RET based on the complaints/counter-intuitive
 observations.

 Let me know if those are similar to your issue. Perhaps Bastien can
 comment on the state of these thread, now at least four in number...

 - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg70718.html
 - http://osdir.com/ml/emacs-orgmode-gnu/2013-05/msg00846.html
 - http://permalink.gmane.org/gmane.emacs.orgmode/72399

 I've taken to using C-RET in the meantime, as it seems to do what I
 often expect when reflexively pressing M-RET. Also, someone once
 corrected me on the documentation that "at the end of the line" might
 mean before the ellipsis, not after?


 Hope that helps!
 John


 On Tue, Jul 2, 2013 at 1:53 PM, Erik Iverson  
 wrote:
> Hello,
>
> I am using a current git pull (Org-mode version 8.0.3,
> release_8.0.3-345-g239aa7) and noticed behavior that's easiest to show
> with a small example. If you save and visit the following org file,
>
> https://dl.dropboxusercontent.com/u/7514404/test.org
>
> you will see the behavior described and documented (assuming it's
> reproducible under your version of emacs and orgmode).
>
> Briefly M- at the end of a *folded* headline that contains plain
> list items will insert a new plain list item at the end of the
> subtree, instead of a new top-level headline. I believe this conflicts
> with the documentation for M-, which currently reads:
>
> ... If the command is used at the end of a folded subtree (i.e.,
> behind the ellipses at the end of a headline), then a headline like
> the current one will be inserted after the end of the subtree...
>
> Best,
> --Erik
>

>>

[O] org-clock-is-active

2013-07-03 Thread Łukasz Stelmach

Hi.

Please take a look at this.

--8<---cut here---start->8---
(defun org-clock-is-active ()
  "Return non-nil if clock is currently running.
The return value is actually the clock marker."
  (marker-buffer org-clock-marker))
--8<---cut here---end--->8---

Either the docstring is lying or the code does not do what it is said
to. (Or it is too late for me?)

Bug? Feature?

Kind regards,
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

Re: [O] possible org-insert-heading bug?

2013-07-03 Thread Erik Iverson

Robert,

I noticed that behavior, too. But that does seem documented under M-:

"When this command is used in the middle of a line, the line is split
and the rest of the line becomes the new item or headline".

Footnote 10 is referenced, which says:

"If you do not want the line to be split, customize the variable
org-M-RET-may-split-line."

Hope this helps,
--Erik

On Wed, Jul 3, 2013 at 10:01 AM, Robert Horn  wrote:
> I've noticed a probably related bug.  In a file like
>
> * before
>   break between
>
> If I put the cursor between break and between, M-ret causes the result
>
> * before
> * break between
>
> rather than what I expected:
>
> * before
>   break
> * between
>
> With the holiday coming I might look at it also and figure out what is
> happening.
>
> R Horn
>
> Carsten Dominik writes:
>
>> Hi,
>>
>> yes, org-insert-heading is broken - nad I am trying to find time
>> to rewrite it.  My top Org priority.
>>
>> - Carsten
>>
>> On 3.7.2013, at 00:11, John Hendy  wrote:
>>
>>> Hi Erik,
>>>
>>>
>>> Glad to see you around :)
>>>
>>> These all may be quite related. I haven't seen activity on those
>>> threads suggesting whether a) the documentation is, in fact, right or
>>> wrong or b) whether anyone has taken action to fix or adjust the
>>> behavior of M-RET or C-RET based on the complaints/counter-intuitive
>>> observations.
>>>
>>> Let me know if those are similar to your issue. Perhaps Bastien can
>>> comment on the state of these thread, now at least four in number...
>>>
>>> - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg70718.html
>>> - http://osdir.com/ml/emacs-orgmode-gnu/2013-05/msg00846.html
>>> - http://permalink.gmane.org/gmane.emacs.orgmode/72399
>>>
>>> I've taken to using C-RET in the meantime, as it seems to do what I
>>> often expect when reflexively pressing M-RET. Also, someone once
>>> corrected me on the documentation that "at the end of the line" might
>>> mean before the ellipsis, not after?
>>>
>>>
>>> Hope that helps!
>>> John
>>>
>>>
>>> On Tue, Jul 2, 2013 at 1:53 PM, Erik Iverson  wrote:
 Hello,

 I am using a current git pull (Org-mode version 8.0.3,
 release_8.0.3-345-g239aa7) and noticed behavior that's easiest to show
 with a small example. If you save and visit the following org file,

 https://dl.dropboxusercontent.com/u/7514404/test.org

 you will see the behavior described and documented (assuming it's
 reproducible under your version of emacs and orgmode).

 Briefly M- at the end of a *folded* headline that contains plain
 list items will insert a new plain list item at the end of the
 subtree, instead of a new top-level headline. I believe this conflicts
 with the documentation for M-, which currently reads:

 ... If the command is used at the end of a folded subtree (i.e.,
 behind the ellipses at the end of a headline), then a headline like
 the current one will be inserted after the end of the subtree...

 Best,
 --Erik

>>>
>

Re: [O] [BUG] Tag selection is inconsistent when loaded from #+SETUPFILE in orgmode 8.0.x

Hi Anupam,

Anupam Sengupta  writes:

> Thanks a lot for the fix.  The test files are now behaving properly
> after the fix (I am on orgmode git development head at commit
> 36848fdec9eb8c9c17a2e98cd742af1f9f9b23db as on 23rd May).
>
> *However*, while testing this fix, I think I have uncovered a few more bugs(?)
> with the +SETUPFILE interaction with the in-buffer tag selection.
>
> Specifically, if the +SETUPFILE contains /any/ of the following
> directives (not exhaustive, just what my setup happened to have), then
> the tag listing in the completion buffer is showing _duplicated lists_
> of the tags read from the setup file:

I finally fixed this.  Thanks,

-- 
 Bastien

Re: [O] possible org-insert-heading bug?

2013-07-03 Thread Robert Horn

I've noticed a probably related bug.  In a file like

* before
  break between

If I put the cursor between break and between, M-ret causes the result

* before
* break between

rather than what I expected:

* before
  break
* between

With the holiday coming I might look at it also and figure out what is
happening.

R Horn

Carsten Dominik writes:

> Hi,
>
> yes, org-insert-heading is broken - nad I am trying to find time
> to rewrite it.  My top Org priority.
>
> - Carsten
>
> On 3.7.2013, at 00:11, John Hendy  wrote:
>
>> Hi Erik,
>> 
>> 
>> Glad to see you around :)
>> 
>> These all may be quite related. I haven't seen activity on those
>> threads suggesting whether a) the documentation is, in fact, right or
>> wrong or b) whether anyone has taken action to fix or adjust the
>> behavior of M-RET or C-RET based on the complaints/counter-intuitive
>> observations.
>> 
>> Let me know if those are similar to your issue. Perhaps Bastien can
>> comment on the state of these thread, now at least four in number...
>> 
>> - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg70718.html
>> - http://osdir.com/ml/emacs-orgmode-gnu/2013-05/msg00846.html
>> - http://permalink.gmane.org/gmane.emacs.orgmode/72399
>> 
>> I've taken to using C-RET in the meantime, as it seems to do what I
>> often expect when reflexively pressing M-RET. Also, someone once
>> corrected me on the documentation that "at the end of the line" might
>> mean before the ellipsis, not after?
>> 
>> 
>> Hope that helps!
>> John
>> 
>> 
>> On Tue, Jul 2, 2013 at 1:53 PM, Erik Iverson  wrote:
>>> Hello,
>>> 
>>> I am using a current git pull (Org-mode version 8.0.3,
>>> release_8.0.3-345-g239aa7) and noticed behavior that's easiest to show
>>> with a small example. If you save and visit the following org file,
>>> 
>>> https://dl.dropboxusercontent.com/u/7514404/test.org
>>> 
>>> you will see the behavior described and documented (assuming it's
>>> reproducible under your version of emacs and orgmode).
>>> 
>>> Briefly M- at the end of a *folded* headline that contains plain
>>> list items will insert a new plain list item at the end of the
>>> subtree, instead of a new top-level headline. I believe this conflicts
>>> with the documentation for M-, which currently reads:
>>> 
>>> ... If the command is used at the end of a folded subtree (i.e.,
>>> behind the ellipses at the end of a headline), then a headline like
>>> the current one will be inserted after the end of the subtree...
>>> 
>>> Best,
>>> --Erik
>>> 
>>

Re: [O] fill paragraph: math and latex environments

2013-07-03 Thread Paul Stansell

Nicolas,

Thanks for your reply.

> If we allow \[...\] constructs to be an element, they cannot be
> recognized as such within paragraphs. So
>
>   Some text \[1+1\] and some other text
>
> will not be recognized anymore, even though any latex editing mode
> supports it. Again, I think it's not worth loosing it.
>
> Also, using \begin{...}...\end{...} environments is not really an issue
> with editing facilities in Emacs (e.g., yasnippets).

I'm sorry, but I don't fully understand your explanation as I don't
know what you mean by an "element" in this context?

Also, am I missing something about the latex?  Do you want to be able
to use display style maths inside a sentence (ie. avoid placing the
maths on a new line but have it formatted in display style)?  That
would seem strange as that's not what it's for.  I don't, therefore,
see why anyone would want to write

  Some text \[1+1\] and some other text

as in the resulting processed document it will look like

  Some text
 1+1
  and some other text

I think one should instead write

Some text \(1+1\) and some other text

or

   Some text $1+1$ and some other text

which, in the processed document, will look like

Some text 1+1 and some other text

If someone wants a display maths equation they could write it in their
org file as

  Some text
  \[
 1+1
  \]
   and some other text

so that the look of the org file resembles more closely that of the
processed document.

> Also, using \begin{...}...\end{...} environments is not really an issue
> with editing facilities in Emacs (e.g., yasnippets).

I agree with you there.  It's not a big deal type, but I do think

\[
1+1
\[

looks a lot nicer and cleaner in the org file than

\begin{displaymath}
1+1
\end{displaymath}

Kind regards,

Paul

Re: [O] org-mode and python pandas

2013-07-03 Thread Eric Schulte

Dov Grobgeld  writes:

> Thanks for the answers, but there is still something missing in order
> to get it to work. Part of it seems to be connected to the python
> parsing. E.g. the following translation of Eric's sh example doesn't
> output correctly with python:
>
>
> #+BEGIN_SRC python :results output
> print """,A,B,C
> 0,0.628365,0.424279,0.619791
> 1,0.799666,0.527572,0.132928
> 2,0.837255,0.138906,0.408233
> 3,0.388080,0.146212,0.575346
> """
> #+END_SRC
>
> #+RESULTS:
> : ,A,B,C
> : 0,0.628365,0.424279,0.619791
> : 1,0.799666,0.527572,0.132928
> : 2,0.837255,0.138906,0.408233
> : 3,0.388080,0.146212,0.575346
>
>
> #+BEGIN_SRC python :results table
> return """,A,B,C
> 0,0.628365,0.424279,0.619791
> 1,0.799666,0.527572,0.132928
> 2,0.837255,0.138906,0.408233
> 3,0.388080,0.146212,0.575346
> """
> #+END_SRC
>
> #+RESULTS:
> | 
> ,A,B,C\n\n0,0.628365,0.424279,0.619791\n\n1,0.799666,0.527572,0.132928\n\n2,0.837255,0.138906,0.408233\n\n3,0.388080,0.146212,0.575346
> |
>
> It seems that the only way to get a table from python is by outputting
> a two dimensional python structure:
>
> #+BEGIN_SRC python
> return [[0,0.628365,0.424279,0.619791],
> [1,0.799666,0.527572,0.132928]]
> #+END_SRC
>
> #+RESULTS:
> | 0 | 0.628365 | 0.424279 | 0.619791 |
> | 1 | 0.799666 | 0.527572 | 0.132928 |
>
> This seems quite limiting
>

In most cases this is what one wants when returning data from python
code.  The following elisp defined a "panda" code block, which is just
like python, only it assumes that the results will be these sort of
human readable strings instead of python code.

;; -*- emacs-lisp -*-
(defun org-babel-execute:panda (body params)
  (let ((results
 (org-babel-execute:python
  body (org-babel-merge-params '((:results . "scalar")) params
(org-babel-result-cond (cdr (assoc :result-params params))
  results
  (let ((tmp-file (org-babel-temp-file "sh-")))
(with-temp-file tmp-file (insert results))
(org-babel-import-elisp-from-file tmp-file)

With the above evaluated the following works

#+BEGIN_SRC panda
return """,A,B,C
0,0.628365,0.424279,0.619791
1,0.799666,0.527572,0.132928
2,0.837255,0.138906,0.408233
3,0.388080,0.146212,0.575346
"""
#+END_SRC

#+RESULTS:
|   |A |B |C |
| 0 | 0.628365 | 0.424279 | 0.619791 |
| 1 | 0.799666 | 0.527572 | 0.132928 |
| 2 | 0.837255 | 0.138906 | 0.408233 |
| 3 |  0.38808 | 0.146212 | 0.575346 |

>
> Another related question is if there is any support for header tables?
> I.e. instead of this:
>
> |   |A |B |C |
> | 0 | 0.827817 | 0.664009 | 0.089161 |
> | 1 | 0.170031 | 0.729214 | 0.110918 |
> | 2 | 0.575918 | 0.863924 | 0.757536 |
> | 3 | 0.682722 | 0.774445 | 0.992041 |
>
> I want this:
>
> |   |A |B |C |
> |---+--+--+--|
> | 0 | 0.827817 | 0.664009 | 0.089161 |
> | 1 | 0.170031 | 0.729214 | 0.110918 |
> | 2 | 0.575918 | 0.863924 | 0.757536 |
> | 3 | 0.682722 | 0.774445 | 0.992041 |
>
> I guess that if I start playing around with the python ob module, it
> should be possible to get this working?
>

See the :colnames header argument in the manual.

Best,

>
> Regards,
> Dov
>
> On Mon, Jul 1, 2013 at 8:04 PM, Rasmus  wrote:
>> Achim Gratz  writes:
>>
> 2. Add to pandas the option of globally influencing the text
> formatting so that it outputs something more parsable by org-mode.

 This sounds promising, if pandas support csv output that will be
 correctly parsed by Org-mode.
>>>
>>> The package already has CSV export, so one could use that.  I don't know
>>> if you could echo the result directly to the output, all examples
>>> revolve around putting the CSV into a file.  For Org, TSV output would
>>> be more natural.
>>
>> Something like:
>>
>> from pandas import DataFrame
>> from numpy.random import rand
>> from sys import stdout
>> df = DataFrame(rand(10,3), columns = list('abc'))
>> df
>> df.to_csv(stdout, sep="\t", header = True, cols=(1,2))
>>
>> I was completely unable to get ob-python working this morning, so I
>> haven't tested it.  I'm using python3, build in python mode and elpy.
>>
>> In any case, the csv route might be better, as Pandas doesn't print
>> the table if it's too big (try changing 10 to 1000 above).
>>
>> --
>> Powered by magic pixies!
>>
>>
>

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

Re: [O] tag groups

Hi Maurice,

Maurice  writes:

> value for : org-tag-alist-for-agenda
>
>  ((:startgroup)
>  ("prêté" . 112)
>  ("emprunté" . 101)
>  (:endgroup)
>  ("note" . 110)
>  ("noexport" . 120)
>  ("lien" . 98)
>  ("crypt" . 99)
>  ("projet" . 112)
>  ("suspendu" . 122)
>  (:startgroup "lieu")
>  ("@dehors" . 100)
>  (:grouptags)
>  ("@lieu1" . 97)
>  ("@lieu2" . 118))

You're missing an :endgroup here -- that's weird.

> org-tag-groups-alist 
> org-tag-groups-alist-for-agenda
>
> keep their original value : nil
>
> If I filter by tag @dehors, I do not get the new filter by tags
> @dehors or @lieu1 or @lieu2.

I just fixed a bug wrt to handling the "@" character in tags.

Can you pull from the git repo and report if you still have the
issue you reported?  If so, please add an example I can quickly
use to reproduce the problem.

Thanks!

-- 
 Bastien

Re: [O] [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.

2013-07-03 Thread Feng Shu

Suvayu Ali  writes:

> On Wed, Jul 03, 2013 at 02:22:40PM +0800, Feng Shu wrote:
>> Suvayu Ali  writes:
>> 
>> > On Wed, Jul 03, 2013 at 07:09:35AM +0800, feng shu wrote:
>> >> Customize  `org-latex-pdf-process isn't very convenient.
>> >> Is it possible add a  feature like: #+LATEX_PDF_PROCESS:  latexmk
>> >> or add  #OPTIONS:  ;latex_pdf_process  latexmk
>> >
>> > If you don't mind my chiming in, the standard way to customise Emacs
>> > behaviour (across all modes, not just Org) is through
>> > customize-variable.  Org cannot keep on introducing new keywords just
>> > because of convenience.
>> 
>> I don't think so, Convenience is very important in most situation. we can
>> introduce new keywords just for convenience!  #+LATEX_CLASS is a good 
>> example,
>> If we don't want convencience.  we can just customize 
>> `org-latex-default-class
>
> There is a big difference between the two variables.  Consider this:
> org-latex-classes depends per document (most likely you wand different
> documents for different things, hence maybe you also want different
> classes), however you want to choose your LaTeX backend once (at most it
> varies from project to project).  But again, if you use one build system
> for a project you are most likely using the same build system in other
> projects too.  The only difference I can see is when you have something
> like make for projects, but simply LaTeX for a simple document/notes.
> In that case, I would say Bastien's suggestion to use file local
> variables is best suited.  At one point I used something like this
> headline at the end of few Org files:
>
> * COMMENT local setup :ARCHIVE:
>
> # Local Variables:
> # org-latex-to-pdf-process: ("xelatex -interaction nonstopmode
> -output-directory %o %f" "xelatex -interaction nonstopmode
> -output-directory %o %f" "xelatex -interaction nonstopmode
> -output-directory %o %f")
> # End:

Powerful Tips, I like!  Maybe it should be include into org document. 

>
> Hope this helps,

--

[O] Sort check lists by checked status

I just pushed a change in master: you can now sort check lists
by the "checked" status.  `C-c ^ c' on a check list will put the
checked item at the end.  I've been using this quite heavily, I
hope other will find this useful.

-- 
 Bastien

Re: [O] scrum with emacs org-mode

2013-07-03 Thread Oliver Dunkl

thk...@koch.ro writes:

> has anybody some success stories to share how to use org-mode in scrum
> projects? Googling for scrum and org-mode already showed some
> interesting things:

I have made some additions to my agenda commands to produce a
Scrum-Board for the current file or a defined file.

My status for the Board are:

TODO - all open tasks
PROG - all tasks currently in progress
DONE - all done tasks
IDEA - all tasks in the backlog

(setq org-agenda-custom-commands
("W" . "Work queries")
("Ws" . "Scrum Boards"
 ;; all open tasks
 ((todo "TODO"
((org-agenda-files '("Work.org"))
 (org-agenda-overriding-header "All open tasks:")
 (org-agenda-todo-keyword-format "")
 (org-agenda-sorting-strategy '(priority-down
  ;; all tasks currently in progress
  (todo "PROG"
((org-agenda-files '("Work.org"))
 (org-agenda-overriding-header "All tasks in progess:")
 (org-agenda-todo-keyword-format "")
 (org-agenda-sorting-strategy '(priority-down
  ;; product backlog
  (todo "IDEA"
((org-agenda-files '("Work.org"))
 (org-agenda-todo-keyword-format "")
 (org-agenda-overriding-header "Product Backlog:")))
  ;; all done tasks
  (todo "DONE"
((org-agenda-files '("Work.org"))
 (org-agenda-overriding-header "All done tasks:")
 (org-agenda-todo-keyword-format "")
 (org-agenda-sorting-strategy '(priority-down)))

So if you like to produce the Scrum-Board for the current file

C-c < a W s

or for the given file 'Work.org'

C-c a W s

You can also tag your sprints if you like. I have very good experience
with that approach for multiple projects at the same time.

\= odi

Oliver Dunkl
Software Engineer

Re: [O] Starting emacs followed directly by org-agenda search and visiting file removes color formatting

Hi Mike,

Mike McLean  writes:

> Did you ever find a resolution for this? I am experiencing very
> similar, né identical, symptoms.

I applied Nicolas' patch from this thread.

Thanks for the heads up,

-- 
 Bastien

Re: [O] [patch] language support for da, no, sv.

Nicolas Goaziou  writes:

> Applied to master.

You're too fast :)

I suggested minor changes to Rasmus for the ChangeLog entry: uppercase
first letter of the sentence, and to avoid the passive form.

Anyway, just a boring reminder that this is important: I will have to
fix all changelog entries before committing to Emacs (and get spanked
for entries I overlooked.)

> Note that you needn't add TINYCHANGE anymore, since
> you signed FSF papers.

Indeed.

Thanks to both of you,

-- 
 Bastien

Re: [O] [patch v2] language support for da, no, sv.

Rasmus  writes:

> Attached are two minor patches with respect to languages plus one
> change to the org translation dictionary.

Only the changelog are changed in these patches to follow the standard
format better.

–Rasmus

-- 
If you can mix business and politics wonderful things can happen!
>From f78487862ea006458ad90084b29a2fa9fc5d6543 Mon Sep 17 00:00:00 2001
From: rasmus 
Date: Wed, 3 Jul 2013 12:06:24 +0200
Subject: [PATCH 1/3] Bugfix for Norwegian in ox.el
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* ox-latex.el (org-latex-babel-language-alist): Added 'nb', 'nn', and
'no' for Norwegian.  Removed 'no-no'.

In ox.el Norwegian is given by 'no' for Norwegian, 'nb' for bokmål,
and 'nn' for nynorsk, correspond to the ISO-2 language codes.  'no-no'
is not defined in ox.el.

TINYCHANGE
---
 lisp/ox-latex.el | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index dcbed54..de6f6f9 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -143,7 +143,9 @@
 ("la" . "latin")
 ("ms" . "malay")
 ("nl" . "dutch")
-("no-no" . "nynorsk")
+("nb" . "norsk")
+("nn" . "nynorsk")
+("no" . "norsk")
 ("pl" . "polish")
 ("pt" . "portuguese")
 ("ro" . "romanian")
@@ -342,7 +344,6 @@ the toc:nil option, not to those generated with #+TOC keyword."
   :group 'org-export-latex
   :type 'boolean)
 
-
  Headline
 
 (defcustom org-latex-format-headline-function
-- 
1.8.3.2

>From 9478a3ed8e8accb83685b68716cfa1ed918c6ea5 Mon Sep 17 00:00:00 2001
From: rasmus 
Date: Wed, 3 Jul 2013 12:09:21 +0200
Subject: [PATCH 2/3] Extended org-export-default-language docstring

* ox.el (org-export-default-language): Mention other variables
affected by language.

TINYCHANGE
---
 lisp/ox.el | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/lisp/ox.el b/lisp/ox.el
index a043dd6..6531fa3 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -501,8 +501,9 @@ e.g. \"H:2\"."
 (defcustom org-export-default-language "en"
   "The default language for export and clocktable translations, as a string.
 This may have an association in
-`org-clock-clocktable-language-setup'.  This option can also be
-set with the LANGUAGE keyword."
+`org-clock-clocktable-language-setup',
+`org-export-smart-quotes-alist' and `org-export-dictionary'.
+This option can also be set with the LANGUAGE keyword."
   :group 'org-export-general
   :type '(string :tag "Language"))
 
-- 
1.8.3.2

>From d33611074cc574cd3afdb6aec7b5cd136c6807d2 Mon Sep 17 00:00:00 2001
From: rasmus 
Date: Wed, 3 Jul 2013 12:15:26 +0200
Subject: [PATCH 3/3] Some language support for Danish, Swedish and Norwegian

* ox.el (org-export-smart-quotes-alist): Add ("da" "no" "nb" "nn"
"sv").
* ox.el (org-export-dictionary): Add some entries ("da" "no" "nb" "nn"
 "sv").

These languages are rather unrestricted with respect to typesetting,
so some changes may to some extend reflect personal preferences.
---
 lisp/ox.el | 87 +++---
 1 file changed, 84 insertions(+), 3 deletions(-)

diff --git a/lisp/ox.el b/lisp/ox.el
index 6531fa3..92ad356 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -4893,7 +4893,20 @@ Return a list of src-block elements with a caption."
 ;; `org-export-smart-quotes-regexps'.
 
 (defconst org-export-smart-quotes-alist
-  '(("de"
+  '(("da"
+ ;; one may use: »...«, "...", ›...‹, or '...'.
+ ;; http://sproget.dk/raad-og-regler/retskrivningsregler/retskrivningsregler/a7-40-60/a7-58-anforselstegn/
+ ;; LaTeX quotes require Babel!
+ (opening-double-quote :utf-8 "»" :html "»" :latex ">>"
+			   :texinfo "@guillemetright{}")
+ (closing-double-quote :utf-8 "«" :html "«" :latex "<<"
+			   :texinfo "@guillemetleft{}")
+ (opening-single-quote :utf-8 "›" :html "›" :latex "\\frq{}"
+			   :texinfo "@guilsinglright{}")
+ (closing-single-quote :utf-8 "‹" :html "‹" :latex "\\flq{}"
+			   :texinfo "@guilsingleft{}")
+ (apostrophe :utf-8 "’" :html "’"))
+("de"
  (opening-double-quote :utf-8 "„" :html "„" :latex "\"`"
 			   :texinfo "@quotedblbase{}")
  (closing-double-quote :utf-8 "“" :html "“" :latex "\"'"
@@ -4926,7 +4939,42 @@ Return a list of src-block elements with a caption."
 			   :texinfo "@guillemetleft{}@tie{}")
  (closing-single-quote :utf-8 " »" :html " »" :latex "\\fg{}"
 			   :texinfo "@tie{}@guillemetright{}")
- (apostrophe :utf-8 "’" :html "’")))
+ (apostrophe :utf-8 "’" :html "’"))
+("no"
+ ;; https://nn.wikipedia.org/wiki/Sitatteikn
+ (opening-double-quote :utf-8 "«" :html "«" :latex "\\guillemotleft{}"
+			   :texinfo "@guillemetleft{}")
+ (closing-double-quote :utf-8 "»" :html "»" :latex "\\guillemotright{}"
+			   :texinfo "@guillemetright{}")
+ (opening-single-quote :utf-8 "‘" :html "‘" :latex "`" :texinfo "`")
+ (closing-single-quote :utf-8 "’" :html "’" :latex "'" :texinfo "'")
+ (apostrophe :ut

Re: [O] [patch] language support for da, no, sv.

2013-07-03 Thread Nicolas Goaziou

Hello,

Rasmus  writes:

> Attached are two minor patches with respect to languages plus one
> change to the org translation dictionary.

Applied to master. Note that you needn't add TINYCHANGE anymore, since
you signed FSF papers.

Thank you.


Regards,

-- 
Nicolas Goaziou

[O] org-mime-htmlize problem: org-indent-line

2013-07-03 Thread Martin Marier

Hi,

I had an issue with org-mime-htmlize lately.  Whenever I try to htmlize
a Messoage mode buffer (M-x org-mime-htmlize), I get this error message:

eval: Symbol's value as variable is void: org-indent-line

I am using Org-mode version 8.0.3 (8.0.3-61-g5381eb-elpa @ 
~/.emacs.d/elpa/org-20130701/)

Has anyone else had the same issue?
Thank you very much.

Martin
-- 
Martin Marier
http://www.martinmarier.com

Re: [O] Break a line in org-mode

2013-07-03 Thread Søren Mikkelsen

On 2013-07-03 11:01, Rasmus wrote:
> Søren Mikkelsen  writes:
> 
>> I usually have some #+LaTeX_HEADER: entries in my org-mode files where
>> some of them are macros. These lines can be rather long so I have to
>> type in #+LaTeX_HEADER: multiple times for breaking the line to a decent
>> level.
>>
>> Is there a way of breaking a line when it is export options (or a
>> regular comment in org-mode)?
> 
> No.  But maybe you could do 
> 
> #+LATEX_HEADER: \input{pre}
> #+BEGIN_SRC LATEX :tangle pre.tex
> \usepackage{mypackage}
> #+END_SRC
> 
> Or you could make a new Org-Latex, see the variable org-latex-classes
> if you have the same problem often.  
> 
> Some people entertained the idea of writing sty and/or cls files
> recently on this list.  If you use the same macros all over perhaps
> you should pack them as a sty or the very least as an external tex
> file, I guess.
> 
> Alternatively, use the function string-rectangle.  In the following
> example, place your mark at the first `|', click C-Space, move to the
> second `|' click C-x r t LATEX_HEADER RET.
> 
> |\usepackage{pac1}
>  \usepackage{pac1}
> |\usepackage{pac1}.
> 
> Hope it helps. 
> 
> –Rasmus
> 

Okay, just thought that there might be a symbol for that. That could
have been nice.

But thanks for the suggestions.

--
Søren

Re: [O] Starting emacs followed directly by org-agenda search and visiting file removes color formatting

2013-07-03 Thread Mike McLean

Good Morning

Did you ever find a resolution for this? I am experiencing very similar, né
identical, symptoms.

Mike



On Mon, May 20, 2013 at 6:47 PM, John Hendy  wrote:

> On Mon, May 20, 2013 at 5:15 PM, John Hendy  wrote:
> > Sorry for the long title, but that's the summary! I fired up a fresh
> > Emacs session and used =C-a s search-term RET= to navigate to a
> > headline in the results by putting the cursor on the line and pressing
> > RET.
> >
> > The file text was all black.
> >
> > If I visited the file directly, I had the typical color-coded text for
> > headlines/keywords. I decided to replicate with a minimal config, and
> > I was able to. Here's the context of the min config:
> >
> > #+begin_min-config
> > ;; set load paths
> > ;; set load dirs and global config options
> > (add-to-list 'load-path "~/.elisp/org.git/lisp/")
> > (add-to-list 'load-path "~/.elisp/org.git/contrib/lisp")
> > #+end_min-config
> >
> > This was on a work file, and I couldn't initially replicate with a
> > test file... but it appears it has to do with my header options.
> > Here's the test file:
> >
> > #+begin_src org
> > #+setupfile: "~/org/aux/setupfile.org"
> > #+options: <:t num:t author:t creator:nil tags:t toc:nil date:t
> > #+latex_header: \usepackage{lscape}
> > #+latex_header: \usepackage{amsmath}
> >
> > * Test headline
> >
> > Some paragraph just to give me a keyword to search for
> >
> > ** Sub headline
> >
> > Some more text in the next headline
> > #+end_src
> >
> > My process:
> > - emacs -Q
> > - M-x load-file RET ~/path/to/min-config RET
> > - C-x C-f /path/to/file.org RET
> > - C-c [ to add to agenda list
> > - C-x C-k RET to kill buffer
> > - M-x org-agenda RET s RET text RET
> > - Navigate to test.org matching line RET
> > - File looks like attached pic
> >
> > I deleted everything but my #+setupfile line and it still does that.
>
> Last bit of input -- when this behavior is displayed, if I C-c C-c on
> my options block at the top of the file, it returns to fontified
> behavior and stays that way (even if meddling with headlines). It
> appears that navigating to a headline with various #+keyword lines is
> not letting Org recognize something. Refreshing the setup seems to
> handles this. This is on:
>
> Org-mode version 8.0.3 (release_8.0.3-139-g419b69 @
> /home/jwhendy/.elisp/org.git/lisp/)
>
> Happy to try anything else or provide more info. For now, I think I've
> made enough noise about this!
>
>
> Thanks,
> John
>
> >
> > Without any #+ options at the top of the file, it appears in color.
> >
> >
> > John
>
>

Re: [O] Break a line in org-mode

2013-07-03 Thread Søren Mikkelsen

On 2013-07-03 10:21, Nick Dokos wrote:
> Søren Mikkelsen  writes:
> 
>> I usually have some #+LaTeX_HEADER: entries in my org-mode files where
>> some of them are macros. These lines can be rather long so I have to
>> type in #+LaTeX_HEADER: multiple times for breaking the line to a decent
>> level.
>>
>> Is there a way of breaking a line when it is export options (or a
>> regular comment in org-mode)?
>>
> Wouldn't it be better to put the macros in a separate file (say
> mymacros.sty) and use
> 
> #+LATEX_HEADER: \usepackage{mymacros}
> 
> ? Less clutter in the org file and if the macros are more generally useful,
> you can make it available, say by moving it to your personal texmf
> directory (mine is at ~/.texmf-var/tex/latex but ymmv) and running texhash.
> 

Well, I would like it to be in one file. If I, for instance, want to
have long author list, it is not possible to do without having all the
names on one line.

I through maybe that there was a newline symbol, like in python or matlab.

--
Søren

Re: [O] org-mode and python pandas

Hi Dov,

> Another related question is if there is any support for header tables?
> I.e. instead of this:
>
> |   |A |B |C |
> | 0 | 0.827817 | 0.664009 | 0.089161 |
> | 1 | 0.170031 | 0.729214 | 0.110918 |
> | 2 | 0.575918 | 0.863924 | 0.757536 |
> | 3 | 0.682722 | 0.774445 | 0.992041 |
>
> I want this:
>
> |   |A |B |C |
> |---+--+--+--|
> | 0 | 0.827817 | 0.664009 | 0.089161 |
> | 1 | 0.170031 | 0.729214 | 0.110918 |
> | 2 | 0.575918 | 0.863924 | 0.757536 |
> | 3 | 0.682722 | 0.774445 | 0.992041 |

This is an issue in R as well, e.g. often I might want to have 
|A|
|-|
|1|
|2|
|-|
|3|

where the last is a summary statistic.  The last hline can be gotten
as 

#+BEGIN_SRC emacs-lisp :var X=mytabel :exports results
(let
((L (- (length X) 1)))
  (append
   (subseq X 0 L)
   (list 'hline)
   (subseq X L)))
#+END_SRC

Perhaps a better way exists?

–Rasmus

-- 
. . . It begins of course with The Internet.  A Net of Peers.

[O] [patch] language support for da, no, sv.

Hi,

Attached are two minor patches with respect to languages plus one
change to the org translation dictionary.

The first fixes inconsistencies between the language code in ox.el and
ox-latex.el for Norwegian.  Before #+LANGUAGE: no would not work.  It
also adds support for Nynorsk.

The second patch adds some more variables to the docstring of
org-export-default-language.  Why?  Because, people may look there
when wanting to add support for more languages, and currently it takes
a bit of effort to find all the variables that needs fixing.

The third patch adds some support for Norwegian, Danish and Swedish
languages in the translation dictionary.  I'm open to criticism of
these translations, of course.

–Rasmus
  
-- 
When the facts change, I change my mind. What do you do, sir?
>From 730ab3e4590ff7f98e88b15ed1ab45180e302124 Mon Sep 17 00:00:00 2001
From: rasmus 
Date: Wed, 3 Jul 2013 12:09:21 +0200
Subject: [PATCH 2/3] Extended org-export-default-language docstring

* ox.el (org-export-default-language): mention other variables
affected by language.

TINYCHANGE
---
 lisp/ox.el | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/lisp/ox.el b/lisp/ox.el
index a043dd6..6531fa3 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -501,8 +501,9 @@ e.g. \"H:2\"."
 (defcustom org-export-default-language "en"
   "The default language for export and clocktable translations, as a string.
 This may have an association in
-`org-clock-clocktable-language-setup'.  This option can also be
-set with the LANGUAGE keyword."
+`org-clock-clocktable-language-setup',
+`org-export-smart-quotes-alist' and `org-export-dictionary'.
+This option can also be set with the LANGUAGE keyword."
   :group 'org-export-general
   :type '(string :tag "Language"))
 
-- 
1.8.3.2

>From 70f9800b97596ab247c61e42abd45c2f434a9423 Mon Sep 17 00:00:00 2001
From: rasmus 
Date: Wed, 3 Jul 2013 12:15:26 +0200
Subject: [PATCH 3/3] Some language support for Danish, Swedish and Norwegian

* ox.el (org-export-smart-quotes-alist): Added ("da" "no" "nb" "nn"
"sv").
* ox.el (org-export-dictionary): Added some entries ("da" "no" "nb"
"nn" "sv").

These languages are rather unrestricted, so some changes may to some
extend reflect my preferences.
---
 lisp/ox.el | 87 +++---
 1 file changed, 84 insertions(+), 3 deletions(-)

diff --git a/lisp/ox.el b/lisp/ox.el
index 6531fa3..92ad356 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -4893,7 +4893,20 @@ Return a list of src-block elements with a caption."
 ;; `org-export-smart-quotes-regexps'.
 
 (defconst org-export-smart-quotes-alist
-  '(("de"
+  '(("da"
+ ;; one may use: »...«, "...", ›...‹, or '...'.
+ ;; http://sproget.dk/raad-og-regler/retskrivningsregler/retskrivningsregler/a7-40-60/a7-58-anforselstegn/
+ ;; LaTeX quotes require Babel!
+ (opening-double-quote :utf-8 "»" :html "»" :latex ">>"
+			   :texinfo "@guillemetright{}")
+ (closing-double-quote :utf-8 "«" :html "«" :latex "<<"
+			   :texinfo "@guillemetleft{}")
+ (opening-single-quote :utf-8 "›" :html "›" :latex "\\frq{}"
+			   :texinfo "@guilsinglright{}")
+ (closing-single-quote :utf-8 "‹" :html "‹" :latex "\\flq{}"
+			   :texinfo "@guilsingleft{}")
+ (apostrophe :utf-8 "’" :html "’"))
+("de"
  (opening-double-quote :utf-8 "„" :html "„" :latex "\"`"
 			   :texinfo "@quotedblbase{}")
  (closing-double-quote :utf-8 "“" :html "“" :latex "\"'"
@@ -4926,7 +4939,42 @@ Return a list of src-block elements with a caption."
 			   :texinfo "@guillemetleft{}@tie{}")
  (closing-single-quote :utf-8 " »" :html " »" :latex "\\fg{}"
 			   :texinfo "@tie{}@guillemetright{}")
- (apostrophe :utf-8 "’" :html "’")))
+ (apostrophe :utf-8 "’" :html "’"))
+("no"
+ ;; https://nn.wikipedia.org/wiki/Sitatteikn
+ (opening-double-quote :utf-8 "«" :html "«" :latex "\\guillemotleft{}"
+			   :texinfo "@guillemetleft{}")
+ (closing-double-quote :utf-8 "»" :html "»" :latex "\\guillemotright{}"
+			   :texinfo "@guillemetright{}")
+ (opening-single-quote :utf-8 "‘" :html "‘" :latex "`" :texinfo "`")
+ (closing-single-quote :utf-8 "’" :html "’" :latex "'" :texinfo "'")
+ (apostrophe :utf-8 "’" :html "’"))
+("nb"
+ ;; https://nn.wikipedia.org/wiki/Sitatteikn
+ (opening-double-quote :utf-8 "«" :html "«" :latex "\\guillemotleft{}"
+			   :texinfo "@guillemetleft{}")
+ (closing-double-quote :utf-8 "»" :html "»" :latex "\\guillemotright{}"
+			   :texinfo "@guillemetright{}")
+ (opening-single-quote :utf-8 "‘" :html "‘" :latex "`" :texinfo "`")
+ (closing-single-quote :utf-8 "’" :html "’" :latex "'" :texinfo "'")
+ (apostrophe :utf-8 "’" :html "’"))
+("nn"
+ ;; https://nn.wikipedia.org/wiki/Sitatteikn
+ (opening-double-quote :utf-8 "«" :html "«" :latex "\\guillemotleft{}"
+			   :texinfo "@guillemetleft{}")
+ (closing-double-quote :utf-8 "»" :html "»" :latex "\\guillemotright{}"
+			   :texin

Re: [O] HTML export and info: links

Sebastian Wiesner  writes:

> Ideally the HTML exporter would consult this database when exporting
> info links, to find out where the corresponding HTML manual is
> published.

I see, thanks.  Is it safe to assume that htmlxref.cnf will always
be located in /usr/share/texinfo/?  E.g. is it for you?

-- 
 Bastien

Re: [O] HTML export and info: links

2013/7/3 Bastien :
> Hi Sebastian,
>
> Sebastian Wiesner  writes:
>
>> I'll put Org mode migration of said manual on hold, for I currently
>> lack the time to write a proper link exporter myself.
>
> I gave this a closer look: one problem is that info links are relative
> to the user installation.
>
> For example [[info:internals#Top]] goes to the XEmacs manual, but
> there is no information about XEmacs in the link itself.

Texinfo deals with problem by mapping Info manual names to URLs of
corresponding online HTML manuals, see the link in my previous post.
The built-in manual database of Texinfo is pretty comprehensive, and
covers almost all GNU manuals, and some more.  It'd be totally
sufficient for my use case.

Ideally the HTML exporter would consult this database when exporting
info links, to find out where the corresponding HTML manual is
published.

Re: [O] Org entries from tables

2013-07-03 Thread Eric Abrahamsen

Bastien  writes:

> Hi Baptiste,
>
> Baptiste  writes:
>
>> Is there a way back (or the other way), that is, create org entries with 
>> associated properties from a table. 
>
> Not to my knowledge (and that of the Org FAQ, FWIW...)
>
> Sorry!

If you were very, very adventurous, however, you could make a babel
block that read rows from a table, marshaled the data into an
org-element parse tree (maybe use `org-element-at-point' on an example
heading to see what the parse tree should look like), and then use
`org-element-interpret-data' to write the tree(s) as text in org syntax.
Probably a lot of work...

Re: [O] HTML export and info: links

Hi Sebastian,

Sebastian Wiesner  writes:

> I'll put Org mode migration of said manual on hold, for I currently
> lack the time to write a proper link exporter myself.

I gave this a closer look: one problem is that info links are relative
to the user installation.

For example [[info:internals#Top]] goes to the XEmacs manual, but
there is no information about XEmacs in the link itself.

We can imagine some hackish prepend-this-URL-to-all-HTML-info-links
but that's really hackish...

> Anyway, thank you for your answer, and please excuse the rather harsh
> brevity of my previous answer.

No problem! 

-- 
 Bastien

Re: [O] org-mode and python pandas

2013-07-03 Thread Dov Grobgeld

Thanks for the answers, but there is still something missing in order
to get it to work. Part of it seems to be connected to the python
parsing. E.g. the following translation of Eric's sh example doesn't
output correctly with python:


#+BEGIN_SRC python :results output
print """,A,B,C
0,0.628365,0.424279,0.619791
1,0.799666,0.527572,0.132928
2,0.837255,0.138906,0.408233
3,0.388080,0.146212,0.575346
"""
#+END_SRC

#+RESULTS:
: ,A,B,C
: 0,0.628365,0.424279,0.619791
: 1,0.799666,0.527572,0.132928
: 2,0.837255,0.138906,0.408233
: 3,0.388080,0.146212,0.575346


#+BEGIN_SRC python :results table
return """,A,B,C
0,0.628365,0.424279,0.619791
1,0.799666,0.527572,0.132928
2,0.837255,0.138906,0.408233
3,0.388080,0.146212,0.575346
"""
#+END_SRC

#+RESULTS:
| 
,A,B,C\n\n0,0.628365,0.424279,0.619791\n\n1,0.799666,0.527572,0.132928\n\n2,0.837255,0.138906,0.408233\n\n3,0.388080,0.146212,0.575346
|

It seems that the only way to get a table from python is by outputting
a two dimensional python structure:

#+BEGIN_SRC python
return [[0,0.628365,0.424279,0.619791],
[1,0.799666,0.527572,0.132928]]
#+END_SRC

#+RESULTS:
| 0 | 0.628365 | 0.424279 | 0.619791 |
| 1 | 0.799666 | 0.527572 | 0.132928 |

This seems quite limiting

Another related question is if there is any support for header tables?
I.e. instead of this:

|   |A |B |C |
| 0 | 0.827817 | 0.664009 | 0.089161 |
| 1 | 0.170031 | 0.729214 | 0.110918 |
| 2 | 0.575918 | 0.863924 | 0.757536 |
| 3 | 0.682722 | 0.774445 | 0.992041 |

I want this:

|   |A |B |C |
|---+--+--+--|
| 0 | 0.827817 | 0.664009 | 0.089161 |
| 1 | 0.170031 | 0.729214 | 0.110918 |
| 2 | 0.575918 | 0.863924 | 0.757536 |
| 3 | 0.682722 | 0.774445 | 0.992041 |

I guess that if I start playing around with the python ob module, it
should be possible to get this working?

Regards,
Dov

On Mon, Jul 1, 2013 at 8:04 PM, Rasmus  wrote:
> Achim Gratz  writes:
>
 2. Add to pandas the option of globally influencing the text
 formatting so that it outputs something more parsable by org-mode.
>>>
>>> This sounds promising, if pandas support csv output that will be
>>> correctly parsed by Org-mode.
>>
>> The package already has CSV export, so one could use that.  I don't know
>> if you could echo the result directly to the output, all examples
>> revolve around putting the CSV into a file.  For Org, TSV output would
>> be more natural.
>
> Something like:
>
> from pandas import DataFrame
> from numpy.random import rand
> from sys import stdout
> df = DataFrame(rand(10,3), columns = list('abc'))
> df
> df.to_csv(stdout, sep="\t", header = True, cols=(1,2))
>
> I was completely unable to get ob-python working this morning, so I
> haven't tested it.  I'm using python3, build in python mode and elpy.
>
> In any case, the csv route might be better, as Pandas doesn't print
> the table if it's too big (try changing 10 to 1000 above).
>
> --
> Powered by magic pixies!
>
>

Re: [O] Break a line in org-mode

Søren Mikkelsen  writes:

> I usually have some #+LaTeX_HEADER: entries in my org-mode files where
> some of them are macros. These lines can be rather long so I have to
> type in #+LaTeX_HEADER: multiple times for breaking the line to a decent
> level.
>
> Is there a way of breaking a line when it is export options (or a
> regular comment in org-mode)?

No.  But maybe you could do 

#+LATEX_HEADER: \input{pre}
#+BEGIN_SRC LATEX :tangle pre.tex
\usepackage{mypackage}
#+END_SRC

Or you could make a new Org-Latex, see the variable org-latex-classes
if you have the same problem often.  

Some people entertained the idea of writing sty and/or cls files
recently on this list.  If you use the same macros all over perhaps
you should pack them as a sty or the very least as an external tex
file, I guess.

Alternatively, use the function string-rectangle.  In the following
example, place your mark at the first `|', click C-Space, move to the
second `|' click C-x r t LATEX_HEADER RET.

|\usepackage{pac1}
 \usepackage{pac1}
|\usepackage{pac1}.

Hope it helps. 

–Rasmus

-- 
This is the kind of tedious nonsense up with which I will not put

Re: [O] HTML export and info: links

2013/7/3 Bastien :
> Hi Sebastian,
>
> Sebastian Wiesner  writes:
>
>> Hardly the answer I hoped to get.
>
> Please let us know the answer you hoped to get, it will
> surely help us giving it :)

Uh, I hoped for a “easy, just toggle that customize setting” sort of
answer, not the “well, write it yourself” one ;)  More precisely I had
hoped for an easy way to plug Texinfo's HTML Xref Configuration [1]
into Org, which would have given proper HTML links for free.

I'll put Org mode migration of said manual on hold, for I currently
lack the time to write a proper link exporter myself.  I might get
back to it later, and look into the details of Texinfo's system, but I
can't promise anything.  I'll probably just stick to Texinfo, until
someone else does the dirty work ;)

Anyway, thank you for your answer, and please excuse the rather harsh
brevity of my previous answer.

Sebastian Wiesner

[1]: 
http://www.gnu.org/software/texinfo/manual/texinfo/html_node/HTML-Xref-Configuration.html#HTML-Xref-Configuration

Re: [O] [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.

2013-07-03 Thread Suvayu Ali

On Wed, Jul 03, 2013 at 02:22:40PM +0800, Feng Shu wrote:
> Suvayu Ali  writes:
> 
> > On Wed, Jul 03, 2013 at 07:09:35AM +0800, feng shu wrote:
> >> Customize  `org-latex-pdf-process isn't very convenient.
> >> Is it possible add a  feature like: #+LATEX_PDF_PROCESS:  latexmk
> >> or add  #OPTIONS:  ;latex_pdf_process  latexmk
> >
> > If you don't mind my chiming in, the standard way to customise Emacs
> > behaviour (across all modes, not just Org) is through
> > customize-variable.  Org cannot keep on introducing new keywords just
> > because of convenience.
> 
> I don't think so, Convenience is very important in most situation. we can
> introduce new keywords just for convenience!  #+LATEX_CLASS is a good example,
> If we don't want convencience.  we can just customize `org-latex-default-class

There is a big difference between the two variables.  Consider this:
org-latex-classes depends per document (most likely you wand different
documents for different things, hence maybe you also want different
classes), however you want to choose your LaTeX backend once (at most it
varies from project to project).  But again, if you use one build system
for a project you are most likely using the same build system in other
projects too.  The only difference I can see is when you have something
like make for projects, but simply LaTeX for a simple document/notes.
In that case, I would say Bastien's suggestion to use file local
variables is best suited.  At one point I used something like this
headline at the end of few Org files:

* COMMENT local setup   :ARCHIVE:

# Local Variables:
# org-latex-to-pdf-process: ("xelatex -interaction nonstopmode 
-output-directory %o %f" "xelatex -interaction nonstopmode -output-directory %o 
%f" "xelatex -interaction nonstopmode -output-directory %o %f")
# End:

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Org entries from tables

Hi Baptiste,

Baptiste  writes:

> Is there a way back (or the other way), that is, create org entries with 
> associated properties from a table. 

Not to my knowledge (and that of the Org FAQ, FWIW...)

Sorry!

-- 
 Bastien

Re: [O] org-id should require newcomment?

Hi Samuel,

Samuel Wales  writes:

> I require 'org-id, then store the link, then insert the link, and that
> is the backtrace I get.  Please tell me what else I can provide.  If
> nobody else can confirm it, I will require 'newcomment and work around
> the bug.  :)

I can't reproduce the bug, so I'd say let's stick with your own
solution for now and see if others can reproduce it.

-- 
 Bastien

Re: [O] Break a line in org-mode

Søren Mikkelsen  writes:

> I usually have some #+LaTeX_HEADER: entries in my org-mode files where
> some of them are macros. These lines can be rather long so I have to
> type in #+LaTeX_HEADER: multiple times for breaking the line to a decent
> level.
>
> Is there a way of breaking a line when it is export options (or a
> regular comment in org-mode)?
>
Wouldn't it be better to put the macros in a separate file (say
mymacros.sty) and use

#+LATEX_HEADER: \usepackage{mymacros}

? Less clutter in the org file and if the macros are more generally useful,
you can make it available, say by moving it to your personal texmf
directory (mine is at ~/.texmf-var/tex/latex but ymmv) and running texhash.
-- 
Nick

[O] Org entries from tables

2013-07-03 Thread Baptiste

Hi,

it is a nice feature to be able to export structured org entries as a table 
(through column view generated table).

Is there a way back (or the other way), that is, create org entries with 
associated properties from a table. 

Lot of people is using spreadsheet to organise its data, then it would be 
nice if their is an easy way to import this information formated as table 
into an org file (structured as org entries, which is better for in many 
ways).

Thanks.

--- Bat.

Re: [O] Incorrect sum of times in table

Bastien  writes:

> Both solutions work -- we don't need to fear other problems here,
> `org-table-sum' is pretty isolated, so I'd say "please go ahead!
> and fix this in maint.

I just applied the first solution, thanks!

-- 
 Bastien

Re: [O] advice needed: how do you guys sync org files between devices?

2013-07-03 Thread Samuel Loury

Hi,
Xebar Saram writes:

> I was wondering what you guys do for syncing org files between PC's, Os's,
> devices (android etc)..

There have been lot's of awesome solutions provided in this thread. Mine
is quite similar but I think it is worth describing it anyway.

I use git (a hand made script¹) to synchronize my personal files (not
only the org files) with a usb key. In fact, into the key, there is only
a encrypted version (via encfs) of a git bare repository. The data are
encrypted in case someone get access to my key.

I am now used to launch the script first thing in the morning, just
after plugging the key, and just before I unplug it.

The script has been in use for 2 years now and works quite well.

The problem with synchronizing with git is that the history might grow
out of control after some time. My workaround for the time being (it is
still being thought about) is to "cut" the repository. The idea is that
I only need most recent history, not the full one. My current
implementation² uses git clone --depth and results in a shallow
repository. This implementation really sucks because shallow
repositories are really limited. Any better idea would be welcome.

To get access to my org files from android, I tested two years ago
mobile org without success. Recently, I exported my errand tasks³ as a
ics file that I looked via a home made python script (thanks to sl4a⁴)
with a webview⁵ graphical interface. Nonetheless, I lost the python
script (CyanogenMod paaaa) and I am too lazy to rewrite it. Then I
guess I will give mobile org another chance.

Best

¹ https://github.com/Konubinix/Devel/blob/master/bin/konix_perso-sync.sh
² https://github.com/Konubinix/Devel/blob/master/bin/konix_perso-shorten.sh
³
https://github.com/Konubinix/Devel/blob/master/config/elfiles/config/after-loads/KONIX_AL-org.el#L1909
⁴ http://code.google.com/p/android-scripting/
⁵ http://code.google.com/p/android-scripting/wiki/ApiReference#webViewShow

--
Konubinix
GPG Key: 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A

signature.asc
Description: PGP signature

Re: [O] Date format when exporting to LaTeX?

Hi Nicolas and Richard,

Nicolas Goaziou  writes:

>>   * org-export-allow-bind-keywords must be true.  Adding it as a
>> file-local variable is not an acceptable solution in my
>> circumstance.
>>
>> I didn't have to set this variable when I was using 7.8.03 --
>> org-mode simply asked me (once) if it was OK to bind the
>> variables.  I miss that behavior.
>
> Unfortunately, re-implementing that behaviour is not trivial. The
> internals are just too different.

Yes, I remember we tried to re-implement this behavior.  Nicolas was
kind enough to provide patches per my request, as I think the previous
behavior is better.  If someone can help in this area, I think this
would be nice to fix this "regression".

2 cts,

-- 
 Bastien

Re: [O] [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.

Hi,

Suvayu Ali  writes:

> If you don't mind my chiming in, the standard way to customise Emacs
> behaviour (across all modes, not just Org) is through
> customize-variable.  Org cannot keep on introducing new keywords just
> because of convenience.
>
> In any case, this is also a security risk.  This starts an external
> process.  Allowing something like this means one can run an arbitrary
> command just by exporting a file.  I do not think that is wise at all.
> Exactly for this reason we have org-confirm-babel-evaluate defaulting to
> t.

I tend to agree.  Also, the user can setup `org-latex-pdf-process' as
a local variables, which are less error-prone when it comes to security.

-- 
 Bastien

Re: [O] Weekly clock reports for the previous or current week, with a per-day&project breakdown?

Hi Steinar,

Steinar Bang  writes:

>> l.stelm...@samsung.com (Łukasz Stelmach):
>
>> How about
>
>> + entering the agenda: C-c a 
>
>> + choosing week view: v w
>
> Hm... I get "invalid key" when pressing 'v' after doing 'C-c a'... am I
> missing some key binding or other setting?

`C-c a' should be followed by the key for the agenda view you want to
display.  `v w' does its job when an agenda view is already displayed.

HTH,

-- 
 Bastien

Re: [O] org-mode no longer picking up scheduled tasks when upgraded to 8.0.3

Hi Paul,

Paul Whipp  writes:

> A message "org-agenda-skip: Wrong type argument: stringp, nil"
> appears when I try to recalculate the agenda view.

Please start emacs with ~$ emacs --debug-init and send us the
backtrace.  Wild guess: delete ~/.emacs.d/elpa/org and reinstall
Org from ELPA and a fresh emacs session.

-- 
 Bastien

Re: [O] HTML export and info: links

Hi Sebastian,

Sebastian Wiesner  writes:

> Hardly the answer I hoped to get.

Please let us know the answer you hoped to get, it will
surely help us giving it :)

-- 
 Bastien

Re: [O] scrum with emacs org-mode

2013-07-03 Thread Samuel Loury

Hi,
thk...@koch.ro writes:

> has anybody some success stories to share how to use org-mode in scrum 
> projects?
Unfortunately, I won't be able to help with that. I am quite interested
by ideas as well.

> If you have some free software tools besides org-mode please tell us for 
> comparison!
I use Trac¹. It seems extensible enough to fit with most of the scrum
methodology. At least most of the scrum methodology I know
about. Besides, I use the EstimationToolsPlugin² to display burndown
charts.

Hope that helps.

¹ http://trac.edgewall.org/
² http://trac-hacks.org/wiki/EstimationToolsPlugin#BurndownChart

-- 
Konubinix
GPG Key: 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A


signature.asc
Description: PGP signature

Re: [O] Is org 8 going to added to Emacs git?