Re: [fossil-users] Asciidoc(tor) Fossil
On Sun, 17 Aug 2014 13:49:01 -0400 Ron W ronw.m...@gmail.com wrote: And it could be even easier than it is, now, per my suggested enhancement to Fossil. Where can one read about it? Sincerely, Gour -- In this endeavor there is no loss or diminution, and a little advancement on this path can protect one from the most dangerous type of fear. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Mon, Aug 18, 2014 at 4:46 PM, Gour g...@atmarama.net wrote: On Sun, 17 Aug 2014 13:49:01 -0400 Ron W ronw.m...@gmail.com wrote: And it could be even easier than it is, now, per my suggested enhancement to Fossil. Where can one read about it? In my message in this thread on Thu, 14 Aug 2014 18:47:54 -0400 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Fri, Aug 15, 2014 at 12:55 AM, Gour g...@atmarama.net wrote: My intention was not to suggest using AsciiDoc as 'alternative' to the Fossil's Nor mine. wiki (I had enough in the past when asking for markdown support), but only if there is some simple way to make it render AsciiDoc documents (for those already using such markup) via Asciidoctor.js. And it could be even easier than it is, now, per my suggested enhancement to Fossil. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 09:56:32 +0200 Stephan Beal sgb...@googlemail.com wrote: You can in fact do that with the JSON API. i've been serving Google Code-format wiki pages this way for a a couple years now: Very interersting! Does it mean there is nothing interesting in Asciidoctor.js to make Fossil 'speak' AsciiDoc? Sincerely, Gour -- One who sees inaction in action, and action in inaction, is intelligent among men, and he is in the transcendental position, although engaged in all sorts of activities. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 10:14 AM, Gour g...@atmarama.net wrote: Does it mean there is nothing interesting in Asciidoctor.js to make Fossil 'speak' AsciiDoc? Correct, but it also means that if you try to view those pages in the fossil wiki, they will be mangled. For those 3 sites i use only my custom front-end for the wiki and store only GoCo-format docs in the wiki. If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc. What we'll need: First, i need to go get reacquainted with that code. i haven't touched it in... [stephan@host:~/cvs/fossil/fwiki/js/fijet]$ f-timeline -n 2 checkin [c2546ff7595d] @ 2013-01-02 16:18:00 by [stephan] branch [trunk] *CURRENT* fix(?) for wrong friendly time calculation for =26 weeks in the past. checkin [187257d5123b] @ 2012-05-05 09:50:31 by [stephan] branch [trunk] removed some debug output. in a long time. IIRC, it is capable of dispatching to renderers depending on rules (page name patterns, IIRC), but i can't seem to find proof of that at the moment. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 10:32:20 +0200 Stephan Beal sgb...@googlemail.com wrote: Correct, but it also means that if you try to view those pages in the fossil wiki, they will be mangled. That's clear, but originally I was thinking about https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc. You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool...the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Sincerely, Gour -- You have a right to perform your prescribed duty, but you are not entitled to the fruits of action. Never consider yourself the cause of the results of your activities, and never be attached to not doing your duty. http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 12:24 PM, Gour g...@atmarama.net wrote: https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; Sorry, i missed that part. i'm glad to see someone gets some use out of the wiki CLI commands (IIRC those were my first contributions to Fossil). You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. Just let me know. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool... _Somewhere_ (in a fossil repo, nonetheless) i've got an example of it, possibly in another source tree. It can be done, i just don't know if it's in that particular tree or not. i explicitly remember adding renderers for shell code and plain text at one point. the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Indeed. It's called LaTeX ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 12:39 PM, Stephan Beal sgb...@googlemail.com wrote: i'm glad to see someone gets some use out of the wiki CLI commands (IIRC those were my first contributions to Fossil). Fossil says otherwise, though: http://fossil-scm.org/index.html/timeline?ym=2008-02n=35y=au=stephan They came soon after, though: http://fossil-scm.org/index.html/timeline?ym=2008-05n=26y=au=stephan -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 12:24:24 +0200, Gour g...@atmarama.net wrote: On Thu, 14 Aug 2014 10:32:20 +0200 Stephan Beal sgb...@googlemail.com wrote: Correct, but it also means that if you try to view those pages in the fossil wiki, they will be mangled. That's clear, but originally I was thinking about https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; If you like, as a repayment for saving me weeks of work writing/debugging another ncurses script binding (by introducing me to termbox), we can try to get one set up for you with Asciidoc. You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool...the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? asciidoc sure is a very good markup language and much more capable than markdown. so it would be very nice to see it supported for wiki markup in fossil. books: I wouldn't do that, probably, since while it is quite easy to get decent pdf-formatted output it is a pain to customize it (both with the FOP and the dblatex backends) beyond very basic things. I thus quite probably still would prefer the LaTeX route for serious typesetting. but overall asciidoc is really great. just my 2c... Sincerely, Gour -- Using Opera's revolutionary email client: http://www.opera.com/mail/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 09:56:32AM +0200, Stephan Beal wrote: On Thu, Aug 14, 2014 at 9:27 AM, Gour [1]g...@atmarama.net wrote: Now the interesting part in regard to is is Asciidoctor.js � - a fully-functional version of Asciidoctor that works in any JavaScript environment, such as a web browser or Node.js., so I wonder whether there is some possibility to make it integrate it with Fossil in order to enjoy combination of Asciidoc markup + Fossil? You can in fact do that with the JSON API. i've been serving Google Code-format wiki pages this way for a a couple years now: [2]http://fossil.wanderinghorse.net/wikis/ all of those use the JSON API to serve GoCo-format pages, which then get rendered on the client side. May be it would be more simple (if possible) to just modify fossil skins related configuration (header, footer, css, ...) to use Asciidoctor.js. If it is possible for google-code-prettify for syntax highlighting, I guess it could be for Asciidoctor.js. It's only my 2 cents since I don't know much about Asciidoctor.js. note: For google-code-prettify, I use my own skin based on the google-code skin from here: http://fossil.include-once.org/fossil-skins/index That I modify to don't have to link to google-code-prettify js script from google, I've integrated it to my repository instead so it can be use on a local network without internet access.. I've also removed dependency on jquery. Regards, -- Martin G. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 12:39:06 +0200 Stephan Beal sgb...@googlemail.com wrote: Indeed. It's called LaTeX ;). I like LaTeX's output and used it for printed books along with LyX, but it's simply not very readable. Sincerely, Gour -- The humble sages, by virtue of true knowledge, see with equal vision a learned and gentle brāhmana, a cow, an elephant, a dog and a dog-eater. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 12:50:21 +0200 j. van den hoff veedeeh...@googlemail.com wrote: I thus quite probably still would prefer the LaTeX route for serious typesetting. but overall asciidoc is really great. Don't forget there is Pandoc. ;) Sincerely, Gour -- One who is not disturbed in mind even amidst the threefold miseries or elated when there is happiness, and who is free from attachment, fear and anger, is called a sage of steady mind. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 3:39 AM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Aug 14, 2014 at 12:24 PM, Gour g...@atmarama.net wrote: https://github.com/srackham/asciidoc-fossil-backend which says: https://github.com/srackham/asciidoc-fossil-backend; Sorry, i missed that part. i'm glad to see someone gets some use out of the wiki CLI commands (IIRC those were my first contributions to Fossil). You're very generous, but let's wait a bit if there is some more interest to integrate/use Asciidoc(tor) with Fossil by using Asciidoctor.js. Just let me know. If indeed it does support that, then we can plug asciidoc in with little work. i _know_ somewhere i have an example which dispatches to a different renderer based on file type, but that might have been in a different source tree (i can't see to find an example of it in this one). That would be really cool... _Somewhere_ (in a fossil repo, nonetheless) i've got an example of it, possibly in another source tree. It can be done, i just don't know if it's in that particular tree or not. i explicitly remember adding renderers for shell code and plain text at one point. the more I play with Asciidoc I see it's really capable even to the extent of writing books using it. (I read somewhere that these days it's possible for author writing book in AsciiDoc and submit it to O'Reilly.) So, rich markup + Fossil for keeping it under DVCS sounds as great combo for writers, isn't it? Indeed. It's called LaTeX ;). I think asciidoc is a lowest common denominator, reasonable for many use cases, 80/20 rule compliant substitute for LaTeX with the massive benefit that the source document is usable as text documentation as-is where LaTeX source is absolutely NOT readable as stand-alone documentation by anyone other than the author. I would use an asciidoc(tor) plugin or a recipe for using asciidoc(tor) from within fossil. I already have a lot of documentation in asciidoc format. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority... ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
Personally, I don't see much need for fossil to have built-in support for rendering anything much richer than its own wiki or the vanilla markdown we have now. I happily use fossil as-is for storing writing projects. Lately I write in a combination of markdown and LaTeX (usually LuaLaTeX, specifically), using Pandoc to do the needed transformation and either replacing its stock template or supplying my own outer .tex file to assemble the finished product. On 8/14/2014 5:41 AM, Gour wrote: On Thu, 14 Aug 2014 12:50:21 +0200 j. van den hoff veedeeh...@googlemail.com wrote: I thus quite probably still would prefer the LaTeX route for serious typesetting. but overall asciidoc is really great. Don't forget there is Pandoc. ;) I tried to like ASCIIDoc, but the whole FOP framework and its assumption that a giant Java application is ok just in my way too often. I do wish for finer control over tables and figures from time to time, so far I've done what I needed by at worst post-processing the TeX emitted by Pandoc and often just be dropping literal TeX in the markdown source. -- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, Aug 14, 2014 at 3:27 AM, Gour g...@atmarama.net wrote: the topic of the markup in Fossil is quite an old one and in the past there was a thread about using AsciiDoc markup which can be rendered with I looked at AsciiDoc. In theory, it's nice, but it appears to have gathered a huge number of features over the years. It really appears to try to be LaTeX Light. Also, it uses [ and ] for purposes other than wiki links (as many wiki mark-ups use) , so using it as an alternative to either Fossil's native wiki mark-up or to mark-down would be awkward for many users. Last I checked (2 years ago?), other than the JASON API, Fossil's web interface did not provide an easy means for a client side mark-up renderer to identify the file content. While the JSON API is very nice, I still think there would be value in Fossil's generated HTML putting a clearly identifiable div around the content. Maybe like: div class=user_content filename=filename.ext Then a client side handler could easily extract both the content and the filename/extension with which it could dispatch the appropriate renderer. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 18:47:54 -0400 Ron W ronw.m...@gmail.com wrote: I looked at AsciiDoc. In theory, it's nice, but it appears to have gathered a huge number of features over the years. It really appears to try to be LaTeX Light. As it was already said, readability counts here. Also, it uses [ and ] for purposes other than wiki links (as many wiki mark-ups use) , so using it as an alternative to either Fossil's native wiki mark-up or to mark-down would be awkward for many users. My intention was not to suggest using AsciiDoc as 'alternative' to the Fossil's wiki (I had enough in the past when asking for markdown support), but only if there is some simple way to make it render AsciiDoc documents (for those already using such markup) via Asciidoctor.js. Sincerely, Gour -- From wherever the mind wanders due to its flickering and unsteady nature, one must certainly withdraw it and bring it back under the control of the self. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Asciidoc(tor) Fossil
On Thu, 14 Aug 2014 14:29:55 -0700 Ross Berteig r...@cheshireeng.com wrote: Personally, I don't see much need for fossil to have built-in support for rendering anything much richer than its own wiki or the vanilla markdown we have now. I agree and as I already replied the idea is just to be able to *render* documentation written in AsciiDoc markup using Asciidoctor.js, not adding AsciiDoc as another 'built-in' markup. I happily use fossil as-is for storing writing projects. Lately I write in a combination of markdown and LaTeX (usually LuaLaTeX, specifically), using Pandoc to do the needed transformation and either replacing its stock template or supplying my own outer .tex file to assemble the finished product. The possible advantage of being able to directly render AsciiDoc documents via AsciiDoctor.js is that I could happily use my (relatively cheap) hosting and have nicely looking documents in my repo *without* the need to have/install the usual toolchain used to built html from e.g. LaTeX. I believe you agree that built-in wiki markup as well as plain markdown are not suitable for more complex docs. Sincerely, Gour -- Therefore, without being attached to the fruits of activities, one should act as a matter of duty, for by working without attachment one attains the Supreme. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
