Re: [O] Two potentially useful functions for org-element

[Nicolas Goaziou]

Hello,

Thorsten Jolitz  writes:

> now that I understand the 'org-element API' a bit better, I think that
> the following two functions can be very useful for creating and
> modifying Org elements without the usual point movements, regexp
> searches and string operations in a buffer:

Element isn't really meant to provide tools to modify the buffer. It is
only a parser, i.e. buffer to parse tree transformation.

The reciprocal, i.e., modifying a parse tree in order to alter the
buffer may belong to another library. IIRC, this is the goal of
"org-sync" (from GSOC 2012). You may want to look into it.


Regards,

-- 
Nicolas Goaziou

Re: [O] (Maybe) enhance `org-element-src-block-interpreter'?

[Thorsten Jolitz]

Nicolas Goaziou  writes:

> Here goes the completeness...
>
> Nicolas Goaziou  writes:
>
>> For completeness, if you're working at the local level (i.e. with
>> `org-element-at-point'), available accessors are
>
> with `org-element-at-point' or `org-element-context'
>
>>   - `org-element-type'
>>   - `org-element-property'

Accessor `org-element-contents' is badly missed here ...

E.g. I can get locally the content of a src-block (its :value), but for
most other elements (e.g. paragraph) that is not true. OTOH I cannot
reuse a src-block value as the content of a (locally created) paragraph
because this element has no :value property I could set (and its
interpreter simply inserts 'content', which is unaccessible on local
level). 

I know this is *much* easier asked as provided:
can getters and setters for element-content be introduced at the local
level too? maybe via another property shared by all elements (:content
?). The content is probably not even parsed at local level, but anyway,
maybe there is some kind of trick to make it accessible without parsing
the whole buffer?

The only thing that comes to my mind is narrow the buffer to
element-at-point and then parse only this visible buffer part and return
its content. Valid idea?

>> When you're working at the global level (i.e. with
>> `org-element-parse-buffer'), you get another accessor,
>> `org-element-contents',
>
> In fact, new accessors are
>
>   - `org-element-contents'
>   - `org-element-map'
>
>> and some tools to modify the parse tree
>>
>>   - `org-element-put-property'
>>   - `org-element-adopt-element'
>>   - `org-element-insert-before'
>>   - `org-element-extract-element'
>>   - `org-element-set-element'


-- 
cheers,
Thorsten

Re: [O] Bug: org-in-src-block-p always returns nil [8.2.7b (8.2.7b-1-ga5beff-elpaplus @ /Users/ryan/.emacs.d/.cask/24.3.1/elpa/org-plus-contrib-20140714/)]

[Nicolas Goaziou]

Hello,

Ryan  writes:

> Actually, my implementation has a bug. org-element-at-point also
> returns the element if point is actually on one of the blank lines
> between that element and the next. So I've rewritten it to handle that
> case by computing the content end position and comparing point to
> that.

Thank you.  Here are a few notes about this implementation.

> (defun org-in-src-block-p (&optional inside)
>  "Whether point is in a code source block.
> When INSIDE is non-nil, don't consider we are within a src block
> when point is at #+BEGIN_SRC or #+END_SRC."
>  (save-match-data
>(let* ((elem (org-element-at-point))
>   (elem-type (car elem))

  (elem-type (org-element-type elem))

>   (props (cadr elem))
>   (end (plist-get props :end))

You don't need PROPS.

  (end (org-element-property :end elem))

>   (pb (plist-get props :post-blank))
>   (content-end
>(save-excursion
>  (goto-char end)
>  (forward-line (- pb))
>  (point)))

Using PB is incorrect.

  (contend-end
(save-excursion
  (goto-char end)
  (skip-chars-backward " \r\t\n")
  (line-beginning-position)))

>   (case-fold-search t))
>  (and
>   ;; Elem is a src block
>   (eq elem-type 'src-block)
>   ;; Make sure point is not on one of the blank lines after the
>   ;; element.
>   (< (point) content-end)
>   ;; If INSIDE is non-nil, then must not be at block delimiter
>   (not
>(and
> inside
> (save-excursion
>   (beginning-of-line)
>   (looking-at ".*#\\+\\(begin\\|end\\)_src"

Test is simply

  (and (eq elem-type 'src-block)
   (if inside
   (and (> (line-beginning-position) (org-element-property 
:post-affiliated elem))
(< (point) contents-end))
 (<= (line-beginning-position) contents-end)))

Note that this is not yet possible to re-implement `org-in-src-block-p'
with `org-element-at-point' as the former is used for fontification. It
would be sub-optimal to use it that way, since you can call once
`org-element-at-point' and fontify the element under point accordingly
to its type.


Regards,

-- 
Nicolas Goaziou

Re: [O] Two potentially useful functions for org-element

[Thorsten Jolitz]

Nicolas Goaziou  writes:

> Hello,
>
> Thorsten Jolitz  writes:
>
>> now that I understand the 'org-element API' a bit better, I think that
>> the following two functions can be very useful for creating and
>> modifying Org elements without the usual point movements, regexp
>> searches and string operations in a buffer:
>
> Element isn't really meant to provide tools to modify the buffer. It is
> only a parser, i.e. buffer to parse tree transformation.
>
> The reciprocal, i.e., modifying a parse tree in order to alter the
> buffer may belong to another library. IIRC, this is the goal of
> "org-sync" (from GSOC 2012). You may want to look into it.

Sorry, did not read this before writing my other recent post ...

I will have a look at org-sync, but even if Element isn't really meant
to provide tools to modify the buffer, it seems to be tremendously
useful in doing so? The most limiting aspect I found is the missing
access to an elements content (see my parallel post wrt to this topic). 

Otherwise 'rewiring' an elements internals looks like a huge
productivity booster compared to the usual buffer operations on the
textual representation. As long as the interpreter works as expected,
and it does!

-- 
cheers,
Thorsten

Re: [O] org-8 manual on Amazon!

[Rasmus]

John Kitchin  writes:

> I saw on twitter today the org mode 8 manual is available on Amazon
> today: http://www.amazon.com/dp/9881327709/. It looks like it covers Org 8.2.

I'm surprised by the change of publisher¹ and fact that there is no
reference to this edition on orgmode.org. . .

—Rasmus


Footnotes: 
¹   Though Network Theory Ltd isn't printing new manuals cf. 
http://www.network-theory.co.uk/about.html.

-- 
Send from my Emacs

Re: [O] #+OPTIONS: line kept in 'body-only' export to Org

[Nicolas Goaziou]

Hello,

Thorsten Jolitz  writes:

> doing:
>
> ,
> | 1. C-c C-e
> | 2. C-b ; body-only
> | 3. O O ; -> Org buffer
> `
>
> on this Org-buffer 
>
>
> ,
> | #+TITLE: Foo
> | #+DATE:  <1953-05-15 Fr> 
> | #+OPTIONS: toc:nil p:t author:nil pri:t prop:t tags:nil
> | 
> | * A
> | 
> | ** TODO B
> |:PROPERTIES:
> |:task_id:  xyz
> |:END:
> `
>
> I get
>
> ,
> | #+OPTIONS: toc:nil p:t author:nil pri:t prop:t tags:nil
> | 
> | * A
> | 
> | ** TODO B
> | :PROPERTIES:
> | :task_id:  xyz
> | :END:
> `
>
> Is that expected behaviour?
>
> For me thats a bit surprising, since it would still force me to
> post-process the results to really extract only the body of the Org
> buffer.

"Body" of the Org buffer is a bit fuzzy as OPTIONS could be anywhere,
including at the end of the buffer.

Anyway, I moved it into template, so it shouldn't appear anywore when
exporting body-only.

Thank your for suggesting this.


Regards,

-- 
Nicolas Goaziou

Re: [O] Org equivalent to \chapter*

[Rasmus]

Alan L Tyree  writes:

> On 07/08/14 20:05, Rasmus wrote:
 I'm sure this has been asked before, but I can't seem to find it. Is
 there an org markup that produces a starred latex heading?

 In a book, for example, I want the Preface to be at chapter level, but
 not included in the numbering. Same for HTML export, of course.
>>> You would probably need some sort of filter for this.  Most certainly
>>> you will be able to find implementations on this list.
>>>
>>> Here's something from my init file that works with LaTeX.  Other
>>> formats such as txt and html are harder since Org generates section
>>> numbers and the TOC.
>> Thanks for sharing this.  It will be useful for book authors.
>>
>> Do you think it is possible to write a general headline filter that
>> takes care of all the various LaTeX possibilities?
> I don't like *one* filter to rule them all.  Of course, if it's a
> collection of other function calls that is OK.  As your recent
> question showed execution order may matter,
> (e.g. with :ignoreheading:clearpage:).
>
> Of course it's possible to bundle a couple of filters generally useful
> for ox-latex and provide a "consistent" interface.  Alternatively, one
> could make a ox-latex+.el that provides a derived class with extra
> options. That's may be more work, and may be harder to hack.
>
> In fact Aaron started ox-extra.el, with the intention of providing
> "semi-official" extensions but Worg may be a better means of
> communication.
>
>> Right now Iʻm using tags to ignoreheading, clearpage, and newpage.
>> In addition to your nonum filter, Eric S. has a filter that gets rid
>> of a heading and promotes the content, which I havenʻt had occasion
>> to use, but also has its own tag.
> Yes, Eric has cool tree-based filter(s).  I want to study them more
> carefully.  Quite possibly, it's easier to provide elegant filters
> with trees.  For instance, you have direct access to the element
> representation.  In my filters I "hack" my way to this using
> text-properties.
>
>>   From the LaTeX authorʻs point of view, it would be great to have a set
>> of tags (and options) that "just work."
> Would you want this as a derived class or filters?  Perhaps it's
> easier to have a derived class with an alternative headline
> function. . .
>
>> Do you (and others) think the "tag and filter" approach can achieve
>> this?  Or, are there too many moving parts to make it feasible?
> Yes.
>
> The ox-koma-script interface is basically controlled via tags.  I
> think it's nice.
 Thanks for this useful overview and the pointers to good examples.

 Iʻve been slowly building a set of filters and links that work for me,
 but each new project differs a bit from the previous one and I have to
 fiddle with the Org mode setup.  Iʻm eager to get to the place Iʻm at
 with LaTeX, where I just jump in and start writing.

 Thanks again for your help.

 All the best,
 Tom

>>> Thanks to everyone who responded.
>>>
>>> Several of my books are out of print and I am converting them to ePub
>>> and to printed form. ePub is pretty smooth by exporting to HTML and
>>> then using Calibre. LaTeX is the obvious choice for print.
>> Have you seen this project:
>>
>>   https://github.com/rzoller/tex2ebook
>>
>> I haven't tried it myself, but the process seems similar to what you
>> are doing only that it uses hevea to convert from tex to html.
>>
>> —Rasmus
>>
>>
> Thanks, Rasmus. I'll have a look at this and report back. Org -> tex
> -> 
> HTML would at least solve the unnumbered heading problem (with the use
> of your filter).
>
> As an additional aside, note that Pandoc Markdown permits the use of a
> tag to produce an unnumbered heading when exporting to HTML and LaTeX.
>
> # Heading {.unnumbered}

Pandoc has something good going for it, though in this case Org tags
seem nicer.  I'm particularly envious of the native support of
citations via "@·" in Pandoc.

> I'm a very inexperienced lisp coder, but it seems to me that this
> should be incorporated into the basic exporters. The HTML exporter,
> for example, adds the numbering to each heading. In the loop that
> accomplishes that, it should be easy to ignore headings with a tag
> such as your :nonum:. Otherwise, it is necessary to write a filter
> that not only undoes the numbering for selected headlines, but
> essentially reproduces the numbering algorithms originally introduced
> in ox-html.

How about the TOC?  Should unnumbered headlines still appear there?
If yes the implementation may be as easy as you are suggesting here
and a patch could be written.

—Rasmus

-- 
Send from my Emacs

Re: [O] (Maybe) enhance `org-element-src-block-interpreter'?

[Nicolas Goaziou]

Thorsten Jolitz  writes:

> Accessor `org-element-contents' is badly missed here ...
>
> E.g. I can get locally the content of a src-block (its :value), but for
> most other elements (e.g. paragraph) that is not true. OTOH I cannot
> reuse a src-block value as the content of a (locally created) paragraph
> because this element has no :value property I could set (and its
> interpreter simply inserts 'content', which is unaccessible on local
> level). 
>
> I know this is *much* easier asked as provided:
> can getters and setters for element-content be introduced at the local
> level too? 

No, `org-element-at-point' focuses on the element at point, not elements
within. It would slow it down and make caching more complicated, for
little benefit.

> maybe via another property shared by all elements (:content
> ?). The content is probably not even parsed at local level, but anyway,
> maybe there is some kind of trick to make it accessible without parsing
> the whole buffer?
>
> The only thing that comes to my mind is narrow the buffer to
> element-at-point and then parse only this visible buffer part and return
> its content. Valid idea?

You're correct. Some cleanup is needed though (org-data + section
elements).


Regards,

-- 
Nicolas Goaziou

[O] Slight inconsistency wrt 'verse-block' properties?

[Thorsten Jolitz]

Hi List, 

while all other Org blocks that are elements but not greater-elements
have a :value property, verse-blocks don't. Is that an accidental
inconsistency?

-- 
cheers,
Thorsten

Re: [O] Slight inconsistency wrt 'verse-block' properties?

[Nicolas Goaziou]

Hello,

Thorsten Jolitz  writes:

> while all other Org blocks that are elements but not greater-elements
> have a :value property, verse-blocks don't. Is that an accidental
> inconsistency?

No, this is neither accidental nor an inconsistency.

Verse blocks are at the same level as paragraphs: they directly contain
objects and plain text. This is explained in the comments at the
beginning of "org-element.el".


Regards,

-- 
Nicolas Goaziou

[O] [patch, ox] Unnumbered headlines

[Rasmus]

Hi,

In a recent thread¹ Tom and Alan mention that authors sometimes need
unnumbered headlines, e.g. for prefaces.  This patch (tries to) add
this feature via the tag :nonumber: (customizable via Custom or
in-file).

I make two assumptions.  First, the tag is recursive, so if the parent
is not numbered the child is not numbered.  Secondly, I depart from
the LaTeX tradition of ignoring unnumbered headlines in the TOC
(except in the case of ox-latex.el where it depends on
org-latex-classes).  (See example below).

Needless to say such a feature needs to be discussed and I not sure
whether the greater Org community finds it useful or needless clutter.

In my opinion a :nonumber: tag is a natural continuation of :export:
and :noexport: and unlike :ignoreheading: the implementation is fairly
clean (or maybe I'm cheating myself here).  A reason for why to
include it is that it seems relatively easy to do *during* export, but
it's hard to consistently get it right on in both headlines and the
TOC via filters.

The patch is messing with ox.el, and thus I would appreciate a review
and potentially testing, in the case that it is agreed that such a
feature would be OK to add to ox.

It seems to work well with ox-latex.el, ox-ascii.el and ox-html.el.
It doesn't play well with ox-odt.el (headlines are still numbered).  I
will fix this as well as adding documentation if a consensus of the
worthwhileness of the patch can be reached.

Finally, here's an example output using ox-ascii

#+begin_src org
* a (not numbered):nonum:
** aa (not numbert)
* b (1)
** ba (not numbered)  :nonum:
*** baa (not numbered)
** bb (1.1)

#+end_src

#+RESULTS: (TOC only, but the rest is as expected)
a (not numbered)
.. aa (not numbert)
1 b (1)
.. ba (not numbered)
. baa (not numbered)
.. 1.1 bb (1.1)


Thanks,
Rasmus

Footnotes:
¹   http://permalink.gmane.org/gmane.emacs.orgmode/89515

--
Vote for proprietary math!
>From d38a728fef66af9df2a0b87e2126533961d87ecf Mon Sep 17 00:00:00 2001
From: Rasmus 
Date: Fri, 8 Aug 2014 14:53:01 +0200
Subject: [PATCH] ox.el: Support unnumbered headlines via tag.

* ox.el (org-export-options-alist): NO_NUMBER_TAGS new keyword.
(org-export-not-numbered-tags): New defcustom.
(org-export--collect-headline-numbering): Considers whether
headline is numbered.
(org-export-numbered-headline-p): Tests if headline is
to be numbered.
(org-export--recursive-tags): New function based.  Previouesly
part of `orge-export-get-tags'.
(org-export-get-tags): Ignoes NO_NUMBER_TAGS.
---
 lisp/ox.el | 60 +++-
 1 file changed, 43 insertions(+), 17 deletions(-)

diff --git a/lisp/ox.el b/lisp/ox.el
index d47c2e6..2fff14f 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -109,6 +109,7 @@
 (:language "LANGUAGE" nil org-export-default-language t)
 (:select-tags "SELECT_TAGS" nil org-export-select-tags split)
 (:exclude-tags "EXCLUDE_TAGS" nil org-export-exclude-tags split)
+(:no-number-tags "NO_NUMBER_TAGS" nil org-export-not-numbered-tags split)
 (:creator "CREATOR" nil org-export-creator-string)
 (:headline-levels nil "H" org-export-headline-levels)
 (:preserve-breaks nil "\\n" org-export-preserve-breaks)
@@ -448,6 +449,18 @@ e.g. \"*:nil\"."
   :group 'org-export-general
   :type 'boolean)
 
+
+(defcustom org-export-not-numbered-tags '("nonumber")
+  "Tags that exclude trees from obtaining numbers.
+
+All trees carrying any of these tags will be excluded from
+receiving a number.  This includes subtress.
+
+This option can also be set in files with the NO_NUMBER_TAGS
+keyword."
+  :group 'org-export-general
+  :type '(repeat (string :tag "Tag")))
+
 (defcustom org-export-exclude-tags '("noexport")
   "Tags that exclude a tree from export.
 
@@ -1993,7 +2006,8 @@ for a footnotes section."
   (let ((numbering (make-vector org-export-max-depth 0)))
 (org-element-map data 'headline
   (lambda (headline)
-	(unless (org-element-property :footnote-section-p headline)
+	(unless (or (org-element-property :footnote-section-p headline)
+		(not (org-export-numbered-headline-p headline info)))
 	  (let ((relative-level
 		 (1- (org-export-get-relative-level headline options
 	(cons
@@ -3785,9 +3799,12 @@ INFO is a plist holding contextual information."
 (defun org-export-numbered-headline-p (headline info)
   "Return a non-nil value if HEADLINE element should be numbered.
 INFO is a plist used as a communication channel."
-  (let ((sec-num (plist-get info :section-numbers))
+  (let ((tags (org-export--recursive-tags headline info))
+	(sec-num (plist-get info :section-numbers))
 	(level (org-export-get-relative-level headline info)))
-(if (wholenump sec-num) (<= level sec-num) sec-num)))
+(unless (loop for k in (plist-get info :no-number-tags)
+		  thereis (member k tags))
+  (if (wholenump sec-num) (<= level sec-num) sec-num
 
 (defun org-export-number-to

Re: [O] Problems with org-export: "byte-code: Invalid function: 0"

[Martin Beck]

Nick Dokos  gmail.com> writes:


> 
> This shows a problem evaluating a babel #+call or an inline source block
> somewhere between positions 1 and 3532 in the buffer. I suspect those
> call_skype thingies in your text are misinterpreted as babel calls
> somehow.
> 
> The thing is that org-babel-exp-non-block-elements does not exist any
> longer: it was taken out last December (from both master and maint).
> With recent org, I don't have a problem exporting your text, so my
> suggestion is: upgrade.
> 

Hi Nick,

thanks a lot for your help! I just installed org-mode 8.2.7c,
so in general, I think I should not have this problem.

Org-mode version 8.2.7c (8.2.7c-dist @ 
c:/Users/myaccount/Documents/mypath/org-mode/org_current/lisp/)

I launched emacs -q from cygwin terminal, then did org-version 
which said "N/A" and found that there seemed to be some org-files in 
/usr/share/emacs/site-lisp/org 
and some in  /usr/share/emacs/24.3/lisp/org

I removed both directories with their content, but I still have 
the problem during export.
I can only avoid it, if i change the text in the org file, e. g. by
removing the "c" from "call_", so that it just leaves "all_".
Then the export works without a problem.

So my question is: how can I track down the component (which should not be
in my system) that causes this problem?

Kind regards

Martin

Kind regards

Martin

Re: [O] left padding added each time a code block is edited

[Rasmus]

Hi Noah,

Noah Hoffman  writes:

> Noah Hoffman  writes:
>
>> Each time I edit a code block using =C-c '= (org-edit-special) and
>> then return to the org-mode buffer, two spaces are added to the left
>> margin of the code. For example,
>>
>> #+BEGIN_SRC python
>> print "hello"
>> #+END_SRC
>>
>> becomes
>>
>> #+BEGIN_SRC python
>>   print "hello"
>> #+END_SRC
>>
>> after one round-trip. This is particularly problematic for python code
>> blocks since leading whitespace is meaningful.

Have you experienced any bugs with respect to this? On my system Babel
will even run this code correctly:

#+BEGIN_SRC python
   if True:
   return( "hello!")
#+END_SRC

#+RESULTS:
: hello!


> 2. While this variable is very well documented, it isn't very
> discoverable via apropos or the html manual (at least, I wasn't able
> to discover it). Perhaps a reference can be added to this variable in
> the docstring for org-edit-src-code?

Patches are more than welcome!  There's a guide on Worg:

http://orgmode.org/worg/org-contribute.html

Cheers,
Rasmus

-- 
A page of history is worth a volume of logic

Re: [O] ox-reveal cannot export

[Yujie Wen]

Hi,

  I've switched org-reveal's code to follow ox-html's changes. Since
ox-html is changing, I've committed my codes to devel branch.

  Please pull the devel branch and try the fixes.

  Please let me if there are any issue. Thanks.

Regards,
Yujie


2014-08-07 20:22 GMT+08:00 Nicolas Goaziou :

> Hello,
>
> Nick Dokos  writes:
>
> > Tyler van Hensbergen  writes:
> >
> >> Robert Eckl  gmx.de> writes:
> >>
> >>> While exporting to reveal i get
> >>>
> >>>   Symbol's function definition is void:
> org-html-format-headline--wrap
> >>>
> >>> What i'm missing?
> >>
> >>
> >> That function's name was changed. I made a temporary fix on
> >> a forked branch on github and submitted a pull request
> >> today (warning I'm new to elisp so I may have missed
> >> something).
> >>
> >> https://github.com/yjwen/org-reveal/pull/69
> >>
> >> Not sure if it fixes everything but it is working for me know
> >> and I am no longer receiving that error.
> >>
> >
> > I haven't read things carefully, so take this with a large grain
> > of salt, but I think it should read:
> >
> >  ...
> >(full-text (org-html-headline headline contents info)))
> >  ...
> >
> > instead of passing a nil for contents.
>
> It should not use `org-html-headline' anyway, as there is no guarantee
> that this is the right function for headlines.
>
> To "export like html back-end", there are `org-export-data-with-backend'
> and `org-export-with-backend' functions, which doesn't require to know
> the original function.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
>

Re: [O] Cannot build documentation (release_8.3beta-155-g82b64d)

[Vicente Vera]

I think you're right. It seems TeX Live 2014 installed its own texinfo over
the one i got from the debian stable repository, but i'm not 100% sure.
Thanks for the help!


2014-08-05 19:37 GMT-04:00 Vicente Vera :

> Yes, i had an old makeinfo (4.13) that lives in the debian wheezy
> repository. Just now got the latest version and it worked. Didn't thought
> about this since some commits ago the documentation was built just fine
> with makeinfo 4.13.
>
> Thank you very much Nick & Achim.
>
>
> 2014-08-05 12:33 GMT-04:00 Vicente Vera :
>
> Hello. Started another "clean" cloned local repository to try building the
>> documentation again and the errors persist.
>> 'M-x org-version' gives: Org-mode version 8.3beta
>> (release_8.3beta-167-g003edd @ /usr/local/share/emacs/site-lisp/org/). I
>> installed everything except documentation.
>> Here's the output of 'make doc':
>>
>> make -C doc info
>> make[1]: Entering directory
>> `/home/vicente/descarga/org-master-git-20140804/org-mode/doc'
>> makeinfo --no-split org.texi -o org
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:16382:
>> Cross reference to nonexistent node `Using
>>
>>  multiple #+TBLFM lines' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:16073:
>> Cross reference to nonexistent node `External
>>  links' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:15543:
>> Cross reference to nonexistent node `Code evaluation
>>  security' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:15284:
>> Cross reference to nonexistent node `Property
>>  inheritance' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14501:
>> Cross reference to nonexistent node `Evaluating code
>>  blocks' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14219:
>> Cross reference to nonexistent node `Evaluating
>>
>>  code blocks' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14214:
>> Cross reference to nonexistent node `Code
>>
>>  evaluation security' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:14164:
>> Cross reference to nonexistent node `Library
>>
>>  of Babel' (perhaps incorrect sectioning?).
>>
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:13386:
>> Cross reference to nonexistent node `HTML
>>  export' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12927:
>> Cross reference to nonexistent node `Evaluating
>>
>>  code blocks' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12214:
>> Cross reference to nonexistent node `Column width and
>>  alignment' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:12095:
>> Cross reference to nonexistent node `Configuring a
>>
>>  document converter' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:11247:
>> Cross reference to nonexistent node `Radio
>>  targets' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10783:
>> Cross reference to nonexistent node `Export
>>  settings' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10499:
>> Cross reference to nonexistent node `In-buffer
>>  settings' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10344:
>> Cross reference to nonexistent node `Literal
>>  examples' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10173:
>> Cross reference to nonexistent node `Math formatting in
>>
>>  HTML export' (perhaps incorrect sectioning?).
>>
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:10013:
>> Cross reference to nonexistent node `Generating
>>
>>  an index' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:9918:
>> Cross reference to nonexistent node `Text
>>
>>  areas in HTML export' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:9846:
>> Cross reference to nonexistent node `Plain
>>  lists' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:9609:
>> Cross reference to nonexistent node `Document
>>  structure' (perhaps incorrect sectioning?).
>> /home/vicente/descarga/org-master-git-20140804/org-mode/doc//org.texi:8779:
>> Cross reference to nonexistent node `Filtering/limiting
>>
>>  agenda items' (perhaps i

Re: [O] Problems with org-export: "byte-code: Invalid function: 0"

[Nick Dokos]

Martin Beck  writes:

> Nick Dokos  gmail.com> writes:
>
>
>> 
>> This shows a problem evaluating a babel #+call or an inline source block
>> somewhere between positions 1 and 3532 in the buffer. I suspect those
>> call_skype thingies in your text are misinterpreted as babel calls
>> somehow.
>> 
>> The thing is that org-babel-exp-non-block-elements does not exist any
>> longer: it was taken out last December (from both master and maint).
>> With recent org, I don't have a problem exporting your text, so my
>> suggestion is: upgrade.
>> 
>
> Hi Nick,
>
> thanks a lot for your help! I just installed org-mode 8.2.7c,
> so in general, I think I should not have this problem.
>
> Org-mode version 8.2.7c (8.2.7c-dist @ 
> c:/Users/myaccount/Documents/mypath/org-mode/org_current/lisp/)
>
> I launched emacs -q from cygwin terminal, then did org-version 
> which said "N/A" and found that there seemed to be some org-files in 
> /usr/share/emacs/site-lisp/org 
> and some in  /usr/share/emacs/24.3/lisp/org
>
> I removed both directories with their content, but I still have 
> the problem during export.
> I can only avoid it, if i change the text in the org file, e. g. by
> removing the "c" from "call_", so that it just leaves "all_".
> Then the export works without a problem.
>
> So my question is: how can I track down the component (which should not be
> in my system) that causes this problem?
>

Yes, it seems that you are picking up an older version (probably the
one that got bundled with your emacs).

These things depend on how you install your org in general.

At the very least however, you *must* load an init file that sets your
load-path appropriately, when you do emacs -q (a so-called "minimal
.emacs" - search the list for some examples):

   emacs -q -l /path/to/minimal/.emacs
   
If you use ELPA to install org, you need to do (package-initialize) as
the very first thing in your init file (and iiuc, this takes care of
setting load-path appropriately). See Achim's posts in reply to Salome
on the ML (recently - within the past week). I don't use ELPA so I hope
somebody will chime in here if this is wrong. See also
http://orgmode.org/elpa.html for more information.

I also don't use Windows/cygwin, so there might be complications here
that I'm not aware of.

-- 
Nick

Re: [O] MobileOrg documentation?

[Jorge A. Alfaro-Murillo]

David Masterson  writes:

Not looking for complete org functionality in my phone -- just a 
reasonable ability to edit org outlines while I'm on the road. 


Well you can do that with MobileOrg... sort of. Once you edit and 
save a change, synchronize in your phone and then pull from your 
computer (org-mobile-pull). From (info (org) Pulling from 
MobileOrg):


"Some changes are applied directly and without user interaction. 
Examples are all changes to tags, TODO state, headline and body 
text that can be cleanly applied. Entries that have been flagged 
for further action will receive a tag ‘:FLAGGED:’, so that they 
can be easily found again. When there is a problem finding an 
entry or applying the change, the pointer entry will remain in the 
inbox and will be marked with an error message. You need to later 
resolve these issues by hand."


I do not understand when "cleanly applied" is the case, but my 
experience is that resolving "these issues by hand" is the most 
likely outcome. Even simple edits in the text of an entry in my 
phone generally result in errors of synchronization. Note that 
besides adding a comment of when the file was changed in the 
mobile, the local file does not change. Also you can see the 
differences in the files in the from-org-mobile.org file (or 
whatever you set the org-mobile-inbox-for-pull variable to).


Because of this limitation, I am better off just adding simple 
captures on my phone as remainders to do something in my computer, 
even adding information to a certain file. Then, when I 
synchronize in the phone and pull in my computer, the only file 
that changes is from-org-mobile.org, I open that buffer and use 
org-refile to send things to the right place.  Save all org 
buffers, org-mobile-push and repeat.


I you have access by ssh to a computer that is always on, then I 
recommend leaving an emacsclient open and using JuiceSSH of 
ConnectBot for editing your org files on the go.


Best,

--
Jorge.

Re: [O] left padding added each time a code block is edited

[Achim Gratz]

Noah Hoffman writes:
> This is particularly problematic for python code
> blocks since leading whitespace is meaningful.

The problem you imagine doesn't exist because the leading whitespace is
stripped before the code is sent to the interpreter.


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

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

[O] Tracking Current Org Version

[Kenneth Jacker]

Good day!

I am using 'git' to (I hope!) keep up to date on the latest Org distribution.

For me, there is a little confusion on just which version I'm using ...

I changed to the org-mode "git managed" directory, and entered:

$ make update

{ Do I need to do more?  I followed the above with
  "make" and "make install" ... necessary? }

After performing the above yesterday and then checking with "M-x org-version" 
shows:

   Org-mode version 8.3beta (release_8.3beta-175-g59cd25

Is that the latest?  No date is included ...


In addition, I receive announcements from  that shows things like:

   Latest: org-20140804.tar, 2014-Aug-04, 5.21MB

How does *that* differ/compare to what 'git' is downloading?

What is the "best" way to do this?  ;-)


Thanks for your comments,

-- 
Prof Kenneth H Jacker (ret)   k...@cs.appstate.edu
Computer Science Dept www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA

Re: [O] left padding added each time a code block is edited

[Noah Hoffman]

On Fri, Aug 8, 2014 at 6:47 AM, Rasmus  wrote:

> Have you experienced any bugs with respect to this? On my system Babel
> will even run this code correctly:
>
> #+BEGIN_SRC python
>if True:
>return( "hello!")
> #+END_SRC
>
> #+RESULTS:
> : hello!
>
>

To use a slightly different example:

#+BEGIN_SRC python
  import sys
  for i in range(10):
  print "foo"
#+END_SRC

-*- mode: compilation; default-directory: "~/Downloads/" -*-
Compilation started at Fri Aug  8 08:44:39

~/.emacs.d/bin/pychecker /Users/nhoffman/Downloads/broken.py
/Users/nhoffman/Downloads/broken.py:1:2: unexpected indent
  import sys
 ^
/Users/nhoffman/Downloads/broken.py:1:3: E111 indentation is not a
multiple of four
/Users/nhoffman/Downloads/broken.py:1:3: E113 unexpected indentation
/Users/nhoffman/Downloads/broken.py:2:3: E111 indentation is not a
multiple of four
/Users/nhoffman/Downloads/broken.py:3:7: E111 indentation is not a
multiple of four

Compilation finished at Fri Aug  8 08:44:40

Anything other than 4 spaces per indention level is flagged by python
style/syntax checkers that enforce pep8 (and yes, many flame wars have
been fought on the topic, but there are good reasons for enforcing
consistency). This is an issue when editing code blocks and in tangled
code. Maybe it's primarily an aesthetic thing, but I think that it's
best when possible to set the default to follow the standard
conventions for the language (my python mode certainly seems to think
so!).

>> 2. While this variable is very well documented, it isn't very
>> discoverable via apropos or the html manual (at least, I wasn't able
>> to discover it). Perhaps a reference can be added to this variable in
>> the docstring for org-edit-src-code?
>
> Patches are more than welcome!  There's a guide on Worg:
>
> http://orgmode.org/worg/org-contribute.html

I'll do so with pleasure! Thanks again.

Re: [O] proposal for improved integration of cdlatex

[Federico Beffa]

Do you think it is now a reasonable implementation? Would it be a
suitable tiny change to `org-mode'?

Regards,
Federico

> Thanks for the suggestion. Please find attached the improved patch.
>
> Regards,
> Federico
>
>
> On Wed, Jul 30, 2014 at 10:25 PM, Nicolas Goaziou
>  wrote:
>> Hello,
>>
>> Federico Beffa  writes:
>>
>>> +  (save-excursion
>>> +(org-mark-element)
>>> +(org-indent-region (point) (mark
>>
>> The function shouldn't set the mark. The following should be enough:
>>
>>
>>   (let ((element (org-element-at-point)))
>> (when element
>>   (org-indent-region (org-element-property :begin element)
>>  (org-element-property :end element
>>
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou

Re: [O] org-8 manual on Amazon!

[Carlos Sosa]

Rasmus  writes:

> John Kitchin  writes:
>
>> I saw on twitter today the org mode 8 manual is available on Amazon
>> today: http://www.amazon.com/dp/9881327709/. It looks like it covers Org 8.2.
>
> I'm surprised by the change of publisher¹ and fact that there is no
> reference to this edition on orgmode.org. . .
>
> —Rasmus
>
>
> Footnotes: 
> ¹   Though Network Theory Ltd isn't printing new manuals cf. 
> http://www.network-theory.co.uk/about.html.

So if it's not referenced by orgmode.org, it means it was community
made?

- Carlos 

Re: [O] MobileOrg documentation?

[David Masterson]

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:

> David Masterson  writes:
>
>> Not looking for complete org functionality in my phone -- just a
>> reasonable ability to edit org outlines while I'm on the road. 
>
> Well you can do that with MobileOrg... sort of. Once you edit and save
> a change, synchronize in your phone and then pull from your computer
> (org-mobile-pull). From (info (org) Pulling from MobileOrg):
>
> "Some changes are applied directly and without user
> interaction. Examples are all changes to tags, TODO state, headline
> and body text that can be cleanly applied. Entries that have been
> flagged for further action will receive a tag ‘:FLAGGED:’, so that
> they can be easily found again. When there is a problem finding an
> entry or applying the change, the pointer entry will remain in the
> inbox and will be marked with an error message. You need to later
> resolve these issues by hand."
>
> I do not understand when "cleanly applied" is the case, but my
> experience is that resolving "these issues by hand" is the most likely
> outcome. Even simple edits in the text of an entry in my phone
> generally result in errors of synchronization. Note that besides
> adding a comment of when the file was changed in the mobile, the local
> file does not change. Also you can see the differences in the files in
> the from-org-mobile.org file (or whatever you set the
> org-mobile-inbox-for-pull variable to).
>
> Because of this limitation, I am better off just adding simple
> captures on my phone as remainders to do something in my computer,
> even adding information to a certain file. Then, when I synchronize in
> the phone and pull in my computer, the only file that changes is
> from-org-mobile.org, I open that buffer and use org-refile to send
> things to the right place.  Save all org buffers, org-mobile-push and
> repeat.
>
> I you have access by ssh to a computer that is always on, then I
> recommend leaving an emacsclient open and using JuiceSSH of ConnectBot
> for editing your org files on the go.

Hmmm.  Simple question (I think).  Can you edit outlines (at least
somewhat) from MobileOrg?  For instance, can you add outline headers to
your Org outline in MobileOrg?  Or is MobileOrg only useful for viewing
Org outlines and capturing items to add to your outlines later?

-- 
David Masterson
Programmer At Large

Re: [O] org-8 manual on Amazon!

[Subhan Michael Tindall]

This is almost certainly a literally a printed version of the already available 
open source org manual. 
Nothing to see here, move along.


-Original Message-
From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org 
[mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On Behalf Of 
Carlos Sosa
Sent: Friday, August 08, 2014 10:52 AM
To: emacs-orgmode@gnu.org
Subject: Re: [O] org-8 manual on Amazon!

Rasmus  writes:

> John Kitchin  writes:
>
>> I saw on twitter today the org mode 8 manual is available on Amazon
>> today: http://www.amazon.com/dp/9881327709/. It looks like it covers Org 8.2.
>
> I'm surprised by the change of publisher¹ and fact that there is no 
> reference to this edition on orgmode.org. . .
>
> —Rasmus
>
>
> Footnotes: 
> ¹   Though Network Theory Ltd isn't printing new manuals cf. 
> http://www.network-theory.co.uk/about.html.

So if it's not referenced by orgmode.org, it means it was community made?

- Carlos 



This message is intended for the sole use of the individual and entity to which 
it is addressed and may contain information that is privileged, confidential 
and exempt from disclosure under applicable law. If you are not the intended 
addressee, nor authorized to receive for the intended addressee, you are hereby 
notified that you may not use, copy, disclose or distribute to anyone the 
message or any information contained in the message. If you have received this 
message in error, please immediately advise the sender by reply email and 
delete the message.  Thank you.

[O] Control of agenda window size

[Subhan Michael Tindall]

I've been working with some custom agenda commands, and I'm noticing that there 
doesn't seem to be any way to control the size of the split window used for 
display (sometimes it is 50%, sometimes much more.  Likewise the window that is 
opened to display an item from e.g. a clock table when tab is it (again, some 
agendas I'd like this to be a full-frame window)

Is there a configuration variable I can use to control these behaviors? I can't 
seem to find one, nor can I find any hooks that might be run after an agenda 
buffer is displayed.

Am I wasting my time here?
Thanks!
Subhan


Subhan Michael Tindall
Program Analyst - FamilyCare Health Plans
825 NE Multnomah St, Suite 1400; Portland OR 97232
Direct: 503-471-3127
Fax:  503-471-3177
Email:  subh...@familycareinc.org
[Email-Signature-Logos June 20143]


This message is intended for the sole use of the individual and entity to which 
it is addressed and may contain information that is privileged, confidential 
and exempt from disclosure under applicable law. If you are not the intended 
addressee, nor authorized to receive for the intended addressee, you are hereby 
notified that you may not use, copy, disclose or distribute to anyone the 
message or any information contained in the message. If you have received this 
message in error, please immediately advise the sender by reply email and 
delete the message.  Thank you.

Re: [O] MobileOrg documentation?

[Jorge A. Alfaro-Murillo]

David Masterson writes: 

Hmmm.  Simple question (I think).  Can you edit outlines (at 
least somewhat) from MobileOrg?  For instance, can you add 
outline headers to your Org outline in MobileOrg?  Or is 
MobileOrg only useful for viewing Org outlines and capturing 
items to add to your outlines later? 


Yes.

In MobileOrg of your phone: Settings, Synchronization, check 
Advanced capture. Click over any headline and then use the capture 
button (the circle with a plus inside). Write the new headline, 
save, and synchronize.


Afterwards run org-mobile-pull from your computer, the changes should be
there. At least it works for me under Android.

Best,

--
Jorge.

Re: [O] MobileOrg documentation?

[Ken Mankoff]

Advance Capture is Android only, not on my iPhone version. On iPhone, you
cannot add sub-headings. You can type it out as much as you want with "**"
and "***", but you'll need to do some editing on the desktop side. Those
modifications could be made automagically when the desktop auto-detects
that updates have been pushed from the phone...

  -k.


On Fri, Aug 8, 2014 at 2:28 PM, Jorge A. Alfaro-Murillo <
jorge.alfaro-muri...@yale.edu> wrote:

> David Masterson writes:
>
>> Hmmm.  Simple question (I think).  Can you edit outlines (at least
>> somewhat) from MobileOrg?  For instance, can you add outline headers to
>> your Org outline in MobileOrg?  Or is MobileOrg only useful for viewing Org
>> outlines and capturing items to add to your outlines later?
>>
>
> Yes.
>
> In MobileOrg of your phone: Settings, Synchronization, check Advanced
> capture. Click over any headline and then use the capture button (the
> circle with a plus inside). Write the new headline, save, and synchronize.
>
> Afterwards run org-mobile-pull from your computer, the changes should be
> there. At least it works for me under Android.
>
> Best,
>
> --
> Jorge.
>
>
>

[O] org-capture-after-finalize-hook not covered by documentation

[Marcin Antczak]

As in topic.

org-capture-before-finalize-hook is mentioned, after-finalize is not.


http://orgmode.org/tmp/worg/org-configs/org-hooks.html


From ChangeLog:

2010-12-11  Allen S. Rout(tiny change)

* org-capture.el (org-capture-after-finalize-hook): New hook.
(org-capture-finalize): Run the new hook.



Regards,
Marcin

Re: [O] MobileOrg documentation?

[Jorge A. Alfaro-Murillo]

Ken Mankoff writes: 


On iPhone, you cannot add sub-headings.


Another good reason to ditch your iPhone and buy a Nexus =)

Even when the Android and iPhone applications are different, the 
good thing is that the org side (org-mobile.el) is not specific 
for the iPhone or Android (or any external application that uses 
the same conventions).


Perhaps that is why the manual seems to new users so vague, they 
expect that it will explain how to go over the phone installation 
as well. But that is not the job of the org part, but that of the 
phone application IMO.


--
Jorge.

[O] [PATCH] Add support for :dbhost, :dbuser and :database parameters for poastgresql in ob-sql.el

[Steven Rémot]

Hi,

I did some changes to support :dbname, :dbhost and :database in SQL code 
blocks when using postgresql engine.


Even if it was possible to specify this information using :cmdline 
parameter, I thought it was a bit cleaner to be able to provide this 
information in a way independent from the command line.


I will gladly accept any remark / comment on this patch.

Regards,
Steven Rémot
>From 6ad99759a16c8b6f9decfb8ea90c84e7a1c18fdc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Steven=20R=C3=A9mot?= 
Date: Fri, 8 Aug 2014 21:49:44 +0200
Subject: [PATCH] ob-sql.el: Enhance postgresql support

* lisp/ob-sql.el: Add support for :dbhost, :dbuser and :database
  parameters in sql code blocks for postgresql engine.

Before this patch, it was necessary to use :cmdline parameter to
specify host, user and database different the the default ones.  Now,
this can be done using parameters that are independents of the engine
used.

This is not trivial (and not recommended) to pass password as a
command line argument to psql, so :dbpassword is not supported.
---
 lisp/ob-sql.el | 12 +++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/lisp/ob-sql.el b/lisp/ob-sql.el
index 7b85df8..9fe9da2 100644
--- a/lisp/ob-sql.el
+++ b/lisp/ob-sql.el
@@ -87,6 +87,15 @@
 	   (when password (concat "-p" password))
 	   (when database (concat "-D" database))
 
+(defun dbstring-postgresql (host user database)
+  "Make PostgreSQL command line ards for database connection.
+Pass nil to omit that arg."
+  (combine-and-quote-strings
+   (remq nil
+	 (list (when host (concat "-h" host))
+	   (when user (concat "-U" user))
+	   (when database (concat "-d" database))
+
 (defun org-babel-execute:sql (body params)
   "Execute a block of Sql code with Babel.
 This function is called by `org-babel-execute-src-block'."
@@ -123,8 +132,9 @@ This function is called by `org-babel-execute-src-block'."
 (org-babel-process-file-name in-file)
 (org-babel-process-file-name out-file)))
 		('postgresql (format
-  "psql --set=\"ON_ERROR_STOP=1\" %s -A -P footer=off -F \"\t\"  -f %s -o %s %s"
+  "psql --set=\"ON_ERROR_STOP=1\" %s -A -P footer=off -F \"\t\"  %s -f %s -o %s %s"
   (if colnames-p "" "-t")
+  (dbstring-postgresql dbhost dbuser database)
   (org-babel-process-file-name in-file)
   (org-babel-process-file-name out-file)
   (or cmdline "")))
-- 
1.9.1

Re: [O] MobileOrg documentation?

[David Masterson]

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:

> David Masterson writes: 
>
>> Hmmm.  Simple question (I think).  Can you edit outlines (at least
>> somewhat) from MobileOrg?  For instance, can you add outline headers
>> to your Org outline in MobileOrg?  Or is MobileOrg only useful for
>> viewing Org outlines and capturing items to add to your outlines
>> later? 
>
> Yes.
>
> In MobileOrg of your phone: Settings, Synchronization, check Advanced
> capture. Click over any headline and then use the capture button (the
> circle with a plus inside). Write the new headline, save, and
> synchronize.

Hmmm.  Don't see this in MobileOrg for iOS.  I do see Settings,
Settings, AutoCapture Mode, but not Advanced Capture.  Is this an
example of two different code bases?  This is MobileOrg v1.6.1.

> Afterwards run org-mobile-pull from your computer, the changes should be
> there. At least it works for me under Android.

Yes, I expected that, once you made a change in MobileOrg, you have to
cycle over to Emacs Org via org-mobile-pu(sh|ll).

-- 
David Masterson
Programmer At Large

Re: [O] MobileOrg documentation?

[Ken Mankoff]

Some code to auto-update Org when Mobile Org pushes:

http://kenmankoff.com/2012/08/17/emacs-org-mode-and-mobileorg-auto-sync/

  -k.


On Fri, Aug 8, 2014 at 5:15 PM, David Masterson 
wrote:

> jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
>
> > David Masterson writes:
> >
> >> Hmmm.  Simple question (I think).  Can you edit outlines (at least
> >> somewhat) from MobileOrg?  For instance, can you add outline headers
> >> to your Org outline in MobileOrg?  Or is MobileOrg only useful for
> >> viewing Org outlines and capturing items to add to your outlines
> >> later?
> >
> > Yes.
> >
> > In MobileOrg of your phone: Settings, Synchronization, check Advanced
> > capture. Click over any headline and then use the capture button (the
> > circle with a plus inside). Write the new headline, save, and
> > synchronize.
>
> Hmmm.  Don't see this in MobileOrg for iOS.  I do see Settings,
> Settings, AutoCapture Mode, but not Advanced Capture.  Is this an
> example of two different code bases?  This is MobileOrg v1.6.1.
>
> > Afterwards run org-mobile-pull from your computer, the changes should be
> > there. At least it works for me under Android.
>
> Yes, I expected that, once you made a change in MobileOrg, you have to
> cycle over to Emacs Org via org-mobile-pu(sh|ll).
>
> --
> David Masterson
> Programmer At Large
>
>
>

Re: [O] MobileOrg documentation?

[David Masterson]

jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:

> Ken Mankoff writes: 
>
>> On iPhone, you cannot add sub-headings.
>
> Another good reason to ditch your iPhone and buy a Nexus =)
>
> Even when the Android and iPhone applications are different, the good
> thing is that the org side (org-mobile.el) is not specific for the
> iPhone or Android (or any external application that uses the same
> conventions).
>
> Perhaps that is why the manual seems to new users so vague, they
> expect that it will explain how to go over the phone installation as
> well. But that is not the job of the org part, but that of the phone
> application IMO.

But, the Org part should, at least, point to the documentation of the
phone part.  At the very least, provide a place for the phone part(s) to
be documented on Worg and point there...

-- 
David Masterson
Programmer At Large

Re: [O] MobileOrg documentation?

[Nick Dokos]

David Masterson  writes:

> jorge.alfaro-muri...@yale.edu (Jorge A. Alfaro-Murillo) writes:
>
>> Ken Mankoff writes: 
>>
>>> On iPhone, you cannot add sub-headings.
>>
>> Another good reason to ditch your iPhone and buy a Nexus =)
>>
>> Even when the Android and iPhone applications are different, the good
>> thing is that the org side (org-mobile.el) is not specific for the
>> iPhone or Android (or any external application that uses the same
>> conventions).
>>
>> Perhaps that is why the manual seems to new users so vague, they
>> expect that it will explain how to go over the phone installation as
>> well. But that is not the job of the org part, but that of the phone
>> application IMO.
>
> But, the Org part should, at least, point to the documentation of the
> phone part.  At the very least, provide a place for the phone part(s) to
> be documented on Worg and point there...

It does. There is an iOS pointer and an Android pointer in

(info "(org) Appendix B MobileOrg")

For iOS, it says:

,
| The iOS implementation (https://github.com/MobileOrg/) for the
| iPhone/iPod Touch/iPad series of devices, was started by Richard
| Moreland and is now in the hands Sean Escriva.
`

And if you follow that link, you'll get to another link

   http://mobileorg.ncogni.to/

which has a "Documentation" button - I didn't push the button but I hope
there is something substantive behind it.

-- 
Nick

Re: [O] [patch, ox] Unnumbered headlines

[Alan L Tyree]

On 08/08/14 23:39, Rasmus wrote:

Hi,

In a recent thread¹ Tom and Alan mention that authors sometimes need
unnumbered headlines, e.g. for prefaces.  This patch (tries to) add
this feature via the tag :nonumber: (customizable via Custom or
in-file).

I make two assumptions.  First, the tag is recursive, so if the parent
is not numbered the child is not numbered.  Secondly, I depart from
the LaTeX tradition of ignoring unnumbered headlines in the TOC
(except in the case of ox-latex.el where it depends on
org-latex-classes).  (See example below).

Needless to say such a feature needs to be discussed and I not sure
whether the greater Org community finds it useful or needless clutter.

In my opinion a :nonumber: tag is a natural continuation of :export:
and :noexport: and unlike :ignoreheading: the implementation is fairly
clean (or maybe I'm cheating myself here).  A reason for why to
include it is that it seems relatively easy to do *during* export, but
it's hard to consistently get it right on in both headlines and the
TOC via filters.

The patch is messing with ox.el, and thus I would appreciate a review
and potentially testing, in the case that it is agreed that such a
feature would be OK to add to ox.

It seems to work well with ox-latex.el, ox-ascii.el and ox-html.el.
It doesn't play well with ox-odt.el (headlines are still numbered).  I
will fix this as well as adding documentation if a consensus of the
worthwhileness of the patch can be reached.

Finally, here's an example output using ox-ascii

#+begin_src org
 * a (not numbered)   :nonum:
 ** aa (not numbert)
 * b (1)
 ** ba (not numbered) :nonum:
 *** baa (not numbered)
 ** bb (1.1)

#+end_src

#+RESULTS: (TOC only, but the rest is as expected)
 a (not numbered)
 .. aa (not numbert)
 1 b (1)
 .. ba (not numbered)
 . baa (not numbered)
 .. 1.1 bb (1.1)


Thanks,
Rasmus

Footnotes:
¹   http://permalink.gmane.org/gmane.emacs.orgmode/89515

--
Vote for proprietary math!

Rasmus, you're my hero!

Regarding the two assumptions:

- Recursive tags: I think this is correct. I don't think it matters too 
much for my use case since things like the Preface will ordinarily be 
top level headlines and unlikely to have children. If there are child 
headlines, then I don't see why numbering would be required.


- Table of contents: I'm sure this is correct. I always ended up adding 
to the TOC when using LaTeX anyway.


The frontmatter of a book has two distinct types of pages:
  - title pages, copyright pages and so forth. If these pages are 
headlined at all, then the :ignore: tag and Eric's filter takes care of 
them;


  - things like the Preface, Forward and (in my case) Table of Statutes 
and Table of cases. This type wants to be referenced in the TOC but they 
definitely do not want to be sequentially numbered as chapters.


The Wikipedia entry on Book Design lists 12 types of frontmatter pages: 
http://en.wikipedia.org/wiki/Book_design. It's easy to see which ones 
fit into which category.


I think this facility will *greatly* enhance org-mode for book 
authors/publishers. It will certainly make the conversion to ePub go 
more smoothly.


Cheers,
Alan


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

[O] MobileOrg iOS status?? (Sean?)

[David Masterson]

It appears that MobileOrg hasn't really moved in over a year.  In fact,
the Changelog for MobileOrg stops at 1.5.1 where I am using 1.6.1, so it
seems that things really are not up-to-date.  Looking in GitHub (which
I'm not an expert on), it appears that development has split along OS
lines.  What is the status of MobileOrg in general and, in particular,
MobileOrg?  (Sean??)
-- 
David Masterson
Programmer At Large

Re: [O] [PATCH] Add support for :dbhost, :dbuser and :database parameters for poastgresql in ob-sql.el

[Thomas S. Dye]

Aloha Steven,

Steven Rémot  writes:

> Hi,
>
> I did some changes to support :dbname, :dbhost and :database in SQL
> code blocks when using postgresql engine.
>
> Even if it was possible to specify this information using :cmdline
> parameter, I thought it was a bit cleaner to be able to provide this
> information in a way independent from the command line.
>
> I will gladly accept any remark / comment on this patch.
>
> Regards,
> Steven Rémot

I'm not certain who is maintaining ob-sql.el, so I'm not replying in any
directly useful way.  However, this patch looks straightforward and
good to me.

Have you signed FSF papers?  If so, the maintainer can accept (or
reject) your patch.  If not, then you'll need to identify it as a tiny
change (see http://orgmode.org/worg/org-contribute.html).

Thanks for this contribution to Org mode.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] [patch, ox] Unnumbered headlines - early test

[Alan L Tyree]

I have a book length MS that I tested the patch on.

* Copyright page   :nonumber:

* Preface:nonumber:

* Law relating to sale of goods

... etc

Export looked good and as expected, that is, no numbers on the first two 
headlines and the third headline numbered 1. as it should be. Table of 
contents was as expected. LaTeX and ascii exports also looked great.


However, running "tidy -m sog.html" on the resulting file threw up the 
following warnings:


line 222 column 1 - Warning:  anchor "outline-container-sec-" 
already defined

line 223 column 1 - Warning:  anchor "sec-" already defined
line 224 column 1 - Warning:  anchor "text-" already defined
Info: Doctype given is "-//W3C//DTD XHTML 1.0 Strict//EN"
Info: Document content looks like XHTML 1.0 Strict
3 warnings, 0 errors were found!

Line 222, 223 and 224 relate to the Preface heading. The offending items 
were, of course, copies of the corresponding items in Copyright page. To 
avoid these, I think you need to give unique id and sec markers to the 
unnumbered headlines.


It matters because the resulting ePub will not validate unless the html 
passes the "tidy test".


Cheers,
Alan



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

[O] Some thoughts on MobileOrg and its development ....

[Alexis]

Hi all,

In light of recent discussions about 'MobileOrg' - which seemingly
actually constitutes two distinct projects for two different platforms -
together with the apparent relative lack of activity of both projects,
despite demand for them, i can't help but wonder if the 'MobileOrg'
endeavour needs a reboot.

More specifically, it seems to me that rebuilding MobileOrg as a single
project on top of Apache Cordova:

https://cordova.apache.org/

might be a way forward, for several reasons:

* It would help ensure that basically the same set of functionality is
  available across platforms, modulo specific limitations/issues with
  specific platforms. And when people add or modify core functionality,
  that functionality would more easily become available to people across
  platforms, rather than the functionality being initially implemented
  on platform X, and people on platform Y having to wait for it to be
  implemented in its entirety.

* Overall, only one lot of end-user documentation would need to be
  maintained.

* It would enable MobileOrg to be made available for mobile platforms
  other than Android and iOS, such as Windows Phone and Blackberry.

* The number of people available to assist with development might well
  be greater, due to the core development environment involving HTML,
  CSS and JavaScript. Barriers to entry for both regular and occasional
  committers would be much lower.

i'm aware that Cordova has various limitations,
including-but-not-limited-to the lack of native 'feel' of Cordova-based
applications. However, i feel that the above advantages, combined with
the my notion that Emacs users are probably less concerned with a
perfectly slick UI than with having access to functionality they
need/want, probably outweighs such limitations.

Unfortunately, due to other existing commitments, i wouldn't be able to
take point on such a reboot. But i'd definitely be willing and able to
help out!  Particularly in the area of contact management and syncing,
of course. :-)

Thoughts/comments/criticisms?


Alexis.

[O] Source Code Header Not Honored in Exportation?

[Aric Gregson]

Hello,

I am trying to export via org-odt and do not want some of the R source
run during export. For these blocks I have the following:

#+begin_src R :eval no

However, it seems that they are still being evaluated, despite having
refreshed the local set-up. Is this not the correct header to tell org
not to evaluate the code block?

Thanks, Aric

-- 
~O
/\_,
###-\  |_
(*) / (*)

Re: [O] Source Code Header Not Honored in Exportation?

[Aric Gregson]

Aric Gregson  writes:

> I am trying to export via org-odt and do not want some of the R source
> run during export. For these blocks I have the following:
>
> #+begin_src R :eval no
>
> However, it seems that they are still being evaluated, despite having
> refreshed the local set-up. Is this not the correct header to tell org
> not to evaluate the code block?

It seems that the file was actually not getting refreshed. Closing and
opening the file caused the headers to be noticed and the evaluation was
not carried out, just as desired. 

Thanks, Aric

Re: [O] Some thoughts on MobileOrg and its development ....

[Xebar Saram]

Would love to see a reboot and further development on org-mobile. I am not
a developer myself but would love to help out with testing , writing
documentation etc

best

Z


On Sat, Aug 9, 2014 at 3:56 AM, Alexis  wrote:

>
> Hi all,
>
> In light of recent discussions about 'MobileOrg' - which seemingly
> actually constitutes two distinct projects for two different platforms -
> together with the apparent relative lack of activity of both projects,
> despite demand for them, i can't help but wonder if the 'MobileOrg'
> endeavour needs a reboot.
>
> More specifically, it seems to me that rebuilding MobileOrg as a single
> project on top of Apache Cordova:
>
> https://cordova.apache.org/
>
> might be a way forward, for several reasons:
>
> * It would help ensure that basically the same set of functionality is
>   available across platforms, modulo specific limitations/issues with
>   specific platforms. And when people add or modify core functionality,
>   that functionality would more easily become available to people across
>   platforms, rather than the functionality being initially implemented
>   on platform X, and people on platform Y having to wait for it to be
>   implemented in its entirety.
>
> * Overall, only one lot of end-user documentation would need to be
>   maintained.
>
> * It would enable MobileOrg to be made available for mobile platforms
>   other than Android and iOS, such as Windows Phone and Blackberry.
>
> * The number of people available to assist with development might well
>   be greater, due to the core development environment involving HTML,
>   CSS and JavaScript. Barriers to entry for both regular and occasional
>   committers would be much lower.
>
> i'm aware that Cordova has various limitations,
> including-but-not-limited-to the lack of native 'feel' of Cordova-based
> applications. However, i feel that the above advantages, combined with
> the my notion that Emacs users are probably less concerned with a
> perfectly slick UI than with having access to functionality they
> need/want, probably outweighs such limitations.
>
> Unfortunately, due to other existing commitments, i wouldn't be able to
> take point on such a reboot. But i'd definitely be willing and able to
> help out!  Particularly in the area of contact management and syncing,
> of course. :-)
>
> Thoughts/comments/criticisms?
>
>
> Alexis.
>
>

Re: [O] Some thoughts on MobileOrg and its development ....

[David Masterson]

Alexis  writes:

> Hi all,
>
> In light of recent discussions about 'MobileOrg' - which seemingly
> actually constitutes two distinct projects for two different platforms -
> together with the apparent relative lack of activity of both projects,
> despite demand for them, i can't help but wonder if the 'MobileOrg'
> endeavour needs a reboot.
>
> More specifically, it seems to me that rebuilding MobileOrg as a single
> project on top of Apache Cordova:
>
> https://cordova.apache.org/
>
> might be a way forward, for several reasons:
>
> * It would help ensure that basically the same set of functionality is
>   available across platforms, modulo specific limitations/issues with
>   specific platforms. And when people add or modify core functionality,
>   that functionality would more easily become available to people across
>   platforms, rather than the functionality being initially implemented
>   on platform X, and people on platform Y having to wait for it to be
>   implemented in its entirety.
>
> * Overall, only one lot of end-user documentation would need to be
>   maintained.
>
> * It would enable MobileOrg to be made available for mobile platforms
>   other than Android and iOS, such as Windows Phone and Blackberry.
>
> * The number of people available to assist with development might well
>   be greater, due to the core development environment involving HTML,
>   CSS and JavaScript. Barriers to entry for both regular and occasional
>   committers would be much lower.
>
> i'm aware that Cordova has various limitations,
> including-but-not-limited-to the lack of native 'feel' of Cordova-based
> applications. However, i feel that the above advantages, combined with
> the my notion that Emacs users are probably less concerned with a
> perfectly slick UI than with having access to functionality they
> need/want, probably outweighs such limitations.
>
> Unfortunately, due to other existing commitments, i wouldn't be able to
> take point on such a reboot. But i'd definitely be willing and able to
> help out!  Particularly in the area of contact management and syncing,
> of course. :-)
>
> Thoughts/comments/criticisms?

Sounds interesting.  Unfortunately, I haven't done this type of
development in many years.  At this moment, I'm not even sure how to go
about setting up Cordova and its prerequisites.  Otherwise, I might be
interested in taking the lead on this.

Ultimately, someone will have to pull apart the current
immplementation(s) of MobileOrg in order to redevelop it in Cordova.
Anyone got a handle on that?

-- 
David Masterson
Programmer At Large

Re: [O] Tracking Current Org Version

[Suvayu Ali]

On Fri, Aug 8, 2014 at 5:39 PM, Kenneth Jacker  wrote:
>
> What is the "best" way to do this?  ;-)

This should help you

http://orgmode.org/worg/org-faq.html#Keeping-current

-- 
Suvayu

Open source is the future. It sets us free.