>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:

Amir> Good point. I guess more of us should start doing that. How long
Amir> until the LyX code is a noweb document?

I would love to see that!

You have no idea how satisfying it is to produce even a small literate
program. You see, I totally enjoy programming. I often stay up way
past everyone else going to bed, programming something. However, that
enjoyment for me is magnified greatly when I am coding in a literate
style. The methodology produces code that is easier to debug and
change, as well.

Amir> Yeah, it would be nice if we merged it into reLyX.

Amir> It shouldn't be too hard to break nwconvert in two pieces, and
Amir> have 'reLyX -n' (for example) automatically call the pre- &
Amir> post-processing subroutines.

That seems very logical. Hmmm... I think I can change it to do this:

  ``noweb2lyx -pre in-file out-file'' would only call the
  preprocessing part (up to calling reLyX).

  ``noweb2lyx -post in-file out-file'' would only call the
  post-processing part (after calling reLyX).

That way, the only thing you might have to merge into reLyX is the
code that gleans the article class of the noweb file (so it can
generate a literate-$class document).

So, you could just insert ``noweb2lyx -pre'' and ``noweb2lyx -post''
in the right places in reLyX (and noweb2lyx could still be a
standalone script).

>> It would probably be a good idea to find a name with 'lyx' in it,
>> though. 'nwconvert' looks like a very generic name to me...

Amir> Kayvan suggested nw2lyx. Why not the less cryptic noweb2lyx? 

Yes. I like noweb2lyx even better than my cryptic nw2lyx.

                      ---Kayvan

Reply via email to