Hmmm, I previously tried all combinations including full escaping and it didn't work. But yours is working. When I have time I'll go back and try again and see if there was something different.
Thanks. Ted > On Oct 20, 2015, at 8:18 PM, Lex Trotman <[email protected]> wrote: > > On 21 October 2015 at 10:55, Ted Toal <[email protected]> wrote: >> No, it doesn't. I had tried that already. When I run yours, it works. >> Mine is in a different context, which must be altering how it is processed. >> Perhaps I'm misundering something important about the asciidoc formatting. >> Here's the text that does not work for me: > > > Yes, quoting depends on the characters around the quote characters (if > they are themselves quotes, word chars, whitespace, start/end of line, > if the quotes are nested). So there is no one "this incantation will > work in all situations". > > The following only took a little trialling to work for me. > > = Hi > > == Chapter 1 > \### > > . *Open the allParameters.XY file in your plain text editor* > + > -- > If you are in a hurry, you don't need to read anything in the file, but > can simply *search for "\#\#\#"*, which are comment lines > can simply *search for \#\#\#* which are comment lines > can simply *search for "\#@@"*, which are comment lines > can simply search for "\#\#\#", which are comment lines > can simply search for \#\## which are comment lines > can simply search for "#@@", which are comment lines > marking items that may need to be changed. > -- > >> >> >> >> = Hi >> >> == Chapter 1 >> \### >> >> . *Open the allParameters.XY file in your plain text editor* >> + >> -- >> If you are in a hurry, you don't need to read anything in the file, but >> can simply *search for "\###"*, which are comment lines >> can simply *search for \###* which are comment lines >> can simply *search for "#@@"*, which are comment lines >> can simply search for "\###", which are comment lines >> can simply search for \### which are comment lines >> can simply search for "#@@", which are comment lines >> marking items that may need to be changed. >> -- >> >> >> >> >> >> On Oct 20, 2015, at 5:45 PM, Sapphira Armageddos >> <[email protected]> wrote: >> >> I tried escaping just one of the three and it seems to work just fine, at >> least with this source text: https://ptpb.pw/dTzw >> >> Let me know if it works for you too. >> >> >> On Saturday, September 26, 2015 at 7:00:28 AM UTC-7, Ted Toal wrote: >>> >>> No, I tried that. I tried all combinations of escaping two of three. I >>> didn't try escaping only one of the three because that seemed unlikely to >>> work. >>> >>> ted >>> >>> On Sep 25, 2015, at 9:30 PM, Lex Trotman <[email protected]> wrote: >>> >>> Without testing it I think escape the first two. >>> >>> Cheers >>> Lex >>> >>> On 26 September 2015 at 13:46, Ted Toal <[email protected]> wrote: >>> >>> And if I want three consecutive #'s how do I do it? >>> >>> >>> Ted Toal >>> >>> On Sep 25, 2015, at 3:10 PM, Lex Trotman <[email protected]> wrote: >>> >>> On 26 September 2015 at 06:03, Ted Toal <[email protected]> wrote: >>> Multiple pound or hash symbols in a row don't work right when each one is >>> escaped by a backslash character. The last one comes out in the formatted >>> text as having a backslash preceding it. >>> >>> For example, if the asciidoc contains \#\#\# >>> then the output shows ##\# >>> >>> >>> The backslash only has escaping properties if it is in front of a >>> construct that actually has markup meaning. The first two hashes is >>> an "unquoted text" markup (with no content) followed by a hash without >>> a closing hash and so its not markup. If you escape the first hash it >>> is put in the output and the second two are now the unquoted text >>> markup. If you escape the first two the last is again not markup >>> since there is no matching end hash. So if you now escape the last >>> one, its not markup anyway and so the backslash isn't an escape, its a >>> backslash. >>> >>> Cheers >>> Lex >>> >>> >>> ted >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "asciidoc" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/asciidoc. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "asciidoc" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/asciidoc/_7q0bIp0BNo/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/asciidoc. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "asciidoc" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/asciidoc. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "asciidoc" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/asciidoc/_7q0bIp0BNo/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/asciidoc. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> Ted Toal, PhD Candidate, [email protected] >>> Brady Lab, UC Davis, Life Sciences 2243 >>> One Shields Ave., Davis, CA 95616, ph: (530) 752-2537 >>> >>> >>> >>> >>> >>> >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "asciidoc" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/asciidoc/_7q0bIp0BNo/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/asciidoc. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> Ted Toal, PhD Candidate, [email protected] >> Brady Lab, UC Davis, Life Sciences 2243 >> One Shields Ave., Davis, CA 95616, ph: (530) 752-2537 >> >> >> >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "asciidoc" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/asciidoc. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "asciidoc" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/asciidoc/_7q0bIp0BNo/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/d/optout. -- Ted Toal, PhD Candidate, [email protected] Brady Lab, UC Davis, Life Sciences 2243 One Shields Ave., Davis, CA 95616, ph: (530) 752-2537 -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
