On 3 August 2010 21:32, The Quiet Center <[email protected]> wrote: > > > On Aug 2, 9:46 pm, Stuart Rackham <[email protected]> wrote: >> Hi Terrance >> > > Hi Stuart! > >> On 29/07/10 03:34, metaperl wrote: >> >> > The complete new build-websites.sh is a bit more generic and allows >> > people to re-use the asciidoc website example for their own site a bit >> > easier. >> >> Is the bash -x option an undocumented option? I can't find it on the bash >> man page.
Yeah its well hidden down under the set built in command :-) > > wow. All it does is echo the command it is about to execute to STDOUT > > - http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_02_03.html > - http://stackoverflow.com/questions/951336/how-to-debug-a-bash-script > >> >> Long ago I adopted the .txt extension for AsciiDoc source. I experimented >> early >> on with custom extensions but it was too confusing -- AsciiDoc source files >> are >> readable plain text files > > heh, but so is restructured text, markdown, github flavored markdown, > python code, etc. > > Basically for emacs I can program it to start up asciidoc-mode when a > file has a .adoc extension. > > Of course, there are other ways to detect the mode of a file, such as > scanning the first few lines. But the first few lines of an asciidoc > file are not going to look very distinct from other plain-text markup > systems. I havn't tried it but I expect that if the first line was an Asciidoc comment containing the usual -*- mode:... -*- sequence Emacs should recognise it Cheers Lex > > which is what the .txt extension is for and all text >> edits recognize and open .txt files. I also wanted to be able to pass around >> AsciiDoc files for others to read without confusing them with "What on earth >> is >> this file with the funny extension he's sent me? How do I open it? Is it >> safe to >> open?". >> >> My preference is to stick unambiguously with the .txt extension for AsciiDoc >> source files. See >> alsohttp://en.wikipedia.org/wiki/Text_fileandhttp://en.wikipedia.org/wiki/Plain_text). >> Maybe I should put this in an FAQ. > > it's certainly an interesting topic. > >> >> The easiest way is to attach diff files (unified context -u) and post to the >> discussion list. > > got it. > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/asciidoc?hl=en. > > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
