Re: [O] org-babel-execute:go crashes on Mac

[Mario Martelli]

Thank you for your answer. 

> If you haven't already, I suggest checking that there isn't a difference in 
> your Go setup, by working out the "go run ..." command that is being run 
> below, and running that manually yourself.

My first assumption was - to be honest, still is - that the "go run …” is not 
executed at all because the call to “go run …”  is within an illegal elisp 
function. Am I wrong with my assumption?

Kind regards
Mario

P.S. Would have no idea how to work out what the outcome of the function is ;)

[O] org-babel-execute:go crashes on Mac

[Mario Martelli]

Morning,

recently I tried to use ob-go and ran immediately into:

org-babel-execute:go: Invalid function: (results (org-babel-eval (format "%s 
run %s \"%s\" %s" org-babel-go-command (mapconcat (quote identity) 
(org-babel-go-as-list flags) " ") (org-babel-process-file-name tmp-src-file) 
(mapconcat (function (lambda (a) (format "%S" (if (symbolp a) (let* (... ...) 
(if ... ... out)) a (org-babel-go-as-list args) " ")) ""))

The strange thing is, that this only happens on my Mac. On my CentOS machine it 
works like a charm. Both machines run on Emacs 26.1b1 and org mode 
9.1.9-65-g5e454. All packages are from Melpa and the machines share the same 
.emacs.

I have no idea how to get to the bottom of this phenomenon. Any hint or help 
would be appreciated very much.

Thank you
Mario

— 

Re: [O] store-link protocol does not store the title

[Mario Martelli]

Hi Aline,

I just called it from my browser and got a nice org link after executing 
‘org-insert-link’. With ‘C-y’ you’ll get only the URL.

Cheers Mario

— 

GNU Emacs 25.3.3 (x86_64-apple-darwin13.4.0, Carbon Version 157 AppKit 1265.21) 
of 2017-09-28
Org mode version 9.1.2 (release_9.1.2-154-g99dbca @ 
/Users/…./Documents/repo/org-mode/lisp/)




> Am 17.07.2018 um 17:15 schrieb Aline Gerard :
> 
> 
> Hi all,
> 
> I'm testing store-link protocol. 
> When I execute  ' emacsclient "org-protocol://store-link?url=URL=TITLE" 
> ' the title is not stored, just url is stored. 
> I don't have [[URL][TITLE]] but just URL !
> 
> Any idea ? Thanks.
> 
> -- 
> Aline
> 

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,sorry for late response. I like the new docs very much.I would like to suggest some minor changes.

0001-oprg-prtocol-minor-changes-to-new-documentation.patch
Description: Binary data

Kind regardsMario— 

Am 06.07.2017 um 19:54 schrieb Nicolas Goaziou <m...@nicolasgoaziou.fr>:Hello,Mario Martelli <tl...@schnuddelhuddel.de> writes:I started this whole thing because I wanted to learn elisp. Butlearning texinfo en-passant is nice :)Thank you for your patch.I re-worded the documentation based on your work. I also added moreindex entries. Since I'm not using Org Protocol, I may fall wide of themark.Anyway, it's now your turn to do some reviewing ;)WDYT?Regards,-- Nicolas Goaziou    0x80A93738<0001-org.texi-Document-Org-Protocol.patch>

Re: [O] org-protocol documentation

[Mario Martelli]

>> This one I do not understand.
>> I use now @file{emacsclient} consistently if that was the meaning of the 
>> comment.
>> 
> 
> No, it's a much more mundane style issue: you need to have two spaces after a 
> period.

:smile:

I hope I got that changed too ;)

rgrds
Mario
— 



smime.p7s
Description: S/MIME cryptographic signature

Re: [O] Problem with Org-mobile

[Mario Martelli]

> "Steve Prud'Homme"  writes:
> 
>> When I go in the mobile-org App on my phone I sync, nothing append,
>> no file is showing.
> 
> Could it be a problem with Mobile-Org ?

Sounds like it. Would love to hear about it on: 
https://github.com/MobileOrg/mobileorg/issues 


rgrds
Mario
— 



smime.p7s
Description: S/MIME cryptographic signature

Re: [O] org-protocol documentation

[Mario Martelli]

>> I’m not happy with that there is so much information - although
>> outdated - in the old Worg documentation which might be hidden to the
>> reader.
> 
> Note that most of this documentation is available through other
> means, AFAIU.

Ok, what I meant are the readers who are not able to use Google ;)

> You probably missed my remark about this part. I think each sub-protocol
> should be introduced in a similar way.

I misinterpreted the meaning. I do not really like to begin each sentence with 
the same phrase. But I got it eventually that it's a manual ;)

>> +Two functions can help you fill @code{org-protocol-project-alist} with valid
>> +contents: @code{org-protocol-create} and @code{org-publish-project-alist}.  
>> The
>> +latter is of use if you're editing an Org file that is part of a
>> +publishing project.
> 
> Though, I'm puzzled, `org-publish-project-alist' is a variable, not a 
> function.

Don’t know what happened there. Repaired.

>> +Org protocol is triggered by @file{emacsclient}. If you want to use Org
>  ^^^
> Gotcha
> 
>> +protocol, there are many possibilities to do so.  You can invoke emacsclient
>> +by a shortcut on your desktop for example. Or by adding a bookmark to your 
>> browser.
>^^^
>   Ditto

This one I do not understand.
I use now @file{emacsclient} consistently if that was the meaning of the 
comment.

> This is the trick part. We need to feed the index.

>@cindex Installing Org protocol

>  @vindex org-protocol-project-alist

>  @findex org-protocol-project-alist

I started this whole thing because I wanted to learn elisp. But learning 
texinfo en-passant is nice :)




0001-org.texi-Basic-Org-protocol-documentation-is-added.patch
Description: Binary data


0002-org.texi-Fixes-missing-space-after-dot.patch
Description: Binary data


0003-org.texi-Minor-changes-and-added-index-to-org-protoc.patch
Description: Binary data


(second patch attached out of consistency reasons)

Kind regards
Mario
— 

Re: [O] causing work by pasting links

[Mario Martelli]

Hi,

> *   before i paste a link i type [[
> * [[|]]   this leaves the point right there.
> 
> then i paste and now i want to press [ to write my notes.
> 

Did you try ‘org-insert-link’? Should be less typing.

rgrds
Mario
— 



smime.p7s
Description: S/MIME cryptographic signature

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,

>> Any comments?
> 
> Always ;)

:-)

> Are there really two functions? You only
> document one.

Hope it’s clearer now.

> Genuine question: is this documentation actually complete enough to use
> the feature?

I suppose so, if one knows how to configure URL handlers on their OS. Of course 
there are some things missing from the documentation. But it’s more than we 
have at the moment :)

I’m not happy with that there is so much information - although outdated - in 
the old Worg documentation which might be hidden to the reader. 

Anyway, I hope I’ve correctly incorporated all your comments.




0001-org.texi-Basic-Org-protocol-documentation-is-added.patch
Description: Binary data


0002-org.texi-Fixes-missing-space-after-dot.patch
Description: Binary data


Kind regards
Mario
— 

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,

> I’ll start with a fresh approach and try to bring up a short manual in 
> org.texi.

I created a pretty short documentation of org-protocol. It’s still mainly 
copied from the old documentation. But distilled :)

It might be an idea to link to the old documentation at worg. 

I know that it is far away of an ideal documentation but better than what we 
have at the moment ;)

Any comments?



org.texi.diff
Description: Binary data


Kind regards 
Mario
— 

Re: [O] Capture template 'C': nil

[Mario Martelli]

> MM> Try to use ‘entry’ instead of ‘item’
> 
> Unfortunately I need an item. It used to work, unfortunately it no
> longer does.

I was probably to quick by changing ‘item’ to ‘entry’.

I tried your template once again. And it turned out that the file must be 
existent.

("c" "capture CWN through org protocol" item (file 
"~/org/notes.org")
"- %?%:description\n  %:link\n\n")

Does work for me. So giving a path to file might help.

> Greedy org-protocol handler.  Killing client.
> No server editing buffers exist
> Capture template ‘C’: nil

That was caused by using “C”, wasn’t it?

Kind regards
Mario
— 

Re: [O] Capture template 'C': nil

[Mario Martelli]

Hi,

> Here is the template
> 
>  ("C" "capture CWN through org protocol" item (file "next-cwn.org")
>   "- %?%:description\n  %:link\n\n")
> 
> When I use it on a page, it directly adds the entry to the file, without
> going through the capture interface, and it adds an extra %? in the
> text.

Try to use ‘entry’ instead of ‘item’

 ("C" "capture CWN through org protocol" entry (file "next-cwn.org")
  "- %?%:description\n  %:link\n\n")

“C” is usually bound to “Customise org-capture-templates”. Probably it’s better 
to choose another key.

In the next step you will probably get an error:  org-capture: Capture template 
‘i’: Template is not a valid Org entry or tree

To avoid that make the entry a tree:

 (“c" "capture CWN through org protocol" entry (file "next-cwn.org")
  “* %?%:description\n  %:link\n\n")

rgrds
Mario
— 




smime.p7s
Description: S/MIME cryptographic signature

Re: [O] org-protocol documentation

[Mario Martelli]

>> +worked for me on Windows-XP Professional and the emasc23 from 
>> ourcomments.org 
>> +(@uref{http://ourcomments.org/cgi-bin/emacsw32-dl-latest.pl 
>> }). I'm no Windows user
>> +though and enhancements are more than welcome on the org-mode mailinglist. 
>> The
>> +original file is from
>> @uref{http://kb.mozillazine.org/Register_protocol 
>> }.
> 
> Could someone double-check this?
> 
>> +@example
>> +REGEDIT4
>> +
>> +[HKEY_CLASSES_ROOT\org-protocol]
>> +@@="URL:Org Protocol"
>> +"URL Protocol"=""
>> +[HKEY_CLASSES_ROOT\org-protocol\shell]
>> +[HKEY_CLASSES_ROOT\org-protocol\shell\open]
>> +[HKEY_CLASSES_ROOT\org-protocol\shell\open\command]
>> +@@="\"C:\\Programme\\Emacs\\emacs\\bin\\emacsclientw.exe\" \"%1\""
>> +@end example
>> +
>> +@item
>> +macOS setup
> 
> See above.

As it seems Org protocol is not so popular :)

I assume there will be no feedback and it'll be sufficient to relegate to the 
OS documentation.

Especially the OS and 3rd party application related stuff made be anxious about 
rewriting the original documentation.

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,

> Besides the changes suggested above, we should put some thinking in the
> structure, which may be not adapter for a manual.  In particular, it
> should be made shorter.

My attempt was to copy the existing documentation from worg to the core 
documentation and to leave as much as possible unchanged.

I also think that a much shorter documentation of Org protocol would be the 
better approach. 

> Also, index entries are sorely missing for now.


It seems that writing the documentation in Org and exporting it to texi might 
not be the best approach.

I’ll start with a fresh approach and try to bring up a short manual in org.texi.

BTW: Papers are signed

Kind regards
Mario
— 

Re: [O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Mario Martelli]

Applied. Thank you.Thanks to you :)I fixed some whitespace issue and typo in the test.:blush:  Thanks again.Could you provide an ORG-NEWS entry about it?Sure.

0001-ORG_NEWS-org-protocol-s-date-style-URL-support-is-me.patch
Description: Binary data
Kind regardsMario

Re: [O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Mario Martelli]

Hi,

> Would it be possible to make the path involved smaller so that the
> example can fit in 80 columns?

The idea was to give an example which is available online and could get cloned 
easily onto the local machine.
Changed it to a simple example.

> Here, `replacement' isn't lexically bound, so compiling
> "org-protocol.el" should return an error. `replacement' should be
> let-bound instead.
 ...
Thank you for your patience, Nicolas 
Please find attached a fresh attempt.



0001-org-protocol.el-sources-with-date-URL-are-supported.patch
Description: Binary data


> Great. Let me know when the process is complete.

Will do. Sent out the signed copy today.

Kind regards
Mario

— 

Re: [O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Mario Martelli]

Hi,

> OK. Could you wrap up the patches needed so far, with appropriate commit
> messages, so I can apply them?

Sorry for producing noise. Just read the contribution guidelines once again ;)
Hope everything is now according to the guidelines.



0001-org-protocol.el-Fix-for-failing-open-source-subproto.patch
Description: Binary data


0002-org-protocol.el-Fix-for-silently-failing-open-source.patch
Description: Binary data


0003-org-protocol.el-sources-with-date-URL-are-supported.patch
Description: Binary data


0004-test-org-protocol.el-date-style-URL-support.patch
Description: Binary data


> BTW, have you signed FSF papers?

Applied for it just now. Have marked the changes as tiny. 

Kind regards
Mario

— 

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,

> Also, I suggest using ox-texinfo from development version, if you can,
> as the Texinfo output should be superior.

Done that, eventually.

> Also, if the syntax is not quite right, no worries,
> we'll fix it.

That is probably necessary.

Please note, that the documentation assumes that the patches regarding 
“open-source” are applied.



0001-org-protocol-documentation-is-moved-to-core-document.patch
Description: Binary data


Kind regards
Mario
— 

Re: [O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Mario Martelli]

> If all tests in "test-org-protocol.el" pass with your changes, I think
> it is fine to apply them.


Selector: "test-org-protocol/"
Passed:  2
Failed:  0
Skipped: 0
Total:   2/2

> Another round of tests for the cases you solve
> would be nice, too.

I added the configuration part. That will be parsed during the tests I suppose.


Selector: "test-org-protocol/"
Passed:  3
Failed:  0
Skipped: 0
Total:   3/3



0004-config-for-date-style-URL-is-added-to-org-protocol-t.patch
Description: Binary data


Adding full test-coverage of my changes is beyond my abilities at the moment, I 
must admit.
But I will come back to it soon, I promise ;)
Especially as there are succeeding tests for open-source using old-style URIs. 
(old-style URIs are not working for me with open-source)
That will be the next task for me after completing the documentation.

Speaking of the documentation: is it right, that there is no more support for 
“remember”? 
I would then remove that part from the documentation.

Kind regards
Mario
— 

[O] [PATCH] org-protocol: fixes open-source and extends rewriting of URLs

[Mario Martelli]

Hi list,Doing the tests for the documentation I encountered some issues with org-protocol.[0001-url-is-sanitized-before-processing]I’ve got trouble to get sub-protocol “open-source” working in some cases. By sanitising the URL it works for me in all cases.

0001-url-is-sanitized-before-processing.patch
Description: Binary data
[0002-tests-open-source-uri-against-uri-and-not-filename]This changes the test of the URI which was tested against the resulting filename. It’s now tested against the base-url.I’m still unsure with this because the code is there for more than seven years. Maybe I’m not seeing something obvious here. But all tests I made so far are succeeding with this change.

0002-tests-open-source-uri-against-uri-and-not-filename.patch
Description: Binary data
[0003-org-protocol-open-source-can-open-hugo-sources-with-date-url]Enables “open-source” to open hugo sources from a blog which is using date URLs like:https://cool-blog.com/2017/05/20/cool-post/WDYT of this?Kind regardsMario— 

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,

> fails all the time causing the function to fail silently.


I got "open-source" working by sanitising the URI before it is processed.


diff --git a/lisp/org-protocol.el b/lisp/org-protocol.el
index 825435674..7e986a9ed 100644
--- a/lisp/org-protocol.el
+++ b/lisp/org-protocol.el
@@ -520,7 +520,7 @@ The location for a browser's bookmark should look like this:
   ;; As we enter this function for a match on our protocol, the return value
   ;; defaults to nil.
   (let ((result nil)
-(f (plist-get (org-protocol-parse-parameters fname nil '(:url)) :url)))
+   (f (org-protocol-sanitize-uri (plist-get (org-protocol-parse-parameters 
fname nil '(:url)) :url
 (catch 'result
   (dolist (prolist org-protocol-project-alist)
 (let* ((base-url (plist-get (cdr prolist) :base-url))



Unfortunately it is still failing for old-style URIs. Fixing that would exceed 
my abilities.

I could document that "open-source" does only support new-style URIs. Not sure 
if that is the best solution.

Kind regards
Mario
— 

Re: [O] org-protocol documentation

[Mario Martelli]

Hi,

> Am 22.06.2017 um 22:03 schrieb Nicolas Goaziou :
> 
> So as to ease the reviewing process, could you send it on the ML with
> git format-patch sub-command?
> 

sure. I would like to add an example using the subprotocol “open-source” for 
hugo. If that sounds ok for you.
For that I would need “open-source” working, of course.

> Also, I suggest using ox-texinfo from development version, if you can,
> as the Texinfo output should be superior.

have to set that up first. But I think I will need it anyway. ;)

>>> I assume a bug around Line 527 in org-protocol.el
>>> 
>>>  (let* ((base-url (plist-get (cdr prolist) :base-url))
>>> —>   (wsearch (regexp-quote base-url)))   <—
>>> 
>>> Could anyone confirm that? I’m unsure whether it might be a local 
>>> misconfiguration on my side or not.
> 
> Confirm what?

That “open-source" is not working and is failing silently.

> Why do you think there is a bug in the line above?

Because I’m not experienced with elisp ;)

I dug a little deeper and do now assume that there *might* be something wrong 
with “f” which is created in line 523

(f (plist-get (org-protocol-parse-parameters fname nil '(:url)) :url)))

and which has “http:” as value if I’m using old style URIs and the whole URL 
(“http:/orgmode.org/worg/org-tutorials/org-import-rtm.html 
” in my example) if 
I’m using new style URIs.
I assume “f” should be set to the base-url ("http:/orgmode.org/worg/ 
“ in my case). 

Given that, the test in line 529 

(when (string-match wsearch f)

fails all the time causing the function to fail silently.

Thank you for being patient with me. At the moment I’m seeing parenthesises and 
backslashes everywhere :)

Kind regards
Mario
— 

Re: [O] org-protocol documentation

[Mario Martelli]

I’ve incorporated the org-protocol documentation into org.texi.

https://github.com/mgmart/org-mode/commit/31dd3cc13034c8501d8526e25086152a0e6538dd
 
<https://github.com/mgmart/org-mode/commit/31dd3cc13034c8501d8526e25086152a0e6538dd>

In a separate branch you could see the history of changes to the original 
org-protocol documentation from worg

https://github.com/mgmart/org-mode/commits/documentation/org-protocol 
<https://github.com/mgmart/org-mode/commits/documentation/org-protocol>

Still not sure wether the open-source subprotocol is broken or not.

Kind regards
Mario
— 



> Am 22.06.2017 um 10:40 schrieb Mario Martelli <tl...@schnuddelhuddel.de>:
> 
> I’m about to incorporate the new style URIs into the documentation. 
> During my tests somehow the open-source protocol does not work for me.
> 
> I assume a bug around Line 527 in org-protocol.el
> 
>   (let* ((base-url (plist-get (cdr prolist) :base-url))
> —>   (wsearch (regexp-quote base-url)))   <—
> 
> Could anyone confirm that? I’m unsure whether it might be a local 
> misconfiguration on my side or not.
> 
> I tried it with the worg example:
> 
>   emacsclient 
> "org-protocol://open-source?url=http://orgmode.org/worg/org-tutorials/org-import-rtm.html”
> 
> and escaped
> 
>   emacsclient 
> 'org-protocol://open-source?url=https%3A%2F%2Forgmode.org%2Fworg%2Forg-tutorials%2Forg-import-rtm.html’
> 
> In both cases it fails silently.
> 
>> I'm not sure why is pandoc needed here. Org can export to Texinfo
>> format, if needed.
> 
> Thank you! Output is much nicer than with pandoc. I’ve disabled it years ago 
> because not needed. So it went out of my sight ;)
> 
>> Also, if the syntax is not quite right, no worries,
>> we'll fix it.
> 
> That are great news!
> 
> Kind regards
> Mario
> — 
> 
> 
> 

Re: [O] org-protocol documentation

[Mario Martelli]

I’m about to incorporate the new style URIs into the documentation. 
During my tests somehow the open-source protocol does not work for me.

I assume a bug around Line 527 in org-protocol.el

   (let* ((base-url (plist-get (cdr prolist) :base-url))
—>   (wsearch (regexp-quote base-url)))   <—

Could anyone confirm that? I’m unsure whether it might be a local 
misconfiguration on my side or not.

I tried it with the worg example:

emacsclient 
"org-protocol://open-source?url=http://orgmode.org/worg/org-tutorials/org-import-rtm.html”

and escaped

emacsclient 
'org-protocol://open-source?url=https%3A%2F%2Forgmode.org%2Fworg%2Forg-tutorials%2Forg-import-rtm.html’

In both cases it fails silently.

> I'm not sure why is pandoc needed here. Org can export to Texinfo
> format, if needed.

Thank you! Output is much nicer than with pandoc. I’ve disabled it years ago 
because not needed. So it went out of my sight ;)

> Also, if the syntax is not quite right, no worries,
> we'll fix it.

That are great news!

Kind regards
Mario
— 

Re: [O] org-protocol documentation

[Mario Martelli]

> However, AFAIU, this change is about orgmanual.org, which is an outdated
> copy of the official manual in contrib/.

Well, I thought I could begin with an easy task for my first contribution :)

> Could you modify "org.texi" in doc/ directory instead?

This will take a while, I assume. Although pandoc did a terrific job, there is 
some additional work to do.

Kind regards
Mario
— 

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

[Mario Martelli]

> The default capture template didn't work for me:
> 
>(*"w"*
> *"Default template"*
> entry
> (file+headline *"~/org/capture.org "* *"Notes"*)
> *"* %^{Title}\n\n  Source: %u, %c\n\n  %i"*
> *:empty-lines* 1)

There are some asterisks which do not belong there. Probably it helps to remove 
them.
Otherwise it’s similar to the template I’m using.

> The %u and %c bits got replaced by the actual link code (i.e.,
> javascript:...). The following works as I wanted:
> 
>("w" "Default capture " entry
>  (file "~/org/notes.org ")
>  "* %^{Title}
>Source: [[%:link][%:description]]
>%:initial" :empty-lines 1)

It it works then it’s fine :)

Kind regards
Mario
— 





smime.p7s
Description: S/MIME cryptographic signature

Re: [O] mimetype for orgmode files

[Mario Martelli]

>> Is there an official mimetype for orgmode files?
> 
> In `mailcap-mime-extensions' there is a value `(".org"   . "text/x-org")'.
> 
> Maybe that is for Org-Mode.

It is :)
https://lists.gnu.org/archive/html/emacs-orgmode/2011-01/msg00977.html 


If official would mean registered with IANA, then it’s not.
https://www.iana.org/assignments/media-types/media-types.xhtml 


Link regards
Mario
— 




smime.p7s
Description: S/MIME cryptographic signature

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

[Mario Martelli]

>  it would make sense to suggest the
> new style syntax as the default for use by us newbies.

yeah, thought about that too. At the moment it’s still a copy of the old doc. 

Got no feedback so far wether my approach would be acceptable or not. Therefore 
I did not put much effort into it. 

But you’re right. The examples should be new style URIs and the infobox should 
reference the old style URIs.

Kind regards
Mario
— 



smime.p7s
Description: S/MIME cryptographic signature

Re: [O] [PATCH] protocol: allow users to disable warning about old style links

[Mario Martelli]

> I'm just starting to use org-protocol, and I'm confused by this warning.
> I can't find any description of the differences between the old and new
> link styles in the documentation, or any pointers as to how and what I
> should change to adopt the new syntax. The org manual links to
> http://orgmode.org/worg/org-contrib/org-protocol.html 
> , which seems to be
> a year or more out of date.

I have shared a proposal to move org-protocol documentation to core 
documentation.
It’s mainly copied together from the old one and 9.0 NEWS.

The important part regarding the new syntax could be found here:

https://github.com/mgmart/org-mode/blob/documentation/org-protocol/contrib/orgmanual.org#L7347-L7364
 


Would that help or is there still something to add?

Kind regards
Mario

smime.p7s
Description: S/MIME cryptographic signature

Re: [O] org-protocol documentation

[Mario Martelli]

> for what it's worth, the Emacs Mac Port supports org-protocol out of
> box. It works without the Emacs server (emacsclient), e.g.,

Good to know. I’ve listed it in the documentation.
Do you plan to provide ready built binaries?

>> - if not, I would update the documentation in general and for macOS
>> and would leave the linux and windows parts untouched (don’t know if
>> they need to be updated), if that’s ok.
> 
> This is fine as a first step IMO.

Please find my attempt at: https://github.com/mgmart/org-mode 


Kind regards
Mario
— 

[O] org-protocol documentation

[Mario Martelli]

Hi,

recently I’ve updated my macOS - Org mode setup. I had some pain setting up 
org-protocol properly which was mainly because the documentation 
(http://orgmode.org/worg/org-contrib/org-protocol.html 
) is outdated. 
Especially for macOS. I thought about updating the documentation. But I’m 
unsure wether that is still the correct place. To me it seems that org-protocol 
is no longer in org-contrib but in org-mode. I could not verify that because I 
could not clone the repo (fatal: unable to connect to orgmode.org: 
orgmode.org[0: 104.239.132.130]: errno=Operation timed out ).

- is the task of documenting org-protocol already scheduled?
- if not, I would update the documentation in general and for macOS and would 
leave the linux and windows parts untouched (don’t know if they need to be 
updated), if that’s ok.

Kind regards
Mario

— 
http://www.schnuddelhuddel.de 

[O] org-habit: completed-glyph not shown in graph-column

[Mario Martelli]

Hi all,

I’m just setting up org-mode. So I do not know whether this has worked in the 
past or not.

If I complete a habit I get this:

** TODO Shave
   SCHEDULED: 2015-08-11 Tue .+1d/2d
   :PROPERTIES:
   :STYLE:habit
   :END:
   - State TODO   from DONE   [2015-08-10 Mon 18:27]
   - State TODO   from DONE   [2015-08-05 Wed 22:36]
   - State TODO   from DONE   [2015-08-02 Sun 08:04]
   - State TODO   from DONE   [2015-08-01 Sat 08:03]
 

From what I found in the documentation it should be:

** TODO Shave
SCHEDULED: 2009-10-17 Sat .+2d/4d
:PROPERTIES:
:STYLE:habit
:LAST_REPEAT: [2009-10-19 Mon 00:36]
:END:
- State DONE   from TODO   [2009-10-15 Thu]
- State DONE   from TODO   [2009-10-12 Mon]
- State DONE   from TODO   [2009-10-10 Sat]
- State DONE   from TODO   [2009-10-04 Sun]

Despite of missing the LAST_REPEAT property I verified that the inversion of 
TODO and DONE is the reason that the completed-glyph is not shown in the 
graph-column.


The configuration of my habit file is:

* Habits
  :PROPERTIES:
  :LOGGING:  TODO(!) WAIT(!) DONE(!) CANCELED(!)
  :END:

Don’t know if this is a bug or a misconfiguration. 


Org-mode version 8.3.1 (8.3.1-16-gf6aa53-elpaplus

Kind regards
Mario
— 

Re: [O] org-habit: completed-glyph not shown in graph-column

[Mario Martelli]

Hi Nicolas,


 Shouldn't it be 
 
  :LOGGING:  TODO(!) WAIT(!) | DONE(!) CANCELED(!)
 
 Otherwise, DONE is not considered as a final keyword. Only CANCELED is.

thanks for the hint. I was not aware that ‘|’ is also necessary within LOGGING:

Nevertheless I’ve changed the logging property to:

  :LOGGING: DONE(!) 

as I do only need DONE within my habits file.

Now my agenda looks much nicer :-)

Thanks again
Mario