Hi Terry,
A stupid, quick and dirty workaround:
Change '<<' and '>>' before Leo editing to something else, let's say
'<{<{<' and '>}>}>' (be sure that doesn't appears in the text) and change
back after Leo editing.
Using sed, may be something like:
find /your/path -type f -print0 | xargs -0 sed -i 's/<</<{<{</g'
and after Leo:
find /your/path -type f -print0 | xargs -0 sed -i 's/<{<{</<</g'
Cheers
Zoltan
On Monday, February 1, 2016 at 11:40:36 PM UTC+2, Terry Brown wrote:
>
> Hmm, unfortunately I want to write files which contain content like this:
>
> this part is LaTeX etc. etc.
>
> <<show_working>>=
> this part is R code
> @
>
> more LaTeX here
>
> https://github.com/yihui/knitr/blob/master/inst/examples/knitr-minimal.Rnw
> is an example, and http://yihui.name/knitr/demo/minimal/, comments at end
> of main post, explains the situation well. I think the question "can we
> have user defined section delimiters instead of << >> has come up before
> and met with a probably quite reasonable No!
>
> I know @asis and @nosent can do it, but I want hierarchy. I can just use
> other delimiters and post-process.
>
> Cheers -Terry
>
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" 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 https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
