Re: [fossil-users] Using ticket system from command line
On Sat, 15 May 2010 07:11:35 -0400, Richard Hipp d...@sqlite.org wrote:
On Sat, May 15, 2010 at 6:51 AM, Gour wrote:
On Sat, 15 May 2010 11:30:40 +0100
Eric == Eric wrote:
Eric Otherwise, lack of standard wiki
Eric
Eric I continue to be amazed by all this nonsense about the wiki.
s/standard/complete/g
HTML is not complete enough? What do you want to do (or for that
matter what does any other wiki system do) that you can't do (in a more
standard way, I should add) with HTML?
well I kind of like this
|c table caption
|=2 head|= head
| data|
[[http://bouml.free.fr/|{{http://bouml.free.fr/images/bouml_titre.gif}}]]|
data
| data| {{http://bouml.free.fr/images/bouml_titre.gif|bouml image}}| data
versus
The philosophy of Fossil Wiki is to provide simple and common wiki-style
markup to accomplish 90% of what you need, then allow the use of HTML
for
the other 10%. HTML is seen as superior to increasingly arcane Wiki
formatting for the complicated stuff because (1) most programmers
already
know HTML so there is nothing new to learn, (2) HTML is a standard, and
(3) HTML allows you to do just about whatever you want to do in a web
browser - it is complete. You can disagree with the design choice
here. But please distinguish between a lack of understanding and a
disagreement.
There is one argument for using wiki I haven't seen.
It can be a meta language. You can opt to translate
# Item1
html olliItem1/li/ol
docbook orderedlistlistitemItem1/listitem/orderedlist
ODF listlist-itemItem1/list-item/list
Arguable I used a very simple example.
___
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] Using ticket system from command line
On Sat, May 15, 2010 at 5:02 am Gour g...@gour-nitai.com wrote: Otherwise, lack of standard wiki I continue to be amazed by all this nonsense about the wiki. * There is _no_ standard wiki. The small number of formats I can write fluently is not the same an the small number of formats you can write fluently. All you can ever achieve is to change the probability that someone will have to learn a new format. I do not think the gain (for an unknown number of unknown people) is worth the effort. * The issue is further clouded by the assumption that the wiki is about project documentation. I think it is about quick notes, discussions, and, at most, snippets of draft documentation. I want my project documentation (user guides, developer guides, whatever else, and especially specifications) to be proper files in the repository, just like the source code. A project can choose to use wiki format for this (as has happened with the fossil project), but I don't want my SCM tool to dictate my documentation format, even though I may then need to find or create a web-delivery method for my chosen format. email interface for the tracker I don't know if it has a name but there seems to be a law that once a software product is sufficiently popular people want it to do everything, i.e. they want it to be a platform. Fossil sending email - probably OK. Fossil handling incoming mail - far too complicated and too far away from Fossil's core purpose, in my opinion. Eric ___ 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] Using ticket system from command line
On Sat, 15 May 2010 11:30:40 +0100 Eric == Eric wrote: Eric Otherwise, lack of standard wiki Eric Eric I continue to be amazed by all this nonsense about the wiki. s/standard/complete/g Eric email interface for the tracker Eric I don't know if it has a name but there seems to be a law that Eric once a software product is sufficiently popular people want it to Eric do everything, i.e. they want it to be a platform. My mistake... s/email/cli/g I believe it's reasonable to expect that in distributed tracker once can create tickets via cli while being offline and push to the 'central' repo when online. Excuse me for creating unnecessary disturbance... Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 signature.asc Description: PGP signature ___ 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] Using ticket system from command line
On Sat, May 15, 2010 at 6:51 AM, Gour g...@gour-nitai.com wrote: On Sat, 15 May 2010 11:30:40 +0100 Eric == Eric wrote: Eric Otherwise, lack of standard wiki Eric Eric I continue to be amazed by all this nonsense about the wiki. s/standard/complete/g HTML is not complete enough? What do you want to do (or for that matter what does any other wiki system do) that you can't do (in a more standard way, I should add) with HTML? The philosophy of Fossil Wiki is to provide simple and common wiki-style markup to accomplish 90% of what you need, then allow the use of HTML for the other 10%. HTML is seen as superior to increasingly arcane Wiki formatting for the complicated stuff because (1) most programmers already know HTML so there is nothing new to learn, (2) HTML is a standard, and (3) HTML allows you to do just about whatever you want to do in a web browser - it is complete. You can disagree with the design choice here. But please distinguish between a lack of understanding and a disagreement. Eric email interface for the tracker Eric I don't know if it has a name but there seems to be a law that Eric once a software product is sufficiently popular people want it to Eric do everything, i.e. they want it to be a platform. My mistake... s/email/cli/g I believe it's reasonable to expect that in distributed tracker once can create tickets via cli while being offline and push to the 'central' repo when online. The fossil ui command lets you do exactly that. I use Fossil daily for work on SQLite. I normally enter and/or edit tickets off-line (using the fossil ui command) then push them up to the servers later. This is the standard way of working with Fossil. I am sorry that you were left with the impression that one had to be online and connected to a server to work with Fossil tickets. I thought the documentation was reasonably clear on the point that tickets and wiki could be edited offline. Perhaps I can find a way to make it clearer. Excuse me for creating unnecessary disturbance... Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- - D. Richard Hipp d...@sqlite.org ___ 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] Using ticket system from command line
On Sat, 15 May 2010 07:11:35 -0400 Richard == Richard Hipp wrote: Dear Richard, Richard HTML is not complete enough? What do you want to do (or for Richard that matter what does any other wiki system do) that you can't Richard do (in a more standard way, I should add) with HTML? it is not point that HTML is not complete, but it is simply too cumbersome to write documentation in HTML. Probably, that's why we have wikis and so many different kind of markup languages. For the same reason (cumberness), I do not use e.g. DocBook, but prefer more readable formats like Markdown and/or RestructuredText. Richard The philosophy of Fossil Wiki is to provide simple and common Richard wiki-style markup to accomplish 90% of what you need, then Richard allow the use of HTML for the other 10%. Fossil's wiki is simply too limiting. E.g. Only a single level of bullet list is supported by wiki. For nested lists, use HTML. is not acceptable for the writing docs, but I believe there is no need to repeat oneself since there are so many messages which were discussing the issues and several people expressed their sentiments in regard. RichardHTML is seen as superior to increasingly arcane Wiki Richard formatting for the complicated stuff because (1) most Richard programmers already know HTML so there is nothing new to Richard learn, Why you restrict usage of (Fossil) SCM only to programmers? I use SCM for ALL my writings and majority of that is not the code. Richard (2) HTML is a standard, Yes, afaict, people desiring to see 'standard' wiki were/are ready to accept ANY COMPLETE wiki since it means support for converting, editing-modes etc, i.e. one can do ALL the documentation in the one wiki markup. Richard (3) HTML allows you to do just about whatever you want to do Richard in a web browser - it is complete. The point is that by using e.g. Markdown/reST (along with Pandoc) it enables me to target not only HTML, but many other formats like PDF (check http://johnmacfarlane.net/pandoc/) Richard You can disagree with the design choice here. I do. :-) Richard But please distinguish between a lack of understanding and a Richard disagreement. I understand it is your choice since Fossil is your offspring. Richard The fossil ui command lets you do exactly that. I use Richard Fossil daily for work on SQLite. I normally enter and/or edit Richard tickets off-line (using the fossil ui command) then push Richard them up to the servers later. btw, what do you think about: http://www.fossil-scm.org/index.html/tktview?name=3e3018e96f ? RichardThis is the standard way of working with Fossil. Ahh... Richard I am sorry that you were left with the impression that one Richard had to be online and connected to a server to work with Richard Fossil tickets. I thought the documentation was reasonably Richard clear on the point that tickets and wiki could be edited Richard offline. Perhaps I can find a way to make it clearer. I believe there is no need to clarify documents...The problem was that I was so absorbed in cli-interface (reading roundup docs) that I completely forgot about 'fossil ui'. Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 signature.asc Description: PGP signature ___ 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] Using ticket system from command line
On Sat, May 15, 2010 at 8:23 AM, Gour g...@gour-nitai.com wrote: On Sat, 15 May 2010 07:11:35 -0400 Richard == Richard Hipp wrote: Dear Richard, Richard HTML is not complete enough? What do you want to do (or for Richard that matter what does any other wiki system do) that you can't Richard do (in a more standard way, I should add) with HTML? it is not point that HTML is not complete, but it is simply too cumbersome to write documentation in HTML. So it really comes down to a matter of personal preference. You say HTML is cumbersome. I say that Markdown, etc. are arbitrary and cumbersome. Different people have different ideas. And yet, by virtue of supporting HTML, the wiki in Fossil is both standard and complete, for reasonable meanings of those words. What you really mean to say is that the fossil wiki does not suit your tastes in wiki and you would prefer something different. It's an emacs versus vi thing. btw, what do you think about: http://www.fossil-scm.org/index.html/tktview?name=3e3018e96f ? Ticket change histories can be seen by following the links in the submenu bar at the top of the ticket display. Example: http://www.fossil-scm.org/index.html/tkthistory/49929a3557 http://www.fossil-scm.org/index.html/tkttimeline?name=49929a3557 -- - D. Richard Hipp d...@sqlite.org ___ 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] Using ticket system from command line
HTML is complete, We agree. But then why these special formatting rules, which are very basic and too incomplete? http://fossil-scm.org/index.html/wiki_rules It will be preferred if Wiki pages are instead stored as .html files and not use any non-HTML formats. - Altu -Original Message- From: Richard Hipp d...@sqlite.org To: fossil-users@lists.fossil-scm.org Sent: Sat, May 15, 2010 7:18 pm Subject: Re: [fossil-users] Using ticket system from command line On Sat, May 15, 2010 at 8:23 AM, Gour g...@gour-nitai.com wrote: On Sat, 15 May 2010 07:11:35 -0400 Richard == Richard Hipp wrote: Dear Richard, Richard HTML is not complete enough? What do you want to do (or for Richard that matter what does any other wiki system do) that you can't Richard do (in a more standard way, I should add) with HTML? it is not point that HTML is not complete, but it is simply too cumbersome to write documentation in HTML. So it really comes down to a matter of personal preference. You say HTML is cumbersome. I say that Markdown, etc. are arbitrary and cumbersome. Different people have different ideas. And yet, by virtue of supporting HTML, the wiki in Fossil is both standard and complete, for reasonable meanings of those words. What you really mean to say is that the fossil wiki does not suit your tastes in wiki and you would prefer something different. It's an emacs versus vi thing. btw, what do you think about: http://www.fossil-scm.org/index.html/tktview?name=3e3018e96f ? Ticket change histories can be seen by following the links in the submenu bar at the top of the ticket display. Example: http://www.fossil-scm.org/index.html/tkthistory/49929a3557 http://www.fossil-scm.org/index.html/tkttimeline?name=49929a3557 -- - D. Richard Hipp d...@sqlite.org ___fossil-users mailing listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users ___ 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] Using ticket system from command line
For documentation I prefer to use LyX and then produce a PDF and put that into the repository. Then you just have a link from a wiki page of the form: [http:doc/tip/documentation/my_user_man.pdf | User Manual] . The user then has a PDF (with active links in the table of contents and index) of the documentation. The advantage of this is that the user can at his option download the whole thing and print it very easily. Also the formatting if critical can absolutely controlled and doesn't depend on browser issues. This is my preference in documentation as I try to keep all my docs in this form (I actually find iTunes is really great for storing PDFs.) I agree with Richard that the Wiki is great for notes and shorter things but for longer forms and where I want active links in the TOC and index I would rather some other program did that for me. --jim On May 15, 2010, at 9:48 AM, Richard Hipp wrote: On Sat, May 15, 2010 at 8:23 AM, Gour g...@gour-nitai.com wrote: On Sat, 15 May 2010 07:11:35 -0400 Richard == Richard Hipp wrote: Dear Richard, Richard HTML is not complete enough? What do you want to do (or for Richard that matter what does any other wiki system do) that you can't Richard do (in a more standard way, I should add) with HTML? it is not point that HTML is not complete, but it is simply too cumbersome to write documentation in HTML. So it really comes down to a matter of personal preference. You say HTML is cumbersome. I say that Markdown, etc. are arbitrary and cumbersome. Different people have different ideas. And yet, by virtue of supporting HTML, the wiki in Fossil is both standard and complete, for reasonable meanings of those words. What you really mean to say is that the fossil wiki does not suit your tastes in wiki and you would prefer something different. It's an emacs versus vi thing. btw, what do you think about: http://www.fossil-scm.org/index.html/tktview?name=3e3018e96f ? Ticket change histories can be seen by following the links in the submenu bar at the top of the ticket display. Example: http://www.fossil-scm.org/index.html/tkthistory/49929a3557 http://www.fossil-scm.org/index.html/tkttimeline?name=49929a3557 -- - D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Using ticket system from command line
I don't understand why you have to write your docs in Fossil's formatting language. Isn't that equivalent to being constrained to a particular programming language by the scm system? -- Michael L. Barrow On May 15, 2010, at 5:23, Gour g...@gour-nitai.com wrote: On Sat, 15 May 2010 07:11:35 -0400 Richard == Richard Hipp wrote: Dear Richard, Richard HTML is not complete enough? What do you want to do (or for Richard that matter what does any other wiki system do) that you can't Richard do (in a more standard way, I should add) with HTML? it is not point that HTML is not complete, but it is simply too cumbersome to write documentation in HTML. Probably, that's why we have wikis and so many different kind of markup languages. For the same reason (cumberness), I do not use e.g. DocBook, but prefer more readable formats like Markdown and/or RestructuredText. Richard The philosophy of Fossil Wiki is to provide simple and common Richard wiki-style markup to accomplish 90% of what you need, then Richard allow the use of HTML for the other 10%. Fossil's wiki is simply too limiting. E.g. Only a single level of bullet list is supported by wiki. For nested lists, use HTML. is not acceptable for the writing docs, but I believe there is no need to repeat oneself since there are so many messages which were discussing the issues and several people expressed their sentiments in regard. RichardHTML is seen as superior to increasingly arcane Wiki Richard formatting for the complicated stuff because (1) most Richard programmers already know HTML so there is nothing new to Richard learn, Why you restrict usage of (Fossil) SCM only to programmers? I use SCM for ALL my writings and majority of that is not the code. Richard (2) HTML is a standard, Yes, afaict, people desiring to see 'standard' wiki were/are ready to accept ANY COMPLETE wiki since it means support for converting, editing-modes etc, i.e. one can do ALL the documentation in the one wiki markup. Richard (3) HTML allows you to do just about whatever you want to do Richard in a web browser - it is complete. The point is that by using e.g. Markdown/reST (along with Pandoc) it enables me to target not only HTML, but many other formats like PDF (check http://johnmacfarlane.net/pandoc/) Richard You can disagree with the design choice here. I do. :-) Richard But please distinguish between a lack of understanding and a Richard disagreement. I understand it is your choice since Fossil is your offspring. Richard The fossil ui command lets you do exactly that. I use Richard Fossil daily for work on SQLite. I normally enter and/or edit Richard tickets off-line (using the fossil ui command) then push Richard them up to the servers later. btw, what do you think about: http://www.fossil-scm.org/index.html/tktview?name=3e3018e96f ? RichardThis is the standard way of working with Fossil. Ahh... Richard I am sorry that you were left with the impression that one Richard had to be online and connected to a server to work with Richard Fossil tickets. I thought the documentation was reasonably Richard clear on the point that tickets and wiki could be edited Richard offline. Perhaps I can find a way to make it clearer. I believe there is no need to clarify documents...The problem was that I was so absorbed in cli-interface (reading roundup docs) that I completely forgot about 'fossil ui'. Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Using ticket system from command line
You can create tickets now (not via cli, but via the local web interface) and sync them. What's wrong with the current capability? -- Michael L. Barrow On May 15, 2010, at 3:51, Gour g...@gour-nitai.com wrote: On Sat, 15 May 2010 11:30:40 +0100 Eric == Eric wrote: Eric Otherwise, lack of standard wiki Eric Eric I continue to be amazed by all this nonsense about the wiki. s/standard/complete/g Eric email interface for the tracker Eric I don't know if it has a name but there seems to be a law that Eric once a software product is sufficiently popular people want it to Eric do everything, i.e. they want it to be a platform. My mistake... s/email/cli/g I believe it's reasonable to expect that in distributed tracker once can create tickets via cli while being offline and push to the 'central' repo when online. Excuse me for creating unnecessary disturbance... Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Using ticket system from command line
On Sat, 15 May 2010 09:48:01 -0400 Richard == Richard Hipp wrote: Richard Ticket change histories can be seen by following the links in Richard the submenu bar at the top of the ticket display. Example: Thank you. I missed it (somehow). Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 signature.asc Description: PGP signature ___ 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] Using ticket system from command line
On Aug 5, 2009, at 11:06 PM, Alec Clews wrote: The fossil CLI seems to have limited functionality to create and manage tickets (like the fossil wiki command). Is there some way to achieve this? What kinds of commands would you suggest? D. Richard Hipp d...@hwaci.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] Using ticket system from command line
On 06/08/09 23:07, D. Richard Hipp wrote: On Aug 5, 2009, at 11:06 PM, Alec Clews wrote: The fossil CLI seems to have limited functionality to create and manage tickets (like the fossil wiki command). Is there some way to achieve this? What kinds of commands would you suggest? Create Update status (or any field?) Append to text field List all tickets Find ticket Dump a ticket (erhh... I think that would cover it. Closing a ticket is just a case of updating the status) On a similiar note it would be useful to have an wiki subcommand that does an append, although I figure That would make is possible to add powerful email integrations -- Alec Clews Personalalec.cl...@gmail.com Melbourne, Australia. Jabber: aleccl...@jabber.org.auPGPKey ID: 0x9BBBFC7C Blog http://alecthegeek.wordpress.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] Using ticket system from command line
On Fri, Aug 7, 2009 at 12:18 AM, Alec Clews aleccl...@gmail.com wrote: On a similiar note it would be useful to have an wiki subcommand that does an append, although I figure i think an append could be constructed by conceptually doing: wiki export PageName TEMPFILE wiki append [-c] [-m comment string | -f INPUT_FILENAME] TEMPFILE wiki commit PageName TEMPFILE where: * option -m = comment string * option -f = comments read from filename. * option -c = Comment flag to prepend this to the append: emCommend added to LINK_TO_OLD_VERSION by WHOEVER on TIMESTAMP:/em The only new command there is append, but the others might need to be refactored to be reusable in that context. (The code is in src/wiki.c (grep for _cmd_), in case you'd like to take a whack at it.) :-? -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
