Re: [O] Defining macros globally
> I added `org-export-global-macros' in master. It's Christmas, after all. Thanks! And, Merry Christmas! :-) signature.asc Description: PGP signature
Re: [O] Remove Org from Emacs repository?
Achim Gratz writes: > Phillip Lord writes: >> I think there's only a few problems, actually. package.el initialization >> is all or nothing at the moment, and is disabled on emacs -q. Neither of >> these would make sense if we wanted in built packages. > > My opinion is that unless package.el adds explicit support for > system-level packetization decisions (i.e. for admins or distributions) > it's not going to gain widespread support from that small, but important > set of folks. I think it mostly has this, in the sense that you can add packages into admin installation locations. Although, this are disabled with emacs -Q. > Of course the user will then have to be able to override these like > deactivation of packages, installing different versions, etc. Different versions you can do. Deactivation at the moment, no, although I guess you could delete the autoloads. > Before long it also needs to be able to cope with different package > archives simultaneously especially when those have incompatible > numbering schemes. That one would be a bit harder, although you could add support for package repositories to add their own numbering scheme by installating a package. > >> It's not strictly necessary, though. The current idea is to not to use >> packages but to, essentially, move the lisp of packages in ELPA into >> place in the build. package.el need not be involved then. > > Yes I know. Which is in essence prolonging the current state of affairs > as far as the users are concerned. If it gets things moving into the > right direction I'll be glad. I just had hoped for some more general > (some would say radical) solution. Some did say radical, unfortunately. Still, you give me encouragement. I may complete my solution after all. Perhaps combined with a completely repackaged Emacs core. Phil
[O] A modest "framework" for authoring teaching material with org-mode
Hi. For teachning this year, I've used a "framework" that consists in a set of umbrella .org documents which generate various output formats from a single included .org source. The goal is to author only a single "lesson.org" source, and generate both PDF handbooks (for students or teachers) and Web slides (using reveal.js, using org-reveal). I thinks it may be useful to some, so I've decided to document and publish it : http://www-public.tem-tsp.eu/~berger_o/org-teaching/ An example slides deck (self documenting it) : http://www-public.tem-tsp.eu/~berger_o/org-teaching/slides.html and corresponding handbook : http://www-public.tem-tsp.eu/~berger_o/org-teaching/handbook.pdf Feel free to reuse, adapt, enhance and report. Hope this helps. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France)
[O] [ANN] Add EXPORT_FILE_NAME keyword
Hello, I just introduced #+EXPORT_FILE_NAME keyword, which allows to change the output file name upon exporting a document. Regards, -- Nicolas Goaziou0x80A93738
Re: [O] org.texi edits, patch attached
Hello,
Lambda Coder writes:
> See attached patch for Exporting chapter against maint.
Thank you.
Unfortunately, I cannot apply it. Could you send create it with
format-patch against maint's tip, without gzipping it?
> Also my notes to your comments.
Answers follow.
>> +Org has export facilities for printing, format conversions, and general
>> +sharing of Org documents with the outside world. Org export supports
>> +pretty-printing, web publishing, slide shows, and quick exports of lists and
>> +tables to many foreign formats while retaining as much structure
>> +(@pxref{Document structure}) and markup (@pxref{Markup}) as possible. The
>> +many features of Org exports are constantly being improved and expanded and
>> +they are all explained in this chapter.
>
> I would remove "are constantly being improved and expanded and they"
>
> [why?]
It sounds like a commercial ad.
> Shouldn't we leave that for a docstring?
>
> [Perhaps, but all three conditions have to be together.]
Fair enough.
>> +@example
>> +#+ATTR_BEAMER: :options [Lagrange]
>> +Let $G$ be a finite group, and let $H$ be
>> +a subgroup of $G$. Then the order of $H$ divides the order of $G$.
>> +@end example
>
> The example above does nothing useful, does it? :options do not apply to
> paragraphs AFAIK.
>
> [I did not put it there, edit it as you see fit.]
OK, will do, if I remember about it.
>> +Options for MathJax (@code{org-html-mathjax-options}). MathJax is used to
>> +typeset @LaTeX{} math in HTML documents. @ref{Math formatting in HTML
>> +export} has an example.
>
> @xref{Math formatting in HTML export}, for an example.
>
> [commas don't make grammatical sense here after xref]
It is not about English grammar, but about Texinfo syntax.
@xref{whatever}, for example.
produces
See Section 3.1 [whatever], page 24, for example.
whereas
@xref{whatever} for example.
produces
See Section 3.1 [whatever], page 24 for example.
which is awkward.
>> #+BEGIN_SRC emacs-lisp
>> - (defun Fib (n) ; Count rabbits.
>> + (defun Fib (n)
>> (if (< n 2) n (+ (Fib (- n 1)) (Fib (- n 2)
>> #+END_SRC
>
> You ruined the joke :)
>
> ["count rabbit pairs" makes it more accurate but still nothing funny]
Too bad. I found it hilarious (!). Let's remove it then.
>> @example
>> -#+attr_texinfo: :options org-org-export-to-org ...
>> +#+attr_texinfo: :options opt1 opt2 opt3 ...
>> #+begin_defun
>> A somewhat obsessive function.
>> #+end_defun
>> @end example
>
> You also ruined the joke :) You need to replace the contents of the
> defun, which do not make sense anymore.
>
> [I did not know that was a joke.]
Ah well. I find names following specific schemes funny, at times.
> Also, #+begin_defun expects a function name, not arguments.
>
> [That's what I thought but see the original block was like that without
> options]
The original is correct since it provides a name for the function being
defined.
>> @noindent
>> -becomes
>> +exports to
>>=20=20
>> @example
>> -@@defun org-org-export-to-org ...
>> +@@defun opt1 opt2 opt3 ...
>> A somewhat obsessive function.
>> @@end defun
>> @end example
>
> Ditto.
>
> [Restored the previous example. Strongly suggest re-editing this
> example or removing it entirely. It's neither informative nor funny.]
You may not find it funny, but it's definitely informative, since it
illustrates the :options attribute.
Regards,
--
Nicolas Goaziou
Re: [O] [PATCH] Fix org-clock-load
Hello,
Matt Lundin writes:
> Since commit fda64f1ae2110175662b52daa3a5ec0f967f0c0d on November 6,
> org-clock-load no longer restores clocks in org-clock-persist-file. The
> contents of the file look like this:
>
> (setq org-clock-stored-history '(("/home/matt/org/inbox.org" . 39479)
> ("/home/matt/org/reading.org" . 63478)))
>
> The files both exist; the position information is correct; and
> org-clock-persist is t. And yet after calling org-clock-load,
> org-clock-history, org-clock-loaded, and org-clock-stored-history remain
> nil.
>
> The problem, it seems, is that the logic/order of the if statement was
> reversed in the commit above. The attached patch should fix the issue.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
[O] Org Mobile
I get the message error downloading checksums in org mode any suggestions?
[O] Properties ID vs. CUSTOM_ID (was: Automatically Generating IDs From Title and Date)
* Samuel Wales wrote: > On 12/18/16, Karl Voit wrote: >> Usually, my IDs start with the current ISO day to enforce uniqueness >> and look like this: > > my understanding, which might be incorrect, is that custom id is for > human-readable purposes, while id is for uuid. although you could > prepend to uuid. There once was a discussion on this topic here: https://lists.gnu.org/archive/html/emacs-orgmode/2016-08/msg00165.html I am a bit worried: So far, I got 125870 manually set ID properties in my Org-mode files. To me, using :ID: was straight forward since I never read about any other ID when I began with Org-mode in 2011. Many features required me to have an :ID: and no feature I stumbled upon required me to have something else as reference: id:this-is-an-id, making references using org-store-link, and so forth. So let's search through the manual: http://orgmode.org/org.html#Internal-links http://orgmode.org/org.html#Handling-links http://orgmode.org/org.html#Search-options Well, either this did not exist in 2011 or I was not paying attention. I never faced any disadvantage, using ID properties instead. Do I really need to migrate and risk broken links? Or is there a safe way to move to CUSTOM_ID? Are there advantages when I switch to CUSTOM_IDs? Do I really have to have a CUSTOM_ID *and* an ID set for being able to reference any heading via human-readable ids *and* features like org-store-link and so on? -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] a general ID picker
* Eric Abrahamsen wrote:
> Karl Voit writes:
>
>> 1 Improvement: ID Picker
>>
>>
>> First of all, I'd like to see some kind of ID picker when defining
>> `:TRIGGER:' and `:BLOCKER:' dependencies.
>>
>> This should work like this: after setting up the task in headings and
>> giving them IDs, I'd like to invoke a "I want to define a
>> dependency"-command. It first asks me what property I want to set:
>> `:TRIGGER:' or `:BLOCKER:'.
>>
>> Then I get asked to select any ID which could be found within the same
>> sub-hierarchy (or even in all files?).
>>
>> After being asked for the KEYWORD to be set for `:TRIGGER:'
>> dependencies (if applicable), the property is added to the current
>> heading accordingly.
>>
>> This would drastically improve creating dependency definitions and
>> prevent typing errors in the first place.
>
> I like this a lot, for more uses than just org-depend, and it would be
> very easy to implement. We've got `org-property-set-functions-alist' for
> using special functions to read the values of special properties, and
> we've got `org-id-get-with-outline-(drilling|path-completion), so it's
> pretty much already done!
>
> (defun my-trigger-property-prompt ()
> (when (derived-mode-p 'org-mode)
> (let ((id (org-id-get-with-outline-drilling))
> (kw (org-completing-read "Keyword: " org-todo-keywords-1)))
> (do-something-with-id-and-kw
>
> (push '("TRIGGER" . my-trigger-property-prompt)
> org-property-set-functions-alist)
>
> I don't actually know how the TRIGGER property is meant to be formatted
> (and I didn't really test the above), but something very near to the
> above should do what you want.
Well, I am afraid that I am totally lost when it comes to "pretty
much already done". The great Professor Kitchin helped me with a
sophisticated function and sent me the "almost finished" code and I
failed at making it run :-(
However, I do tend to think that the ID picker would be of general
interest and I'd like to see it in the global Org-mode featureset
for multiple purposes, not only defining org-depend dependencies.
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
[O] Preventing Org from being installed by elpa (was: Remove Org from Emacs repository?)
* Eric Abrahamsen wrote: > > Actually, I have a third: the plain old Org package from the > package repos, because I've installed other packages that require > it. (Another gripe: why isn't the loading of a file containing > (provide 'org) enough to tell the package manager not to install > another one?) I got the tipp of creating «~/.emacs.d/elpa/org-3101/org-pkg.el» with: (define-package "org" "3101" "Dummy org mode package" 'nil) And this simulates the fulfilled dependency so that my git version of Org-mode is the only one installed (besides maybe the default one from Emacs). HTH -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: > get Memacs from https://github.com/novoid/Memacs < https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] a general ID picker
Karl Voit writes:
> * Eric Abrahamsen wrote:
>> Karl Voit writes:
>>
>>> 1 Improvement: ID Picker
>>>
>>>
>>> First of all, I'd like to see some kind of ID picker when defining
>>> `:TRIGGER:' and `:BLOCKER:' dependencies.
>>>
>>> This should work like this: after setting up the task in headings and
>>> giving them IDs, I'd like to invoke a "I want to define a
>>> dependency"-command. It first asks me what property I want to set:
>>> `:TRIGGER:' or `:BLOCKER:'.
>>>
>>> Then I get asked to select any ID which could be found within the same
>>> sub-hierarchy (or even in all files?).
>>>
>>> After being asked for the KEYWORD to be set for `:TRIGGER:'
>>> dependencies (if applicable), the property is added to the current
>>> heading accordingly.
>>>
>>> This would drastically improve creating dependency definitions and
>>> prevent typing errors in the first place.
>>
>> I like this a lot, for more uses than just org-depend, and it would be
>> very easy to implement. We've got `org-property-set-functions-alist' for
>> using special functions to read the values of special properties, and
>> we've got `org-id-get-with-outline-(drilling|path-completion), so it's
>> pretty much already done!
>>
>> (defun my-trigger-property-prompt ()
>> (when (derived-mode-p 'org-mode)
>> (let ((id (org-id-get-with-outline-drilling))
>>(kw (org-completing-read "Keyword: " org-todo-keywords-1)))
>> (do-something-with-id-and-kw
>>
>> (push '("TRIGGER" . my-trigger-property-prompt)
>> org-property-set-functions-alist)
>>
>> I don't actually know how the TRIGGER property is meant to be formatted
>> (and I didn't really test the above), but something very near to the
>> above should do what you want.
>
> Well, I am afraid that I am totally lost when it comes to "pretty
> much already done". The great Professor Kitchin helped me with a
> sophisticated function and sent me the "almost finished" code and I
> failed at making it run :-(
>
> However, I do tend to think that the ID picker would be of general
> interest and I'd like to see it in the global Org-mode featureset
> for multiple purposes, not only defining org-depend dependencies.
Ha, sorry, I'll actually look at org-depend...
...okay, so it looks like the :TRIGGER: property can contain several
different types of values. But from your message you seem to be talking
about this kind:
some-other-headings-id-df83454(NEXT)
So the code you'd want would be (I actually tested it this time):
(defun my-trigger-property-prompt (&rest args)
(when (derived-mode-p 'org-mode)
(let ((id (org-id-get-with-outline-path-completion))
(kw (org-completing-read "Keyword: " org-todo-keywords-1 nil nil)))
(format "%s(%s)" id kw
(push '("TRIGGER" . my-trigger-property-prompt)
org-property-set-functions-alist)
I switched from `org-id-get-with-outline-drilling', as that raised an
error about `org-goto-map' being an undefined variable (lexical scoping
issue?). Also, this only does the one kind of TRIGGER format. Also it is
limited to completing on the TODO keywords defined in the current file,
but will accept others.
In short, it's got lots of limitations, but please do eval the above and
see if it works, then we can go from there.
Eric
Re: [O] A modest "framework" for authoring teaching material with org-mode
On 12/20/2016 10:45 AM, Olivier Berger wrote: > Hi. > > For teachning this year, I've used a "framework" that consists in a set > of umbrella .org documents which generate various output formats from a > single included .org source. > > The goal is to author only a single "lesson.org" source, and generate both > PDF handbooks (for students or teachers) and Web slides (using > reveal.js, using org-reveal). > > I thinks it may be useful to some, so I've decided to document and > publish it : > > http://www-public.tem-tsp.eu/~berger_o/org-teaching/ > > > An example slides deck (self documenting it) : > http://www-public.tem-tsp.eu/~berger_o/org-teaching/slides.html > and corresponding handbook : > http://www-public.tem-tsp.eu/~berger_o/org-teaching/handbook.pdf > > > Feel free to reuse, adapt, enhance and report. This is very nice. Thanks for sharing. Scott Randby > > Hope this helps. > > Best regards, >
[O] Mobile org on osx
If I have installation correct should their be installation files visible in my dropbox directory?
Re: [O] Mobile org on osx
Copied from my last response to a similarly vague question: #+begin_quote Greetings, To help anyone with much effectiveness, background information is critical. I'm guessing you're referring to Mobile Org (not Org Mobile) and infer you might be using the iPhone version (since your address is icloud). Other than that... we're completely in the dark. What was your syncing backend (dropbox, ssh, other)? What settings did you apply per the instructions? [1] Did you even follow the instructions? At what stage, specifically, did you get said message? More details from you = better help from us. John [1] http://orgmode.org/manual/MobileOrg.html #+end_quote You're free to continue sending one line emails to the list, but I promise we can't help you without more details. Mobile Org for iPhone (still unclear if you're using that version or Android, though icloud and now OSX suggest iPhone) allows for dropbox and webdav sync. So the answer with current minimal knowledge is "maybe?" What are installation files? *If* you select Dropbox as your sync backend then it is used as an online repository for a local Org-mode installation (on computer) to sync between a mobile device (such as an iPhone). So... typically .org files would be visible in the Dropbox directory you selected. I don't know what you did, what you think should happen, what you actually see... so I can't help. John On Tue, Dec 20, 2016 at 5:25 PM, Matthew Pritchard wrote: > If I have installation correct should their be installation files visible in > my dropbox directory?
Re: [O] [ANN] Add EXPORT_FILE_NAME keyword
Hi Nicolas On 12/20/2016 11:17 AM, Nicolas Goaziou wrote: Hello, I just introduced #+EXPORT_FILE_NAME keyword, which allows to change the output file name upon exporting a document. Thank you and a couple of questions/observations 1. Exporting to pdf latex - I used #+EXPORT_FILE_NAME: /foo/bar at the beginning of a document - worked fine. However, I tried to export a subheading with, e.g. #+EXPORT_FILE_NAME: /foo/baz, and the result is /foo/bar.pdf, not /foo/baz.pdf This is not the same result that using the PROPERTIES construct in a subheading, which will export with the subheading :EXPORT_FILE_NAME: /foo/baz, which does generate a short document named /foo/baz.pdf Should we be able to apply the new #+EXPORT_FILE_NAME: to a subheading or does it work only for an entire buffer? Org mode version 9.0.2 (release_9.0.2-132-gc130b2 @ /usr/local/share/emacs/site-lisp/org-mode/lisp/) GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-03-07 on trouble, modified by Debian 2. An editorial suggestion for the realted ORGNEWS item which currently reads: Simiralry to ~:EXPORT_FILE_NAME:~ property, this keyword allow to specify the name of the output file upon exporting the document. This has also an effect on publishing. be changed along the following lines? Similar to ~:EPORT_FILE_NAME:~ property, this keyword allows the user to specify the name of the output file upon exporting the document. This also has an effect on publishing (or "This also effects publishing." Regards, Charlie Millar
Re: [O] Elisp: help on string operations for fast file visiting
This is a different approach to what I think you want. Here is what I assume in this: 1. All the things you want to search for are in a file called archive.org which is in the same directory you are searching for (use an absolute path if it is not). 2. You have file links that only have a path, i.e. nothing like file:test.odp::45 3. You want the query to match some part of the path in a file link. 4. if you click on the link you want, it will open the file in the external program you want it to open in. This will probably work if they are always absolute paths, and might be a problem for relative paths (they would need to be correctly converted to absolute paths). What it does is get all the file links in the archive.org file that have a path that matches the query. If there is none, you get a message. If there is one, it opens it as if you clicked on the link. and if there is more than one, it prompts you with completing read to choose one, then opens it. #+BEGIN_SRC emacs-lisp (defun memacs-file (query) "Open memacs files by QUERY." (interactive "sQuery: ") (with-current-buffer (find-file-noselect "archive.org") (let ((links (org-element-map (org-element-parse-buffer) 'link (lambda (link) (when (string-match query (org-element-property :path link)) link) (cond ((= 0 (length links)) (message "No files found.")) ((= 1 (length links)) (org-open-link-from-string (format "[[file:%s]]" (org-element-property :path (car links) (t (org-open-link-from-string (completing-read "File: " (mapcar (lambda (link) (format "[[file:%s]]" (org-element-property :path link))) links #+END_SRC For a large archive file, you might be better off with a grep solution, since this has to parse the file first. Karl Voit writes: > Hi! > > For Memacs[1], I'd like to come up with a very fast Org-mode method to > open files independent of their location on your disk. I accomplished > everything necessary so far. However, I've got issues writing an elisp > function for extracting a file and sending it to a function that calls > the operating system app associated. My elisp knowledge is still too > bad :-( > > What I've got is a string (from the lookup) which contains: > (1) nothing > (2) one line like "** <2008-06-17 21:43> [[file:/home/user/dir/2008-06-17 > description of file.odp][2008-06-17 description of file.odp]]" > (3) multiple lines like (2) but with different files and links > > I'd like to get a "Sorry" message for (1). Easy, if only I know how to > count lines in strings (as opposed to buffers). > > For (2) I'd like to call my-open-in-external-app(string). > > For (3), I'd like to use the first line just as in (2) as a starter. I > do have some ideas on gracious "error-recovering" on this one but > that's maybe too complicated to code for now: getting rid of > substrings delimited by not-'a-zA-Z0-9' from the end of the link > until a match is found; message in case there is no unique match which > could be found this way. > > Could you please help me here? It'd help all users of the file index > module of Memacs. > > > The mini fragment I have so far is following but the regex seems to > be broken: > > #+BEGIN_SRC elisp > (let ( > (result (replace-regexp-in-string "\r?\n$" "" > (shell-command-to-string (concat "grep " > "2008-06-17" > " ~/org/memacs/files.org_archive");; > hard coded stuff for testing purposes > ) > ) > ) > ) > (message (concat "result -> " result)) > (re-search-forward " \[\[.+\]\[" nil t 1) > (let ( > (firstlink ((match-string 1))) > ) > (message (concat "first link -> " firstlink)) >) > ) > #+END_SRC > > > > [1] https://github.com/novoid/Memacs -- 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] Make fails on Git (c130b2e)
I just pulled the source and ran make, and it failed here: Done (Total of 115 files compiled, 3 skipped) make[2]: Leaving directory '/usr/local/src/org-mode/lisp' make[1]: Leaving directory '/usr/local/src/org-mode/lisp' make -C doc info make[1]: Entering directory '/usr/local/src/org-mode/doc' org-version: 9.0.2 (release_9.0.2-132-gc130b2) makeinfo --no-split org.texi -o org org.texi:10468: @item outside of table or list Makefile:55: recipe for target 'org' failed make[1]: *** [org] Error 1 make[1]: Leaving directory '/usr/local/src/org-mode/doc' mk/targets.mk:126: recipe for target 'info' failed make: *** [info] Error 2 Bill -- William Denton :: Toronto, Canada :: https://www.miskatonic.org/ Caveat lector.
Re: [O] Mobile org on osx
If you're referring to MobileOrg (here: https://github.com/MobileOrg/mobileorg) I'm the current maintainer and there is active work underway to release a new version. If it is with MobileOrg, feel free to open an issue on github. We'll need a little more info though to help you out. On Tue, Dec 20, 2016 at 6:39 PM John Hendy wrote: > Copied from my last response to a similarly vague question: > > #+begin_quote > Greetings, > > > To help anyone with much effectiveness, background information is > critical. I'm guessing you're referring to Mobile Org (not Org Mobile) > and infer you might be using the iPhone version (since your address is > icloud). > > Other than that... we're completely in the dark. What was your syncing > backend (dropbox, ssh, other)? What settings did you apply per the > instructions? [1] Did you even follow the instructions? At what stage, > specifically, did you get said message? > > More details from you = better help from us. > > > John > > [1] http://orgmode.org/manual/MobileOrg.html > > #+end_quote > > You're free to continue sending one line emails to the list, but I > promise we can't help you without more details. Mobile Org for iPhone > (still unclear if you're using that version or Android, though icloud > and now OSX suggest iPhone) allows for dropbox and webdav sync. So the > answer with current minimal knowledge is "maybe?" What are > installation files? *If* you select Dropbox as your sync backend then > it is used as an online repository for a local Org-mode installation > (on computer) to sync between a mobile device (such as an iPhone). > So... typically .org files would be visible in the Dropbox directory > you selected. I don't know what you did, what you think should happen, > what you actually see... so I can't help. > > > John > > On Tue, Dec 20, 2016 at 5:25 PM, Matthew Pritchard > wrote: > > If I have installation correct should their be installation files > visible in my dropbox directory? > >
Re: [O] mobile org org mode versions
Hi Matthew, do you mean MobileOrg for iOS or the android application? There's not hard constraint on org-* version for MobileOrg iOS as it just uses the built in org-mobile-push, org-mobile-pull commands. Sean On Fri, Dec 16, 2016 at 8:34 PM Matthew Pritchard wrote: > what is the org- version necessary to use mobile org? > >
Re: [O] staging area mobile org
This directory should be created when you link the app to dropbox and it should get created at ~/Dropbox/Apps/MobileOrg due to how Dropbox handles app permissions. If you're experiencing issues, watch for a new release. We're beta testing now with the v2 of the Dropbox API On Tue, Dec 13, 2016 at 8:15 PM Greg Troxel wrote: > > Matthew Pritchard writes: > > > The mobile org manual says to create a directory (set > > org-mobile-directory “~/Dropbox/MobileOrg”) > > That is not creating it so much as configuring org to use it. > > > Can I create this directory with a simple command instead of a lisp > > command? > > I am not sure if the directory has to exist or not. Probably that's > because getting an error that it does not and running mkdir is not hard > and easily forgotten. >
Re: [O] org mobile on Ipnone 5s
If this is MobileOrg iOS I'm assuming it's related to dropbox api changes. We're currently beta testing a switch over to v2 of their API and it is working well in local testing so far. On Tue, Dec 13, 2016 at 9:41 PM Matthew Pritchard wrote: > I have a dropbox account established And the org mode app installed. When > I try to sync I get the message.Error syncing changes > an error was encountered while attempting to fetch mobile.org. from the > server. > Does anyone have any insight? >
