Re: [Bash-completion-devel] Style guide (was: Re: [SCM] bash-completion branch, master, updated. 95cd673b5cbd5658cbf56a56a4113722aab92177)

2009-04-20 Thread Freddy Vulto
On Fri, Apr 17, 2009 at 9:52 PM, Ville Skyttä ville.sky...@iki.fi wrote: This is my first experience with asciidoc (tried 8.4.3), and I must say I'm not too impressed. Does this mean one needs to know the DocBook DTD and be able to write the docs in a asciidoc/plaintext format that kind of

Re: [Bash-completion-devel] Style guide (was: Re: [SCM] bash-completion branch, master, updated. 95cd673b5cbd5658cbf56a56a4113722aab92177)

2009-04-17 Thread Freddy Vulto
On Fri, Apr 17, 2009 at 9:52 PM, Ville Skyttä ville.sky...@iki.fi wrote: This is my first experience with asciidoc (tried 8.4.3), and I must say I'm not too impressed.  Does this mean one needs to know the DocBook DTD and be able to write the docs in a asciidoc/plaintext format that kind of

Re: [Bash-completion-devel] Style guide (was: Re: [SCM] bash-completion branch, master, updated. 95cd673b5cbd5658cbf56a56a4113722aab92177)

2009-04-15 Thread Freddy Vulto
On Tue, Apr 14, 2009 at 8:50 PM, Ville Skyttä ville.sky...@iki.fi wrote: Yeah... why not :).  Anyone want to write a style guide?  Here's a start for a table of contents, in no particular order: I'm in the process of writing documentation for the test suite and I'd like to propose using

[Bash-completion-devel] Style guide (was: Re: [SCM] bash-completion branch, master, updated. 95cd673b5cbd5658cbf56a56a4113722aab92177)

2009-04-14 Thread Ville Skyttä
On Tuesday 14 April 2009, David Paleino wrote: On Tue, 14 Apr 2009 18:24:23 +, Ville Skyttä wrote: @@ -884,8 +885,14 @@ _mount() | grep ^$cur ) ) else # probably Linux - COMPREPLY=( $( awk '! /^[ \t]*#/ {if ($2 ~ /\//)