Re: [O] [BUG] in export to odt -

[Rasmus]

Rainer M Krug  writes:

> The odt is attached for reference.

Please also provide an odt document with the expected, working result.
(I could not produce such a document in LO within 20s, but perhaps it’s
possible).

Thanks,
Rasmus

-- 
You people at the NSA are becoming my new best friends!

Re: [O] interaction between org-latex-custom-lang-environments and name when exporting to latex

[Alan Schmitt]

On 2015-11-20 11:41, Rasmus  writes:

> Alan Schmitt  writes:
>
>> I was wondering if someone had been able to reproduce this, and if so
>> should I file it as a bug?
>
> Sure.  It's how org-latex-src-block handles custom environments (see "Case
> 2.").  At the moment this is hardcoded.
>
> Perhaps the second element of org-latex-custom-lang-environments should
> allow a format string, so that an element could be something like,
>
> (emacs-lisp "\begin{common-lisp-code}[myoptions, label=%l]
> %s
> \end{common-lisp-code}")
>
> (modulus escaping).
>
> WDYT?

That would be great indeed. I see the code is not too hairy there, so
I'll try to write a patch.

Best,

Alan

-- 
OpenPGP Key ID : 040D0A3B4ED2E5C7
Athmospheric CO₂ (Updated November 9, 2015, Mauna Loa Obs.): 399.06 ppm


signature.asc
Description: PGP signature

Re: [O] [BUG] in export to odt -

[Rasmus]

Rainer M Krug  writes:

> I tried in LibreOffice, and indeed it does not seem to be possible. I
> don't know what the convention is, but I don't like that an invald .odt
> file is produced. Maybe give a warning about "incompatible features" or
> just drop the footnote in the footnote?

Dropping it is a possibility, though not a very nice one.

You can insert a cross-reference to a footnote within a footnote.  But I
don’t know how to insert a footnote without also adding a reference in the
text.  If the latter is possible, that way should work.

Rasmus

-- 
Not everything that goes around comes back around, you know

Re: [O] [BUG] in export to odt -

[Rainer M Krug]

Rasmus  writes:

> Rainer M Krug  writes:
>
>> I tried in LibreOffice, and indeed it does not seem to be possible. I
>> don't know what the convention is, but I don't like that an invald .odt
>> file is produced. Maybe give a warning about "incompatible features" or
>> just drop the footnote in the footnote?
>
> Dropping it is a possibility, though not a very nice one.

Agreed - for me it doesn't matter anymore, as the footnote in the
footnote was only a TODO reminder.

>
> You can insert a cross-reference to a footnote within a footnote.  But I
> don’t know how to insert a footnote without also adding a reference in the
> text.  If the latter is possible, that way should work.

This sounds like the way to go, but I would suggest that until there is
a solution (for this apparently not supported feature in LibreOffice?)
to either drop the footnote and give a warning in emacs, or insert the
footnote text in the footnote as verbatim text.

Cheers,

Rainer

>
> Rasmus

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

[O] [odt-export] Setting Text Colour for odt export

[Rainer M Krug]

Hi

I am using 

--8<---cut here---start->8---
\color{red} some red text \color{black} and we continue with black
--8<---cut here---end--->8---

to set the text colour for sections in my document for LaTeX export, but
this does obviously does not org for odt export.

What can I use to achieve the same for odt export?

Thanks

Rainer
-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

Re: [O] [BUG] in export to odt -

[Rasmus]

Hi,

Rainer M Krug  writes:

> Rasmus  writes:
>
>> Rainer M Krug  writes:
>>
>>> I tried in LibreOffice, and indeed it does not seem to be possible. I
>>> don't know what the convention is, but I don't like that an invald .odt
>>> file is produced. Maybe give a warning about "incompatible features" or
>>> just drop the footnote in the footnote?
>>
>> Dropping it is a possibility, though not a very nice one.
>
> Agreed - for me it doesn't matter anymore, as the footnote in the
> footnote was only a TODO reminder.

We support it in html and latex so we should not take this decision
lightly.

>> You can insert a cross-reference to a footnote within a footnote.  But I
>> don’t know how to insert a footnote without also adding a reference in the
>> text.  If the latter is possible, that way should work.
>
> This sounds like the way to go, but I would suggest that until there is
> a solution (for this apparently not supported feature in LibreOffice?)
> to either drop the footnote and give a warning in emacs, or insert the
> footnote text in the footnote as verbatim text.

I would like to see if someone who knows Libreoffice well will chime in.
I’m sure it’s possible somehow.

I have put Alan in the Cc as he has previously uncovered amazing options
in LO.  Alan: we want to be produce an odt document that mimics something
like the following in LO:

X[fn:1]
[fn:1] Y[fn:2]
[fn:2] Z

Worst case we can check the ODF specification which is sort of readable.

Otherwise, we’ll have to throw a warning.  (Error isn’t good here).

Thanks,
Rasmus

-- 
Together we'll stand, divided we'll fall

Re: [O] bug#21818: 24.5; org-set-tags-to indentation problems when called programmatically

[Nicolas Goaziou]

Emanuel Evans  writes:

> Nicolas Goaziou  writes:
>
>> I don't consider it to be a bug.
>>
>> `org-element-interpret-data' produces a string, which is expected to be
>> syntactically correct, but doesn't guarantee aesthetics. In particular,
>> `org-element-headline-interpreter' tries to align tags as accurately as
>> possible, but, in this case, fails to succeed as it would require to
>> introduce fontification in the process. This is out of the scope of the
>> function.
>
> Hmmm, that doesn't really make sense to me. Shouldn't the flow of
>
> 1. Edit a document with org-mode
> 2. (org-element-interpret-data (org-element-parse-buffer))
>
> be as close to the original as possible?

It is already as close to the original as reasonable.

The guarantee is that it is syntactically equivalent to the original.
Yet, some information is lost in the process. For example, global
indentation is not meaningful syntax-wise and not retained in the parse
tree. That information is lost. Case (for blocks, properties...) is
another example. As you noticed, the same goes for tags' column, under
some circumstances.

> Seems like the fontification aspect is just an implementation detail.
> In any case, I looked more into the code and would be happy to submit
> a patch to change it if it makes sense to you.

The problem is that the change has a cost. Basically, you need to create
a new buffer, switch to Org mode, copy local variables from the original
buffer, insert the headline and align the tags properly according to the
current fontification rules.

OTOH, all you need to from the caller is to re-align the tags after
insertion.

I suggest to do the latter.


Regards,

Re: [O] [odt-export] Setting Text Colour for odt export

[Rainer M Krug]

Rasmus  writes:

> Hi,
>
> Rainer M Krug  writes:
>
>> I am using 
>>
>> \color{red} some red text \color{black} and we continue with black
>>
>> to set the text colour for sections in my document for LaTeX export, but
>> this does obviously does not org for odt export.
>>
>> What can I use to achieve the same for odt export?
>
> You can use a macro.  {{{color(text, red)}}}.  You then specify a macro
> that inserts
>
>  @@latex:{\color{red} text}odt: text:style-name="red">text@@,
OK - that looks nice. Where can I read more about the @@...@@ syntax in
org? For conditional backend specific syntax I was only using

--8<---cut here---start->8---
#+MACRO: clearpage (eval (if (org-export-derived-backend-p 
org-export-current-backend 'latex) "\\clearpage"""   ))
--8<---cut here---end--->8---

but the @@...@@ looks clearer to me.

>
> Unfortunately, it doesn’t seem like odt provides inline styles, so you may
> have to add new styles for each color; see:
>
> 
> https://www.gnu.org/software/emacs/manual/html_node/org/Creating-one_002doff-styles.html

Hm. This sounds problematic, as I have to convert these to docx and send
them finally to the co-authors.

At the moment odt export just inserts "\color{red}" so I'll leave it
for this at the moment.

Thanks,

Rainer

>
> Hope it helps,
> Rasmus

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

[O] MobileOrg

[Peter Davis]

I'm just starting out with MobileOrg, using Dropbox, but I'm confused by the 
setup instructions. I've gotten the app linked to my
Dropbox account, but the next step in the setup instructions 
 involve
setting up some emacs stuff on my "local system." My question is: *Which* local 
system? I have several sync'ed to Dropbox. Is the
mobile app going to require a single point of contact?

Thanks,
-pd

Re: [O] interaction between org-latex-custom-lang-environments and name when exporting to latex

[Rasmus]

Alan Schmitt  writes:

> I was wondering if someone had been able to reproduce this, and if so
> should I file it as a bug?

Sure.  It's how org-latex-src-block handles custom environments (see "Case
2.").  At the moment this is hardcoded.

Perhaps the second element of org-latex-custom-lang-environments should
allow a format string, so that an element could be something like,

(emacs-lisp "\begin{common-lisp-code}[myoptions, label=%l]
%s
\end{common-lisp-code}")

(modulus escaping).

WDYT?

Rasmus

-- 
If you can mix business and politics wonderful things can happen!

Re: [O] [odt-export] Setting Text Colour for odt export

[Rasmus]

Hi,

Rainer M Krug  writes:

> I am using 
>
> \color{red} some red text \color{black} and we continue with black
>
> to set the text colour for sections in my document for LaTeX export, but
> this does obviously does not org for odt export.
>
> What can I use to achieve the same for odt export?

You can use a macro.  {{{color(text, red)}}}.  You then specify a macro
that inserts

 @@latex:{\color{red} text}odt:text@@,

Unfortunately, it doesn’t seem like odt provides inline styles, so you may
have to add new styles for each color; see:


https://www.gnu.org/software/emacs/manual/html_node/org/Creating-one_002doff-styles.html

Hope it helps,
Rasmus

-- 
One thing that is clear: it's all down hill from here 

[O] 24.5; PostScript Print Buffer fails on Agenda buffer

[sgeorgii .]

 Hello!

I filed this in debugs

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21938

but may be this list is better place to ask?

Please anyone could help me with the above (bug?) of Org-mode?

Re: [O] [BUG] in export to odt -

[Rainer M Krug]

Rasmus  writes:

> Rainer M Krug  writes:
>
>> The odt is attached for reference.
>
> Please also provide an odt document with the expected, working result.
> (I could not produce such a document in LO within 20s, but perhaps it’s
> possible).

I am not a LibreOffice / MS Word person (but my co-authors but my
co-authors unfortunately are...) so I only stumbled upon this when was
asked to give them a docx... file.

I tried in LibreOffice, and indeed it does not seem to be possible. I
don't know what the convention is, but I don't like that an invald .odt
file is produced. Maybe give a warning about "incompatible features" or
just drop the footnote in the footnote?

Thanks,

Rainer

>
> Thanks,
> Rasmus

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature

[O] Global visibility cycling broken: before first heading

[Loris Bennett]

Hi,

Yesterday I updated to version 8.3.2 (8.3.2-37-gd45217-elpaplus) and
today cycling global visibility seems to have stopped working.  No
matter where the cursors is in an org file, I get the error:

outline-back-to-heading: before first heading

This happens both with S- and M-x org-global-cycle.

Any ideas what might be going on?

Cheers,

Loris

-- 
This signature is currently under construction.

Re: [O] Global visibility cycling broken: before first heading

[Kyle Meyer]

"Loris Bennett"  writes:

> Hi,
>
> Yesterday I updated to version 8.3.2 (8.3.2-37-gd45217-elpaplus) and
> today cycling global visibility seems to have stopped working.  No
> matter where the cursors is in an org file, I get the error:
>
> outline-back-to-heading: before first heading
>
> This happens both with S- and M-x org-global-cycle.
>
> Any ideas what might be going on?

Are you using outshine?

http://thread.gmane.org/gmane.emacs.orgmode/100973

--
Kyle

Re: [O] 24.5; PostScript Print Buffer fails on Agenda buffer

[Eric S Fraga]

On Friday, 20 Nov 2015 at 13:05, sgeorgii . wrote:
>  Hello!
>
> I filed this in debugs
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21938
>
> but may be this list is better place to ask?
>
> Please anyone could help me with the above (bug?) of Org-mode?

Maybe post the details here?  (I read all of my emails while offline...)

In any case, while in agenda view,

  C-u M-x ps-print-buffer RET
  
works fine for me as does 

  C-u M-x ps-print-buffer-with-faces RET

I need the C-u as I don't have a printer defined on my system.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.2-215-gb4af3f

Re: [O] Exporting a subtree

[Brett Viren]

Peter Davis  writes:

> For the first time, I'm trying to export just a single subtree of my overall 
> document, by typing
>
> C-c C-e C-s H O
>
> However, I get this error:
>
> apply: Wrong type argument: listp, #("Details, November 2015" 0 22 (:parent 
> (#0)))

FWIW, I had this problem on my home machine about a week ago or so.  I
messed around with different versions of org and org-plus-contrib
installed from package-list-packages and eventually got it to go away.
Sorry I don't recall the specifics.  But I just wanted to say it's not
just you.

Right now, on my work system your test succeeds:

Org-mode version 8.2.10 (8.2.10-41-g42228a-elpa @ 
/home/bviren/.emacs.d/elpa/org-20150622/)

-Brett.


signature.asc
Description: PGP signature

[O] All source block properties on one line -- or foldied?

[Lawrence Bottorff]

Is there a way to put all of these prelim header lines on one line, such as
turning this

#+NAME: named-block
#+HEADER: :var data=2
#+BEGIN_SRC emacs-lisp
(message "data:%S" data)
#+END_SRC

to, perhaps, this

#+NAME: named-block; #+HEADER: :var data=2; #+BEGIN_SRC emacs-lisp
(message "data:%S" data)
#+END_SRC

. . . or maybe fold them?

I've tried a few things, but they're not working. I guess it's for
aesthetics sake; the chunkiness of all those headers stacked up is
distracting -- and the only folding just folds up the code contents itself.
I know drawers like :PROPERTIES: folds up nicely, but not Babel blocks. Any
way to get that behavior?

Also, Library of Babel seems to need the #+NAME field to "ingest" a code
block, so it's not really an option to just leave #+NAME off. And yes, I
need LOB for individual code block-level of control. Nothing else (I know
of) gives code block-level granularity, not `org-babel-load-file`, not the
usual Emacs package either -- unless I simply put one code block per file.
(FYI my train of thought.)

LB

[O] asynchronous python code blocks in org-mode

[John Kitchin]

Hi everyone,

I worked out some ideas on running Python blocks asynchronously in
org-mode, while seeing the output of the code, /and/ still capturing the
output in org-mode!

The post is here:
http://kitchingroup.cheme.cmu.edu/blog/2015/11/20/Asynchronously-running-python-blocks-in-org-mode/

It seems to work pretty well as a proof of concept, but the present
approach has some limitations, e.g. no sessions, no src-block :var, and
maybe others. These might be fixable at some point.

Anyway, I thought I would share it, to see if anyone has thoughts on
it, and in case it looks useful to you.

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[O] [sgeorgii .] bug#21938: 24.5; PostScript Print Buffer fails on Agenda buffer

[John Wiegley]

Copying bug report.

John

--- Begin Message ---
I launch emacs (-q switch makes no difference), open my .org file and
proceed as follows:

M-x org-agenda

a (agenda for current week or day)

menu "File" ->  "PostScript Print Buffer"

instead of printout of agenda on my printer I get the following error
in Backtrace:

Debugger entered--Lisp error: (wrong-type-argument listp org-priority)
  ps-face-attribute-list((bold . org-priority))
  ps-plot-with-face(78 82 (bold . org-priority))
  ps-generate-postscript-with-faces1(1 4783)
  ps-generate-postscript-with-faces(1 4783)
  ps-generate(# 1 4783 ps-generate-postscript-with-faces)
  ps-spool-with-faces(1 4783 nil)
  ps-print-with-faces(1 4783 nil)
  ps-print-buffer-with-faces(nil)
  call-interactively(ps-print-buffer-with-faces nil nil)
  command-execute(ps-print-buffer-with-faces)


I have this error on both Windows and Linux hosts with emacs version
24.5. Emacs version 24.3 or earlier work just fine on same Windows and
Linux hosts.

I get this error with "PostScript Print Buffer". If I choose "File"->
""PostScript Print Buffer (B+W)" - this gives me printer printout all
right on all versions of emacs on both Windows and Linux hosts .

Any help?


In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'

Important settings:
  value of $LANG: ENU
  locale-coding-system: cp1251

Major mode: Org-Agenda Week Ddl Grid

Minor modes in effect:
  tooltip-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  line-number-mode: t
  transient-mark-mode: t

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Press key for agenda command (unrestricted):
Formatting...  0%
Collecting face information...
ps-plot-with-face: Wrong type argument: listp, org-priority

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rfc822 mml mml-sec mm-decode
mm-bodies mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader
sendmail rfc2047 rfc2045 ietf-drums mm-util help-fns mail-prsvr
mail-utils ps-mule ps-print ps-def lpr diary-lib diary-loaddefs cal-iso
org-agenda org-element org-rmail org-mhe org-irc org-info org-gnus
gnus-util org-docview doc-view jka-compr image-mode dired cl-loaddefs
cl-lib org-bibtex bibtex org-bbdb org-w3m org org-macro org-footnote
org-pcomplete pcomplete org-list org-faces org-entities noutline outline
easy-mmode org-version ob-emacs-lisp ob ob-tangle ob-ref ob-lob ob-table
ob-exp org-src ob-keys ob-comint comint ansi-color ring ob-core ob-eval
org-compat org-macs org-loaddefs format-spec find-func cal-menu easymenu
calendar cal-loaddefs time-date tooltip electric uniquify ediff-hook
vc-hooks lisp-float-type mwheel dos-w32 ls-lisp w32-common-fns
disp-table w32-win w32-vars tool-bar dnd fontset image regexp-opt fringe
tabulated-list newcomment lisp-mode prog-mode register page menu-bar
rfn-eshadow timer select scroll-bar mouse jit-lock font-lock syntax
facemenu font-core frame cham georgian utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanese hebrew greek romanian slovak
czech european ethiopic indian cyrillic chinese case-table epa-hook
jka-cmpr-hook help simple abbrev minibuffer nadvice loaddefs button
faces cus-face macroexp files text-properties overlay sha1 md5 base64
format env code-pages mule custom widget hashtable-print-readable
backquote make-network-process w32notify w32 multi-tty emacs)

Memory information:
((conses 8 221645 10009)
 (symbols 32 26574 0)
 (miscs 32 4419 2098)
 (strings 16 41593 5657)
 (string-bytes 1 1344167)
 (vectors 8 18490)
 (vector-slots 4 493986 7658)
 (floats 8 379 246)
 (intervals 28 2940 838)
 (buffers 508 16))



--- End Message ---

[O] bug#21938:

[sgeorgii .]

 Also if I have no items with priority indication ([A], [B], [C]) -
then "PostScript Print Buffer" works just fine and gives printout just
fine on all emacs versions, with all Linux/Windows hosts.

So may I suggest that it is the face of ([A], [B], [C]) priority marks
what is confusing "PostScript Print Buffer" ? But as far as I could
tell the "org-priority" face is not customized in my system:


Org Priority face: [sample]
State : STANDARD.
   Face used for priority cookies.
   [X] Inherit:
   INS DEL Face: (sample) font-lock-keyword-face
   INS
   Show All Attributes

[O] How to print only visible elements of org-agenda

[sgeorgii .]

Hello!

I run  org-agenda and then I do some filtering of the agenda by tags.

Then I simply want to print the lines which I now see on the screen.

My problem is - I am getting printed _all_ lines of org-agenda,
including those I just filtered out and do not see on my screen!

My desired outcome is to get printed only those org-agenda lines I see
on screen after filtering. Can this be done?

[O] [PATCH] lisp/ox-publish.el: Handle includes with searches

[Nick Gunn]

* lisp/ox-publish.el (org-publish-cache-file-needs-publishing): Ignore
  any link search suffix on an include so that the path represents a
  valid file during the publishing check.

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

diff --git a/lisp/ox-publish.el b/lisp/ox-publish.el
index c7da953..7799d8b 100644
--- a/lisp/ox-publish.el
+++ b/lisp/ox-publish.el
@@ -1244,8 +1244,8 @@ the file including them will be republished as well."
   (let ((value (org-element-property :value element)))
 (and value
  (string-match "^\\(\".+?\"\\|\\S-+\\)" value)
- (org-remove-double-quotes
-  (match-string 1 value)))
+ (car (split-string (org-remove-double-quotes
+ (match-string 1 value)) 
"::")))
(when included-file
  (push (org-publish-cache-ctime-of-src
 (expand-file-name included-file))
-- 
2.5.2

[O] bug#21938: 24.5; PostScript Print Buffer fails on Agenda buffer

[John Wiegley]

> sgeorgii   writes:

> I launch emacs (-q switch makes no difference), open my .org file and
> proceed as follows:

> M-x org-agenda

I've forwarded this to the Org-mode mailing list.

John

Re: [O] MobileOrg

[dean]

On 11/21/15 00:14, Peter Davis wrote:
Hi pd,

> I'm just starting out with MobileOrg, using Dropbox, but I'm confused by the 
> setup instructions. I've gotten the app linked to my
> Dropbox account, but the next step in the setup instructions 
>  involve
> setting up some emacs stuff on my "local system." My question is: *Which* 
> local system? I have several sync'ed to Dropbox. Is the
> mobile app going to require a single point of contact?
> 

Im fairly new to emacs and mobileorg, so im no expert here but...
I believe Mobile org will be using your dropbox folder as its single
point of contact.
For example your workflow would be:
- Create/edit notes/todo's on your phone
- sync the app (which should save to dropbox)
- Open emacs on your pc, issue org-mobile-pull
- This should add your edits to your org files on your pc

For the other direction:
- Edit org files on your pc, issue org-mobile-push
- sync on the app should import your edits into the app

Im assuming you have a dropbox daemon taking care of the syncing in this
process.

This should be the same no matter how many pc's/emacs you use.
Does this help answer your question?

Cheers,
Dean

[O] [BUG] in export to odt -

[Rainer M Krug]

The following .org file produces an invalid .odt file upon export to odt
because of the footnote in the footnote:

--8<---cut here---start->8---
#+TITLE: Footnote in footnote produces invalid .odt
#+AUTHOR: Rainer M. Krug

* A Footnote in a Footnote
Some footnote[fn:2]

* Versions
Org-mode version 8.3.2 (release_8.3.2-161-gd2ac25 @ 
/Users/rainerkrug/.emacs.d/elpa/24.5/org-20151005/)
GNU Emacs 24.5.1 (x86_64-apple-darwin15.0.0, Carbon Version 157 AppKit 1404.13) 
of 2015-11-03 on Rainers-MacBook-Pro.local
Libre Office: Version: 5.0.3.2
  Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
  Locale: en-US (en.UTF-8)

* FOOTNOTES

[fn:2] Footnote 2[fn:1]

[fn:1] CHECK!
--8<---cut here---end--->8---

The odt is attached for reference.


Cheers,

Rainer



test.odt
Description: Binary data




-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


signature.asc
Description: PGP signature