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

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]

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

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:

[O] org-protocol documentation

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

Re: [O] org-protocol documentation

> 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 ma

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

> 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://or

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

> 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

Re: [O] mimetype for orgmode files

>> 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

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

> 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 asterisk

Re: [O] org-protocol documentation

> 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

Re: [O] org-protocol documentation

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-u

Re: [O] org-protocol documentation

o — > Am 22.06.2017 um 10:40 schrieb 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* ((bas

Re: [O] org-protocol documentation

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

Re: [O] org-protocol documentation

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 +

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

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.p

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

> 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 adde

Re: [O] org-protocol documentation

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

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

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-su

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

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

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

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] org-protocol documentation

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 un

Re: [O] org-protocol documentation

>> +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 th

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

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. Tr

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

> 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

Re: [O] org-protocol documentation

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

Re: [O] org-protocol documentation

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 t

Re: [O] causing work by pasting links

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

>> 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 Goog

Re: [O] Problem with Org-mobile

> "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

Re: [O] org-protocol documentation

>> 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 Descri

Re: [O] org-protocol documentation

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

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

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) (mapconc

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

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 …

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

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-g99