Thank you for your reply. The problem has been resolved. I was not aware of the
difference between deadtilde and asciitilde. Deadtilde plus space create an
asciitilde when you are in a text-based application. However, they are not
equivalent in LyX. Prior to fixing my Xmodmap there was no way to type an
asciitilde in Lyx. (now there is no way to type a deadtilde, I guess).
I think, I haven't yet understood how LyX is intended to work with noweb. I work
with LyX 1.1.5 under AIX. Formatting the documentation works pretty well. I use
file > export >custom (postscript to "ps2pdf '$$FName'; acroread
'$$FName'.pdf"). There are differences between the output under AIX and Linux,
e.g. under AIX the identifier instances in code chunks are not highlighted. But
this is a ps2pdf or hyperref issue.
I'm still fighting with the build process, neet to try "listerrors". Are you
aware of any similar tool for perl or python scripts?
My personal wish list of noweb support features is
- Code chunk inset or paragraph layout with
- no need to type C-Return at line ends
- chunk headers acting as labels
- code reference can be done using the Refs menu (offering the code chunks
already defined)
- configurable syntax highlighting (send to emacs and get back the colored
text?)
- Goto line in file: Choose a root file and a line number, point the cursor to
where the line is defined in lyx (semi-automatic and quite general error
tracking). The script should scan the tangled (with line number information)
file, find the line number in the noweb source and pipe the appropriate
server-goto-file-row command to lyx. I would need help to do that.
Greets, Martin Kraska
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> on 21.07.2000 15:40:24
To: Martin Kraska/CargoLifter AG@CargoLifter
cc: [EMAIL PROTECTED]
Subject: Re: Literate programming in lyx
On Fri, Jul 21, 2000 at 01:57:11PM +0100, Martin Kraska wrote:
>
>
> Hi,
>
> I like the idea to use LyX as a front end for noweb. So I found your article
in
> the documentation helpful. For code extraction I prefer a different approach
> (export as latex and run a script that extracts all files and postprocesses
them
> depending on their extension. However, there is still one severe problem. The
> Scrap layout is not literally translated to the latex export, some special
> characters are escaped and following curly braces are included. This is fatal
> for regular expressions, e.g. How can I force Lyx to avoid such conversion?
>
> Thanks for your help. Greets, Martin Kraska
I use the LyX Literate Programming facilities all the time and I don't have
this problem. Can you provide an example LyX file? Which version of LyX are you
using?
---Kayvan
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena
http://www.successlinks.com/kayvan | Reach your goals now! | Robin Gregory
