[O] Running Org Babel code blocks on Mesos!
Hello Org mode users, I've had the idea for a while of combining Org Babel with Mesos, since I believe that such mix could be an interesting alternative for having descriptive deployments of workloads on a cluster by using Org syntax. I finished a very, very, very early version of it already so I'd like to share. (yes, it supports Docker...) I named it 'Borges', hope the name makes sense :) https://github.com/wallyqs/borges This is very early experiment, but any feedback is very appreciated! Regards, - Waldemar
Re: [O] Japanese popularity of orgmode
Ishikawa-san I know a super student. He wrote his thesis using Emacs with org-mode! Sounds interesting, by any chance is it on Github or somewhere publicly available? By the way I live in Tokyo, would be great to attend one of these Emacs+Org mode meetups in Kyoto or Tokyo! Japanese no problem ;) Cheers, - Waldemar On Wed, Jan 28, 2015 at 2:20 AM, Tory S. Anderson torys.ander...@gmail.com wrote: Thanks for the answer! Takaaki Ishikawa tak...@ieee.org writes: Dear Tory, Good point. I don’t know “taking off” is the correct word, but as you mentioned, it’s still growing. I can see several reasons why you think Japanese content has been increasing in the Web. First, some students use Emacs in their university because their teacher also uses Emacs. Then, the students use Emacs to write papers for graduation. I know a super student. He wrote his thesis using Emacs with org-mode! After graduation, they will be programmers, engineers, and researchers with high-level technical skills enough to distribute their knowledge through their blog and twitter. Second, We have several workshops related to Emacs and org-mode. At least, two workshops are held a few times a year at Kyoto and Tokyo. The participants of the workshops write blog entries and release some emacs-lisp actively. An Emacs advent calendar is a good example. Finally, we have many Japanese translated materials, manual, tutorial, org-web, and twitter bot, to know org-mode quickly and easily. And of course, the primary reason is that org-mode is very useful tool to do anything with Emacs :-) Best regards, Takaaki Ishikawa Jan 27, 2015 11:16 PM、Tory S. Anderson torys.ander...@gmail.com のメール： There seems to be (and has been for a while) a growing Japanese presence online with orgmode materials, documentation, addons, etc. Most recenlty I found this blog: http://paper.li/highfrontier/1300501273 . I had also noticed many of the page titles on the orgmode website/wiki had Japanese content. This has me curious. Does anyone know the story of what's causing it to take off in Japan, or whether taking off is even the right word? Is it just a few people or a department at a university that are using it?
Re: [O] FYI: GitLab will Add org-mode syntax highlighting
Awesome! As always in case there are issues in that Ruby parser implementation, feel free to make a ticket here: https://github.com/wallyqs/org-ruby Thanks, - Waldemar On Fri, May 30, 2014 at 2:40 AM, Rodolfo Aramayo raram...@gmail.com wrote: This is great news for every org-moder... http://feedback.gitlab.com/forums/176466-general/suggestions/4104483-add-org-mode-syntax-highlighting
Re: [O] Title of org files in github not recognized
Hi, yes this issue would be fixed once Github upgrades the Ruby implementation of the parser. To upgrade the version it takes making a pull request to the github/markup repository so that they bump the version and do the release, but it takes some time before the upgrade is validated (security checks, etc...) There another couple of issues that I would like it that they make it to Github, so once having those tackled I'll see if I can ask one of the maintainers to help out planning for an update soon. Cheers On Fri, May 2, 2014 at 12:21 AM, Sebastien Vauban sva-n...@mygooglest.comwrote: Julian Gehring wrote: On 01.05.2014 14:17, Sebastien Vauban wrote: Julian Gehring wrote: How I can convince github to recognize the '#+TITLE:' field of an org-file? This should be a 'h1' heading, while it is currently treated as normal text (for example, see https://github.com/julian-gehring/vignettes/blob/master/README.org). I know that this is a problem of the parsing on github's site, but is anyone aware of a good solution? That was supposed to be solved. See https://github.com/wallyqs/org-ruby/issues/3 Nice. So it seems that github is using an older version of org-ruby. Is it clear what the update policy/cycle of github for softwares like org-ruby is? Unfortunately, not to me... ;-) Best regards, Seb -- Sebastien Vauban
Re: [O] babel and long-running computations
Hey Christoph, Not sure if this would help you, but I've playing with the idea of extracting some of the functionality that Org babel provides and created a small tool for doing reproducible runs using Org mode syntax: https://gist.github.com/wallyqs/10989253 It is based on the Org ruby parser implementation so not all the latest syntax and features are covered... I named it `org-converge` in the sense that a reproducible run should converge into the same result, and also because in the long run I hope to achieve some similar functionality (or at least wrap around) what is possible to do currently with tools like chef, ansible etc... I' ve found it useful for doing reproducible runs along with other tools like Chef and Capistrano, and also for some development work. If you have some ideas or feature requests the feedback is welcome :) The repository is here: https://github.com/wallyqs/org-converge Hope this helps, - Wally On Thu, Apr 17, 2014 at 9:45 PM, Christoph Groth christ...@grothesque.orgwrote: Thorsten Jolitz tjol...@gmail.com writes: I’d love to hear about any frameworks or workflows that fulfill these requirements. here is a link about that topic: ,--- | http://draketo.de/english/emacs/parallel-babel `--- Thanks. I had found this one myself - this way of working does not seem to allow to capture the results of the calculation in orgmode. So probably a better way is to have some caching machinery in the background. I see that babel has built-in caching but there seems to be no way to support dependencies. Christoph
[O] [ANN] Syntax highlighting now available in Github in *.org files!
Hello Org mode users and developers, Github has just updated some moments ago their version of the Org Ruby gem which is used for the HTML export, and now code syntax highlight should be available in all the *.org files in your repos. The feedback from Brandon Keepers (@bkeepers) at Github was very helpful to know the requirements and is key person in making this release possible to happen, you can thank him in this now closed ticket: https://github.com/github/markup/issues/253 If you have some feedback on the rendering of the output done by Org Ruby gem, please let me know and submit an issue in the repo and I will follow up (PRs welcome as well of course!): https://github.com/wallyqs/org-ruby/issues Thanks, - Wally
Re: [O] #+HOMEPAGE in metadata - feature request?
I think already 'supported' in the sense that something like #+HOMEPAGE: would count as being an in-buffer setting as described in the http://orgmode.org/manual/In_002dbuffer-settings.html Org mode uses special lines in the buffer to define settings on a per-file basis. These lines start with a '#+' followed by a keyword, a colon, and then individual words defining a setting. On Fri, Mar 21, 2014 at 10:07 PM, Bastien b...@gnu.org wrote: Hi Marcin, Marcin Borkowski mb...@wmi.amu.edu.pl writes: what about adding #+HOMEPAGE (alongside #+AUTHOR and #+EMAIL) to the metadata? What would it do? What are the pros and cons? (One argument against: default LaTeX classes do not support this. Any other?) Not sure what supporting means :) -- Bastien
Re: [O] Writing your book with orgmode and publishing it on Leanpub
Sebastien, For me, an annoying problem is that the Org #+TITLE is treated as a simple text, and not outputted as an headline. So, if we want an headline on GitHub, we need to create a unique level-1 heading, which will be shown as the most important section, hence the title. Then, under that, we can have many level-2 sections. Ok, I will revisit this part of the output from the parser and change it in the next release so that Github can also pick it up (issue here: https://github.com/wallyqs/org-ruby/issues/3) Thanks, - Wally On Mon, Feb 24, 2014 at 6:23 PM, Sebastien Vauban sva-n...@mygooglest.comwrote: Hello Waldemar, Waldemar Quevedo wrote: It is rather annoying that github understands the org syntax but not quite, so the sources appear almost but not quite right. I maintain the parser that is being by Github = https://github.com/wallyqs/org-ruby If you let me now the issues I can try to fix them, (or PRs are also welcome) For me, an annoying problem is that the Org #+TITLE is treated as a simple text, and not outputted as an headline. So, if we want an headline on GitHub, we need to create a unique level-1 heading, which will be shown as the most important section, hence the title. Then, under that, we can have many level-2 sections. That feature makes it impossible to get the same design for Org documents both as PDF, HTML or GitHub presentation page. Best regards, Seb -- Sebastien Vauban
Re: [O] Writing your book with orgmode and publishing it on Leanpub
Sorry I sounded dismissive. You are doing an awesome job, it's amazing how much it did get right. No problem at all :) My problem is that I am trying to share my sources as code, not as documentation. I would like my .org files to be treated as you would treat Python code, shown as they are and syntax-highlighted. I've been trying to have syntax highlighting available for documents rendered in Github for a while now. Possibly when this pull request is accepted thinks would be highlighted: https://github.com/github/markup/pull/254 That said, the one place where the translation fails is when the source code of babel snippets should not be exported. Again, probably due to the tension between the need to show the file's content and the desire to render it as a document. I think this might be because :exports none|both|source is currently not implemented for source code blocks, I will try to get this included in the next version of the gem. Thanks for the feedback, and please if you find another issue let me know by creating an issue :) Regards, - Wally On Mon, Feb 24, 2014 at 5:33 PM, Juan Reyero joa...@gmail.com wrote: On Mon, Feb 24, 2014 at 8:39 AM, Waldemar Quevedo waldemar.quev...@gmail.com wrote: It is rather annoying that github understands the org syntax but not quite, so the sources appear almost but not quite right. I maintain the parser that is being by Github = https://github.com/wallyqs/org-ruby If you let me now the issues I can try to fix them, (or PRs are also welcome) Sorry I sounded dismissive. You are doing an awesome job, it's amazing how much it did get right. My problem is that I am trying to share my sources as code, not as documentation. I would like my .org files to be treated as you would treat Python code, shown as they are and syntax-highlighted. If you parse them you will inevitably miss the context I am relying upon to render them properly (like when you ---rightly--- assume that html should be left standing, but what I wrote expects a jekyll post-process). People visiting the repository will most likely be interested in what I actually wrote, not in its rendering as a document. Close to what you get when you select Raw, but syntax-highlighted. This is what I want the repository for; the document is somewhere else. That said, the one place where the translation fails is when the source code of babel snippets should not be exported. Again, probably due to the tension between the need to show the file's content and the desire to render it as a document. I have this example where you can use `#+layout:` instead of YAML. https://github.com/wallyqs/yet-another-jekyll-org-template https://github.com/eggcaker/jekyll-org/blob/master/convert.rb#L30 Thank you for the pointer. Best, jm On Mon, Feb 24, 2014 at 4:24 AM, Juan Reyero joa...@gmail.com wrote: Greetings, I've solved a couple of bugs in the Leanpub[1] markdown exporter[2] (cross-links within the book using ids were not working, and footnotes containing a colon neither). As far as I can tell using Orgmode and Leanpub to publish books is now quite feasible, and produces rather nice results. I have also published the sources for my book, The Hacker Ways[3], at https://github.com/juanre/hacker-ways It is rather annoying that github understands the org syntax but not quite, so the sources appear almost but not quite right. Clone and open in Emacs to see what's going on. Best regards, jm -- http://greaterskies.com http://juanreyero.com [1] Leanpub.com is a very nice self-publishing platform. I am not associated with them, and they are not responsible for my code. [2] http://juanreyero.com/open/ox-leanpub/ [3] https://leanpub.com/hackerways/ -- http://greaterskies.com http://juanreyero.com
Re: [O] Writing your book with orgmode and publishing it on Leanpub
Hi, It is rather annoying that github understands the org syntax but not quite, so the sources appear almost but not quite right. I maintain the parser that is being by Github = https://github.com/wallyqs/org-ruby If you let me now the issues I can try to fix them, (or PRs are also welcome) I also noticed that you are using Jekyll with Org mode, so in case you are not a fan a adding YAML to your Org mode files I have this example where you can use `#+layout:` instead of YAML. https://github.com/wallyqs/yet-another-jekyll-org-template https://github.com/eggcaker/jekyll-org/blob/master/convert.rb#L30 Regards, - Waldemar On Mon, Feb 24, 2014 at 4:24 AM, Juan Reyero joa...@gmail.com wrote: Greetings, I've solved a couple of bugs in the Leanpub[1] markdown exporter[2] (cross-links within the book using ids were not working, and footnotes containing a colon neither). As far as I can tell using Orgmode and Leanpub to publish books is now quite feasible, and produces rather nice results. I have also published the sources for my book, The Hacker Ways[3], at https://github.com/juanre/hacker-ways It is rather annoying that github understands the org syntax but not quite, so the sources appear almost but not quite right. Clone and open in Emacs to see what's going on. Best regards, jm -- http://greaterskies.com http://juanreyero.com [1] Leanpub.com is a very nice self-publishing platform. I am not associated with them, and they are not responsible for my code. [2] http://juanreyero.com/open/ox-leanpub/ [3] https://leanpub.com/hackerways/
[O] Yet another Jekyll Org mode setup
Hello list, This is just to share my setup for using Jekyll and Org mode in case someone finds it useful... https://github.com/wallyqs/yet-another-jekyll-org-template What I like about this setup is that I can avoid having to add YAML front matter to Org mode posts by patching Jekyll with a plugin (link: https://github.com/wallyqs/jekyll-org/blob/master/convert.rb). It also disables Liquid templates since Org mode syntax can already cover some of those cases (like including files). In this setup I am using the Org-ruby parser to render into HTML for convenience, though it could also be possible to shell out to the Emacs Org mode parser, I just would have to catchup on how to do that in latest versions of Org (last time I did I used 'org-export-as-html', fix would be to shell out to Emacs here: https://github.com/wallyqs/jekyll-org/blob/master/convert.rb#L49). Cheers, - Waldemar
Re: [O] Getting checkboxes in HTML output?
fyi, this feature is heavily requested in Github for their markup project: https://github.com/github/markup/issues/208 So +1 on changing this behavior in Org mode markup itself, since there is already user demand which would validate this usage. On Thu, Nov 28, 2013 at 12:45 AM, Peter Davis p...@pfdstudio.com wrote: I noticed that HTML output contains [ ] and [X], just like the mark-up. Wouldn't it make sense to use actual unchecked or checked checkboxes in HTML? Is there a simple way to do this that I've overlooked? Thanks, -pd
Re: [O] Getting checkboxes in HTML output?
By the way TL;DR; from that Github thread: It seems that Markdown by default does not support read only checkboxes, and Github would not implement this behavior because they want to keep compatibility with other implementations of Markdown: https://github.com/github/markup/issues/208#issuecomment-24927799 I think that Org mode markup syntax is still in the stage where we can be liberal enough to change this kind of behavior which would be gladly received by many people (I hope!), specially since this would change only the HTML output. Some feedback on that thread on a feature like this: - +1 for readonly (checkboxes). It cannot be that hard... = https://github.com/github/markup/issues/208#issuecomment-27712872 - +1, i cannot live without checkboxes in readme! = https://github.com/github/markup/issues/208#issuecomment-27713464 - I'll die; Please add checkboxes = https://github.com/github/markup/issues/208#issuecomment-28001693 Cheers! - Waldemar On Thu, Nov 28, 2013 at 11:30 PM, Waldemar Quevedo waldemar.quev...@gmail.com wrote: fyi, this feature is heavily requested in Github for their markup project: https://github.com/github/markup/issues/208 So +1 on changing this behavior in Org mode markup itself, since there is already user demand which would validate this usage. On Thu, Nov 28, 2013 at 12:45 AM, Peter Davis p...@pfdstudio.com wrote: I noticed that HTML output contains [ ] and [X], just like the mark-up. Wouldn't it make sense to use actual unchecked or checked checkboxes in HTML? Is there a simple way to do this that I've overlooked? Thanks, -pd
Re: [O] org-mode based groupware wiki
Hello Torsten, - Enhance org-ruby? I would be glad to help out in this regard. About the completeness of the implementation of the Org mode ruby parser, it would be very helpful for me to have a set of examples that describe how each one of the features of Org mode Emacs exporter should be rendered in to HTML. I tried to do some work about this some time ago to identify the coverage of Org ruby HTML exporting compared to the Org mode Emacs exporter: https://github.com/wallyqs/org-mode-features/blob/master/features.org https://github.com/bdewey/org-ruby/tree/master/spec/html_examples/ Is there a set of examples of all the features from Org mode anywhere? By the way, recently Github has upgraded to the 0.8.1 version of the org-ruby gem, so Org mode rendering to HTML should have improved a lot (previous version they used was 0.5.3 so it took a while for them to evaluate upgrading the gem). https://github.com/github/markup/issues/186#issuecomment-25342870 Until I have identified the coverage, my current approach with developing Org ruby is 'on demand', so if you find and issue please submit to the issues tracker on Github: https://github.com/bdewey/org-ruby/issues Cheers, - Wally On Fri, Oct 4, 2013 at 8:57 PM, Torsten Wagner torsten.wag...@gmail.comwrote: Hi, recently I discovered gollumn [1] and was amazed to see that there is a software which allows non-orgers to work with / read my org-files and which even use git as the backend to get all save and nice together, even if working concurrently on the same files. I was wondering, because I never read about gollum in this ML and my search only revealed a very short three year old thread between Bastien and Eric Schulte. Despite that many of us was asking of possible ways how to use org as a groupware like environment. I guess this topic was discussed even more frequently over the last three years. Unfortunately, the main drawback, the usage of org-ruby [2] as org-mode parser still remains. I frighten that org-ruby only works on a small subset of the org-mode syntax and that even this might be a bit out-of-date. As far as I understood, org-mode in the meantime switched to a new exporter [3] and we got org-elements [4] and a heavy work towards standardization thanks to Nicolas Goaziou. What would be the best way to get the best out of the gollum idea and the new org-mode capabilities? - Skip gollumn and use (an updated) blorgit [5] (Does it have editor functionality?) ? - Enhance org-ruby? - Write a small script which creates a native html export from org-mode and hook this into gollumn? However, that would require emacs and org-mode being installed on the server side. For me gollums most important feature would be that people could use their web-browser and edit org-files. It might not be the most comfortable way of editing a org-file but a simple adding of a row into a table or rephrasing or adding a paragraph would be totally possible. It even might help to introduce people into using emacs and org-mode. It would be really nice to have such an easy access to org-files. Even hard-core orgers might like the idea to e.g. access and lightly modify there org-files on-the-go via smartphones and tablets without running a full emacs session. (I am aware of Mobileorg ;) ) I got a bit into detail here to hopefully kick-off some discussions. All the best Torsten [1] https://github.com/gollum/gollum [2] http://orgmode.org/worg/org-tutorials/org-ruby.html [3] http://orgmode.org/worg/dev/org-export-reference.html [4] http://orgmode.org/worg/org-api/org-element-api.html [5] http://orgmode.org/worg/blorgit.html
[O] FYI: Github updated Org ruby gem in github.com
Hello, I just noticed but recently Github upgraded the version of the Org ruby gem that they used in github.com : https://github.com/github/markup/issues/186#issuecomment-25342870 This update took a while to happen, but I hope you like the improvements of what the Org ruby contributors and I have worked on (version bump was 0.5.3 - 0.8.1 so many issues fixed) It seems that this update have been available for users, so feedback is appreciated. If you find rendering bugs or something wrong, please help me out filing a ticket with the issues if you want it fixed (or even better submit a pull request :) https://github.com/bdewey/org-ruby/issues Regards, - Waldemar
[O] Examples of Org mode HTML export
Hello Org mode users, In order to give better support to the Org ruby gem exporter, I've been trying to compile a set of exporting examples using Emacs Org mode exporter. and the work in progress is here: https://github.com/wallyqs/org-mode-features https://github.com/wallyqs/org-mode-features/blob/master/features.org Currently, the examples have been rendered with Org mode 7.8 exporter and latest Org ruby. I think that having these sort of examples rendering tests would be very helpful for developers of other parsers to check out the feature parity with the original one, and possibly also useful to check what has changed among different Org mode versions. Right now it is still very much incomplete, but feedback on missing features would be appreciated. Also thanks to Nicolas Goaziou again for this up, http://orgmode.org/worg/dev/org-syntax.org it has been very helpful. Regards, - Wally
[O] Google Summer of Code 2013?
Hello Org-mode community, Are there any plans to participate this year in Google Summer of Code? (Sort of short notice since the deadline is fastly approaching: March 29) http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Surely there are some ideas that could make it!
Re: [O] [RFC] Org syntax (draft)
Hey Nicolas, this looks very detailed and I think it could be useful for people trying to write other parsers implementations for org-mode. Thanks for sharing! By the way, does it exist somewhere a set of examples of Emacs org-mode - html conversion for all org-mode features? (How are changes from org-mode - html converstion from Emacs tested during development?) I am mantaining the org-ruby gem which is used to render org-mode texts to html, and currently there is no roadmap of features to implement for it. As a result, features and tweaks are added to the library as long as someone submits a ticket requesting the feature in Github. (Here is a list of the export features supported in case someone wants to take a look: https://github.com/bdewey/org-ruby/tree/master/spec/html_examples ) Having a set of examples features from org-mode would be very useful to see how much coverage other implementations of org-mode exporting features have. Cheers everyone, keep org-mode being an awesome tool :) - Waldemar On Sat, Mar 9, 2013 at 7:06 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Nicolas Goaziou n.goaz...@gmail.com writes: As discussed a few days ago, here is a document describing the complete Org syntax as read by the parser. I also added some comments. I am going to put the Org file on Worg, so anyone can update it and fix mistakes. [for the record, the org file mentionned by Nicolas is currently at http://orgmode.org/worg/dev/org-syntax.org] This looks truly awesome. I give some (naïve) comments below, from my non-expert point of view. Thank you for your comments. The paragraph is the unit of measurement. An element defines syntactical parts that are at the same level as a paragraph, i.e. which cannot contain or be included in a paragraph. An object is a part that could be included in an element. Greater elements are all parts that can contain an element. This is very clear but I'm slightly worried about confusion that might come from Greater element not being an element, and the word element being a common word : element means Element + Greater Element. It is to be understood as the opposite of object. I think there shouldn't be much ambiguity according to context. Empty lines belong to the largest element ending before them. For example, in a list, empty lines between items belong are part of the item before them, but empty lines at the end of a list belong to the plain list element. Is the word element (in /largest element ending.../) to be understood as an element from the above definition ? I guess not (this would require both list items and plain lists to be on the level 'element', from your example) Again, it's a shortcut for in the largest element or greater element ending before them. 1 Headlines and Sections A headline is defined as: ╭ │ STARS KEYWORD PRIORITY TITLE TAGS ╰ STARS is a string starting at column 0 and containing at least one asterisk (and up to `org-inlinetask-min-level' if `org-inlinetask' library is loaded). It’s the sole compulsory part of a headline. Perhaps it should be mentionned that STARS has to end by a space (see below). I agree. I suggest adding : The number of stars defines the level of the headline. Does it belong to the syntax definition? Level is how Org uses syntax internally. Also the sentence, although right, is misleading, because level definition also depends on `org-odd-levels-only'. KEYWORD is a TODO keyword, which have to belong to the list defined in `org-todo-keywords'. Case is significant. The option #+TODO: is used also. Then it should be ~org-todo-keywords-1~, which is where all TODO keywords are added eventually. PRIORITY is a priority cookie, i.e. a single letter preceded by a hash sign # and enclosed within square brackets. Case is significant. I suggest dropping Case is significant (or maybe give the whole story : IIRC, it is the ascii code of the given letter that is used as priority) I'm not sure that the purpose of this document should be to explain how syntax will be used. ╭ │ * I don't see a space character after that one in your email and it doesn't seem to be recognized as a headline by the exporter (hence my above suggestion) If the first word appearing in the title is `org-comment-keyword', the That should be `org-comment-string' I guess. Indeed. Btw, I think this variable should be a defconst, not a defcustom. It just makes things harder for little benefit. A headline contains directly at most one section, followed by any number of headlines. Only a section can contain another section. From what I understand, A section is delimited by two headlines (and buffer limits). [I initially thought it was by two headlines of the same level, which it is not from the structure example you give later.]
Re: [O] Please consider making a donation
I also donated a bit :) Thanks for the great work! - Waldemar On Sat, Aug 25, 2012 at 12:59 AM, Bastien b...@altern.org wrote: Hello all, I've been a freelancer for the last two months and I want to continue this experience. As such, my main challenge is to discipline myself not to spend too much time on Org -- because, as you can imagine, it *is* very tempting. So the more donation I receive, the more time I will have for Org. Any donation will first go into a new computer, as my lovely Thinkpad X61 is about to die. I you think of any Emacs/Org development you would like to sponsor, independantly from what's already existing, please send me an email. Thanks for your help! -- Bastien
Re: [O] [GSoC] Org-sync v0.2
Hello Aurélien, I just tried org-sync to fetch the issues from a project in github, this looks really useful! Not a big deal but I see that you have to set os-github-auth and call M-x os-import, os etc.. to use org-sync. Since the library is named org-sync, wouldn't it be better to base on the library name for these settings? e.g. `org-sync-github-auth`, `org-sync-import`... Cheers! - Waldemar On Fri, Aug 10, 2012 at 12:07 AM, Aurélien Aptel aurelien.ap...@gmail.comwrote: Hi all, I'm releasing a new version of Org-sync, the tool to sync Org documents with external bugtrackers/TODO-list system. There are functional (although not complete) backends for: - Github - Bitbucket - Redmine And I'm currently working on Remember the Milk. I've updated the installation procedure in the tutorial. It should be easier now if it was bothering you before. I've also made a short (~4mn) demo video covering the Bitbucket backend and conflicts. On a side note, making this video was a painful experience and I now realize the lack of good stable and free(dom) video editing software on Linux. Demo: https://www.youtube.com/watch?v=kbj6-j0teCY Tutorial: http://orgmode.org/worg/org-contrib/gsoc2012/student-projects/org-sync/tutorial/ Webpage: http://orgmode.org/worg/org-contrib/gsoc2012/student-projects/org-sync/index.html
Re: [O] README.org on github
Bastien, My name is Waldemar, and I am the current maintainer of the org-ruby gem. It looks like thanks to you (and many others who reported this) github/markup was updated so that it uses the 0.7.0 org-ruby version of the gem! https://github.com/github/markup/commit/b0144938d42c4e0b0f308c4e9cb1e5a23c155c72 I know that org-ruby html export implementation is far from perfect, but this will improve some things until a better solution that fits Github backed is build. For example, syntax highlighting #+begin_src blocks through Pygments should be available in Github with this release (in theory). Thanks a lot! - Wally On Sat, Aug 4, 2012 at 3:19 AM, Bastien b...@gnu.org wrote: Hi Tom, Tom Regner t...@goochesa.de writes: Maybe you could make yourself heard in the issue I opened [fn:1]; it is actually the third issue I opened, I never got a response and closed the other ones -- maybe my conclusions are wrong, and an update of org-ruby wouldn't help (that much) -- but with more people actually requesting better org-support, maybe it will get a bit more attention and progress. kine regards, Tom ? https://github.com/bdewey/org-ruby [fn:1] https://github.com/github/markup/issues/117 I pushed a +100 on this request. I doubt it will change anything, but who knows. The best way to make sure something happens is to stick to using org markup in github. -- Bastien
