nuweb-users Mailing List for nuweb for Literate Programming

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Although the news is a couple of months old now, I am just seeing that the maintainer of nuweb has passed away. https://forum.ada-lang.io/t/simon-j-wright-rip/2088/7

RIP Simon Wright.

> How do you have two <main>s? Is it by using sections? This is a feature I haven’t implemented in nuweb.py<https://github.com/simonjwright/nuweb.py>!

Yes, exactly, I am using sections. Sections seemed to make the most sense for what I am doing with each of the two parts of the programming challenge being blogged about.

On 23 Mar 2024, at 20:38, Adam Russell <ac....@li...> wrote:

> The past month or so I've been using nuweb to formulate my solutions to The Weekly Challenge. The latest entry is up at http://www.rabbitfarm.com/cgi-bin/blosxom/perl/2024/03/23 <http://www.rabbitfarm.com/cgi-bin/blosxom/perl/2024/03/23>.

How do you have two <main>s? Is it by using sections? This is a feature I haven’t implemented in nuweb.py <https://github.com/simonjwright/nuweb.py>!

The past month or so I've been using nuweb to formulate my solutions to The Weekly Challenge. The latest entry is up at http://www.rabbitfarm.com/cgi-bin/blosxom/perl/2024/03/23<http://www.rabbitfarm.com/cgi-bin/blosxom/perl/2024/03/23>.

While I used literate programming quite a bit for more academic work this type of usage is very new to me. Plenty of things to improve. Certainly I need to modify the css to improve the style. Also, probably just my general writing too! I'd like to include more graphics via tikz and graphviz.

On 22 Mar 2024, at 03:30, Adam Russell <ac....@li...> wrote:
> 
> I am not the OP, but can I make a small suggestion that the documentation pdf on the SF page be updated to be the most recent one? Having it reflect the most recent version is nice. Also I noticed that some things the command line option -r aren't in the manual (v1.60) that is linked to there. 

Updated to 1.64.
I had to update the documentation to actually include -r (and -h, -x)!

—S
I am not the OP, but can I make a small suggestion that the documentation pdf on the SF page be updated to be the most recent one? Having it reflect the most recent version is nice. Also I noticed that some things the command line option -r aren't in the manual (v1.60) that is linked to there.

________________________________
From: Simon Wright <si...@pu...>
Sent: Wednesday, March 20, 2024 4:13 PM
To: Adam Russell <ac....@li...>
Cc: nuw...@li... <nuw...@li...>
Subject: Re: [Nuweb-users] tar: Ignoring malformed pax extended attribute

I’ve uploaded 1.63 (since the version number is embedded in nuweb.w!)

On 20 Mar 2024, at 11:51, Simon Wright <si...@pu...> wrote:

Since there’s no change to nuweb itself, can I call it nuweb-1.62.1?

On 19 Mar 2024, at 20:57, Adam Russell <ac....@li...> wrote:

I also install nuweb via macports, so thank you for helping maintain the package!

________________________________
From: Ryan Carsten Schmidt via Nuweb-users <nuw...@li...>
Sent: Monday, March 18, 2024 7:19 AM
To: nuw...@li... <nuw...@li...>
Subject: [Nuweb-users] tar: Ignoring malformed pax extended attribute

I can't extract nuweb-1.62.tar.gz on old versions of macOS (e.g. 10.12):

tar: Ignoring malformed pax extended attribute
tar: Ignoring malformed pax extended attribute
tar: Error exit delayed from previous errors.

You should exclude xattrs when you create your archives. It's the default when using GNU tar and can be done with BSD tar by using the --no-xattrs flag.

Here is the MacPorts bug report about this issue: https://trac.macports.org/ticket/68047

I wanted to report this in the SourceForge issue tracker but the Create Ticket button is disabled.

_______________________________________________
Nuweb-users mailing list
Nuw...@li...
https://lists.sourceforge.net/lists/listinfo/nuweb-users
_______________________________________________
Nuweb-users mailing list
Nuw...@li...<mailto:Nuw...@li...>
https://lists.sourceforge.net/lists/listinfo/nuweb-users

_______________________________________________
Nuweb-users mailing list
Nuw...@li...
https://lists.sourceforge.net/lists/listinfo/nuweb-users

I’ve uploaded 1.63 (since the version number is embedded in nuweb.w!)

> On 20 Mar 2024, at 11:51, Simon Wright <si...@pu...> wrote:
> 
> Since there’s no change to nuweb itself, can I call it nuweb-1.62.1? 
> 
>> On 19 Mar 2024, at 20:57, Adam Russell <ac....@li...> wrote:
>> 
>> I also install nuweb via macports, so thank you for helping maintain the package!
>> 
>> From: Ryan Carsten Schmidt via Nuweb-users <nuw...@li...>
>> Sent: Monday, March 18, 2024 7:19 AM
>> To: nuw...@li... <nuw...@li...>
>> Subject: [Nuweb-users] tar: Ignoring malformed pax extended attribute
>>  
>> I can't extract nuweb-1.62.tar.gz on old versions of macOS (e.g. 10.12):
>> 
>> tar: Ignoring malformed pax extended attribute
>> tar: Ignoring malformed pax extended attribute
>> tar: Error exit delayed from previous errors.
>> 
>> You should exclude xattrs when you create your archives. It's the default when using GNU tar and can be done with BSD tar by using the --no-xattrs flag.
>> 
>> Here is the MacPorts bug report about this issue: https://trac.macports.org/ticket/68047
>> 
>> I wanted to report this in the SourceForge issue tracker but the Create Ticket button is disabled.
>> 
>> 
>> 
>> _______________________________________________
>> Nuweb-users mailing list
>> Nuw...@li...
>> https://lists.sourceforge.net/lists/listinfo/nuweb-users
>> _______________________________________________
>> Nuweb-users mailing list
>> Nuw...@li... <mailto:Nuw...@li...>
>> https://lists.sourceforge.net/lists/listinfo/nuweb-users
> 
> _______________________________________________
> Nuweb-users mailing list
> Nuw...@li...
> https://lists.sourceforge.net/lists/listinfo/nuweb-users

Since there’s no change to nuweb itself, can I call it nuweb-1.62.1? 

> On 19 Mar 2024, at 20:57, Adam Russell <ac....@li...> wrote:
> 
> I also install nuweb via macports, so thank you for helping maintain the package!
> 
> From: Ryan Carsten Schmidt via Nuweb-users <nuw...@li...>
> Sent: Monday, March 18, 2024 7:19 AM
> To: nuw...@li... <nuw...@li...>
> Subject: [Nuweb-users] tar: Ignoring malformed pax extended attribute
>  
> I can't extract nuweb-1.62.tar.gz on old versions of macOS (e.g. 10.12):
> 
> tar: Ignoring malformed pax extended attribute
> tar: Ignoring malformed pax extended attribute
> tar: Error exit delayed from previous errors.
> 
> You should exclude xattrs when you create your archives. It's the default when using GNU tar and can be done with BSD tar by using the --no-xattrs flag.
> 
> Here is the MacPorts bug report about this issue: https://trac.macports.org/ticket/68047
> 
> I wanted to report this in the SourceForge issue tracker but the Create Ticket button is disabled.
> 
> 
> 
> _______________________________________________
> Nuweb-users mailing list
> Nuw...@li...
> https://lists.sourceforge.net/lists/listinfo/nuweb-users
> _______________________________________________
> Nuweb-users mailing list
> Nuw...@li... <mailto:Nuw...@li...>
> https://lists.sourceforge.net/lists/listinfo/nuweb-users

I also install nuweb via macports, so thank you for helping maintain the package!

________________________________
From: Ryan Carsten Schmidt via Nuweb-users <nuw...@li...>
Sent: Monday, March 18, 2024 7:19 AM
To: nuw...@li... <nuw...@li...>
Subject: [Nuweb-users] tar: Ignoring malformed pax extended attribute

I can't extract nuweb-1.62.tar.gz on old versions of macOS (e.g. 10.12):

tar: Ignoring malformed pax extended attribute
tar: Ignoring malformed pax extended attribute
tar: Error exit delayed from previous errors.

You should exclude xattrs when you create your archives. It's the default when using GNU tar and can be done with BSD tar by using the --no-xattrs flag.

Here is the MacPorts bug report about this issue: https://trac.macports.org/ticket/68047

I wanted to report this in the SourceForge issue tracker but the Create Ticket button is disabled.

_______________________________________________
Nuweb-users mailing list
Nuw...@li...
https://lists.sourceforge.net/lists/listinfo/nuweb-users

On 18 Mar 2024, at 11:19, Ryan Carsten Schmidt via Nuweb-users <nuw...@li...> wrote:
> 
> I can't extract nuweb-1.62.tar.gz on old versions of macOS (e.g. 10.12):
> 
> tar: Ignoring malformed pax extended attribute
> tar: Ignoring malformed pax extended attribute
> tar: Error exit delayed from previous errors.
> 
> You should exclude xattrs when you create your archives. It's the default when using GNU tar and can be done with BSD tar by using the --no-xattrs flag.

OK but is -no-xattrs standard? it doesn’t show on 'man linux' via google

I archived with -no-xattrs, but the result of an immediate extraction was

$ xattr -v -r nuweb-1.62
nuweb-1.62/test/00/t0009a.sh: com.apple.lastuseddate#PS
nuweb-1.62/Makefile: com.apple.lastuseddate#PS
nuweb-1.62/README: com.apple.lastuseddate#PS
nuweb-1.62/htdocs/index.html: com.apple.lastuseddate#PS

so it’s not obvious what you need? I could of course remove the attributes in the source!

> I wanted to report this in the SourceForge issue tracker but the Create Ticket button is disabled.

I have a feeling only registered uses can post tickets? It’s a long time since I engaged seriously with SF.

—S
I can't extract nuweb-1.62.tar.gz on old versions of macOS (e.g. 10.12):

tar: Ignoring malformed pax extended attribute
tar: Ignoring malformed pax extended attribute
tar: Error exit delayed from previous errors.

You should exclude xattrs when you create your archives. It's the default when using GNU tar and can be done with BSD tar by using the --no-xattrs flag.

Here is the MacPorts bug report about this issue: https://trac.macports.org/ticket/68047

I wanted to report this in the SourceForge issue tracker but the Create Ticket button is disabled.

I struggled quite a bit recently to get decent looking html generated with latex2html. While it works fine in many cases it seemed to struggle
with what I consider to be pretty normal things, like latex macros. Some research led me to tex4ht, along with make4ht, which handled whatever I could throw at it and produced some very nice looking html from nuweb generated latex. Also, for what it's worth, tex4t seems to be much more up to date to date than latex2html.

Does anyone have an example of a paper published  which uses Literate Programming? Doesn't necessarily have to be nuweb. The more recent (say, within the past several years) the better. Could be on any subject.

The usage of LP being not especially widespread at present I am having trouble finding an example from within the past twenty years!?!?

I've moved development of nuweb.py to github (https://github.com/simonjwright/nuweb.py).

The latest release includes am Emacs mode, https://github.com/simonjwright/nuweb.py/blob/master/poly-nuweb.el, which is basically latex-mode with nuweb scraps in fundamental mode.

--S

Himanshu sent me this …

Begin forwarded message:

> From: Himanshu Singh <91....@gm...>
> Subject: Re: [Nuweb-users] Problem in extracting c++ code
> Date: 6 June 2012 13:28:19 GMT+01:00
> To: Simon Wright <si...@pu...>
> 
> Hi,
> 
> Wow! Thank you very much! This is exactly what I was looking for.
> 
> Thanks,
> Himanshu
> 
> On Wed, Jun 6, 2012 at 5:51 PM, Simon Wright <si...@pu...> wrote:
> There is an smo.w at ftp://www.ai.mit.edu/pub/users/tlp/projects/svm/svm-smo/ - I think this may be what you're looking for.
> 
> --S
> 
> 
> On 6 Jun 2012, at 13:15, Simon Wright wrote:
> 
>> Himanshu,
>> 
>> I know that smo.pdf says it is a nuweb file, but this is very misleading.
>> 
>> The nuweb (source) file that you need would have been called smo.w; nuweb processed this to create smo.tex and smo.cc. smo.tex was then processed by pdflatex or similar to create the smo.pdf that you've downloaded.
>> 
>> Can you contact the author of the document to get hold of the original .w? If not, it would probably be possible to create a .w file by careful copy-and-paste from the .pdf file, but it'd be hard work.
>> 
>> --S
>> 
>> On 5 Jun 2012, at 21:04, Himanshu Singh wrote:
>> 
>>> Hi,
>>> 
>>> I am a new user of NUWEB. I am using NUWEB 1.58 to extract C++ code from this document: read.pudn.com/downloads60/ebook/208558/smo.pdf
>>> For that I downloaded the source. Ran "make nuweb". And then ./nuweb smo.pdf
>>> But it is giving me this error: "nuweb: bad @ sequence (./smo.pdf, line 176)".
>>> Please help as I need it urgent.
>>> 
>>> Thanks,
>>> Himanshu ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and 
>>> threat landscape has changed and how IT managers can respond. Discussions 
>>> will include endpoint security, mobile security and the latest in malware 
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
>>> Nuweb-users mailing list
>>> Nuw...@li...
>>> https://lists.sourceforge.net/lists/listinfo/nuweb-users
>> 
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and 
>> threat landscape has changed and how IT managers can respond. Discussions 
>> will include endpoint security, mobile security and the latest in malware 
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
>> Nuweb-users mailing list
>> Nuw...@li...
>> https://lists.sourceforge.net/lists/listinfo/nuweb-users
> 
> 

On 05.06.2012 22:04, Himanshu Singh wrote:
> Hi,
>
> I am a new user of NUWEB. I am using NUWEB 1.58 to extract C++ code
> from this document: read.pudn.com/downloads60/ebook/208558/ 
> [1]SMO.pdf
>  For that I downloaded the source. Ran "make nuweb". And then ./nuweb
> smo.pdf
> But it is giving me this error: "nuweb: bad @ sequence (./smo.pdf,
> line 176)".
> Please help as I need it urgent.
> [..]

I hope it is not really urgent.

Nuweb does not extract program code from PDF documents. I do not know 
whether computerprograms exist that extract c-code from PDF documents. 
If that does not exist, you will have to extract the code manually.

Regards,

Paul Huygen

There is an smo.w at ftp://www.ai.mit.edu/pub/users/tlp/projects/svm/svm-smo/ - I think this may be what you're looking for.

--S

On 6 Jun 2012, at 13:15, Simon Wright wrote:

> Himanshu,
> 
> I know that smo.pdf says it is a nuweb file, but this is very misleading.
> 
> The nuweb (source) file that you need would have been called smo.w; nuweb processed this to create smo.tex and smo.cc. smo.tex was then processed by pdflatex or similar to create the smo.pdf that you've downloaded.
> 
> Can you contact the author of the document to get hold of the original .w? If not, it would probably be possible to create a .w file by careful copy-and-paste from the .pdf file, but it'd be hard work.
> 
> --S
> 
> On 5 Jun 2012, at 21:04, Himanshu Singh wrote:
> 
>> Hi,
>> 
>> I am a new user of NUWEB. I am using NUWEB 1.58 to extract C++ code from this document: read.pudn.com/downloads60/ebook/208558/smo.pdf
>> For that I downloaded the source. Ran "make nuweb". And then ./nuweb smo.pdf
>> But it is giving me this error: "nuweb: bad @ sequence (./smo.pdf, line 176)".
>> Please help as I need it urgent.
>> 
>> Thanks,
>> Himanshu ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and 
>> threat landscape has changed and how IT managers can respond. Discussions 
>> will include endpoint security, mobile security and the latest in malware 
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
>> Nuweb-users mailing list
>> Nuw...@li...
>> https://lists.sourceforge.net/lists/listinfo/nuweb-users
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Nuweb-users mailing list
> Nuw...@li...
> https://lists.sourceforge.net/lists/listinfo/nuweb-users

Himanshu,

I know that smo.pdf says it is a nuweb file, but this is very misleading.

The nuweb (source) file that you need would have been called smo.w; nuweb processed this to create smo.tex and smo.cc. smo.tex was then processed by pdflatex or similar to create the smo.pdf that you've downloaded.

Can you contact the author of the document to get hold of the original .w? If not, it would probably be possible to create a .w file by careful copy-and-paste from the .pdf file, but it'd be hard work.

--S

On 5 Jun 2012, at 21:04, Himanshu Singh wrote:

> Hi,
> 
> I am a new user of NUWEB. I am using NUWEB 1.58 to extract C++ code from this document: read.pudn.com/downloads60/ebook/208558/smo.pdf
> For that I downloaded the source. Ran "make nuweb". And then ./nuweb smo.pdf
> But it is giving me this error: "nuweb: bad @ sequence (./smo.pdf, line 176)".
> Please help as I need it urgent.
> 
> Thanks,
> Himanshu ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
> Nuweb-users mailing list
> Nuw...@li...
> https://lists.sourceforge.net/lists/listinfo/nuweb-users

Hi,

I am a new user of NUWEB. I am using NUWEB 1.58 to extract C++ code from
this document: read.pudn.com/downloads60/ebook/208558/*smo*.pdf
For that I downloaded the source. Ran "make nuweb". And then ./nuweb smo.pdf
But it is giving me this error: "nuweb: bad @ sequence (./smo.pdf, line
176)".
Please help as I need it urgent.

Thanks,
Himanshu

I've been frustrated by trying to fix problems in nuweb. It can be really hard to work out how to make a change - for example, how to fix bug 2965157[1] - if it is indeed a bug!

Part of this is down to the fact that nuweb is implemented in C, but I think that mostly it's because we developers haven't treated it as a proper Literate Programming project. There ought to be some explanation of why (referring to 2965157 again) there's a scrap reference inside the parameter list. I think (from discussions on the nuweb-users mailing list) that it was deliberate, but I see no clue as to the intention.

As another problem (far from the only one!), what is a block comment?

Anyway, to scratch this itch I've been reworking nuweb in Python. The code repository is at [2]; it's a Mercurial[3] repo.

So far, the parts implemented are:

* files (@o and @O, but no flags)
* fragments (@d and @D, but no flags)
* scraps (delimited by @{ @} only)
* user-defined identifiers
* old-style fragment parameters
* indices @f, @m and @u (I've laid @u out a little differently)
* @% (anywhere in the document, not just in scraps)
* @# (put code line at left margin)
* @@ handling (this one was tricky, and I may not have caught all the cases)
* switch -r (generate hyperlinks), aliased --hyperlinks.

It won't handle the current nuweb.w, because that web uses new-style parameters. However, it will process it and generate LaTeX. nuweb.w reveals one shortcoming in the Python version, which is that it's slow at processing user-defined identifiers. It takes 8s on this Macbook Pro to process nuweb.w, against 0.07s for the C version. The fix for this (if it's worth it; the other webs I have take about a second overall, which isn't very painful) may be to implement the string search which nuweb.w uses [4], though a quick trial of acora[5] suggests that a pure Python implementation will be slower than the current re-based implementation in nuweb.py.

So why haven't I written nuweb.py as a web? I suppose the answer is, that I've been exploring the problem while writing the code, which doesn't seem to be a very `literate' approach. Now that the overall structure is reasonably clear, maybe it can be webified. That would at least force me to provide wome user-oriented documentation!

[1] http://sourceforge.net/tracker/?func=detail&aid=2965157&group_id=7449&atid=107449
[2] http://nuweb.hg.sourceforge.net/hgweb/nuweb/nuweb.py/
[3] http://mercurial.selenic.com/
[4] http://en.wikipedia.org/wiki/Aho–Corasick_string_matching_algorithm
[5] http://pypi.python.org/pypi/acora

I noticed that if we try and include punctuation in a macro name (e.g. @<Get "("@>) then nuweb crashes with message to user. Perhaps this restriction could be added to documentation and/or error messages.
Sent via BlackBerry by AT&T

On Sat, 14 May 2011 18:05:57 +0100, Simon Wright wrote
> Paul,
> 
> This feature was introduced by Keith Harwood. It seems odd to me,
>  perhaps Keith will tell us what it's for.

I am curious too. I imagine that it is quite demanding to ask for a switch to 
turn the feature on or off.

I use the empty placeholders often as a reminder, and sometimes I use 
templates, e.q. for functions, that include placeholders that could be used 
later on. So, maybe I should change my programming strategy.

Anyway, thank you and Keith for your greatly appreciated efforts wrt Nuweb.

Paul.

Paul,

This feature was introduced by Keith Harwood. It seems odd to me, perhaps Keith will tell us what it's for.

--S

On 10 May 2011, at 13:07, Paul Huygen wrote:

> Dear Simon,
> On Mon, 09 May 2011 18:10:13 +0100, Simon Wright wrote
>> Paul,
>> 
>> I've had a go, attached to this message. It involved a recursive 
>> call to source_get(), not I think a problem on modern machines but 
>> with nuweb you never know!
>> 
>> It works fine with nuweb itself, my web that used the feature, and a 
>> test case 631095.w (also attached).
>> 
>> Can you have a try and see how you get on?
> 
> Great!
> 
> It works on my computer. However, when I tried it on my own project, I
> discovered another "for-me" problem, that probably betrays my sloppiness. I
> have multiple scrap placeholders that refer to nothing. The older nuweb
> versions respond on this with a warning only, but nuweb-1.55 writes the
> placeholder in the output. E.g. when nuweb-1.01 processes the following file
> 
> ---testit.w-----------------------
> \documentclass{article}
> \begin{document}
> @o test.out @{@%
> Some text.
> @< a placeholder that refers to nothing @>
> @| @}
> \end{document}
> ----------------------------------
> 
> , it produces the following "test.out":
> 
> ---test.out----------------------
> Some text.
> 
> ---------------------------------.
> 
> However, nuweb 1.55 produces:
> 
> ---test.out----------------------
> Some text.
> @<a placeholder that refers to nothing@>
> ---------------------------------.
> 
> Thanks,
> 
> Paul.
> 
> 
> 
> 

Dear Simon,
On Mon, 09 May 2011 18:10:13 +0100, Simon Wright wrote
> Paul,
> 
> I've had a go, attached to this message. It involved a recursive 
> call to source_get(), not I think a problem on modern machines but 
> with nuweb you never know!
> 
> It works fine with nuweb itself, my web that used the feature, and a 
> test case 631095.w (also attached).
> 
> Can you have a try and see how you get on?

Great!

It works on my computer. However, when I tried it on my own project, I
discovered another "for-me" problem, that probably betrays my sloppiness. I
have multiple scrap placeholders that refer to nothing. The older nuweb
versions respond on this with a warning only, but nuweb-1.55 writes the
placeholder in the output. E.g. when nuweb-1.01 processes the following file

---testit.w-----------------------
\documentclass{article}
\begin{document}
@o test.out @{@%
Some text.
@< a placeholder that refers to nothing @>
@| @}
\end{document}
----------------------------------

, it produces the following "test.out":

---test.out----------------------
Some text.

---------------------------------.

However, nuweb 1.55 produces:

---test.out----------------------
Some text.
@<a placeholder that refers to nothing@>
---------------------------------.

Thanks,

Paul.

Paul,

I've had a go, attached to this message. It involved a recursive call to source_get(), not I think a problem on modern machines but with nuweb you never know!

It works fine with nuweb itself, my web that used the feature, and a test case 631095.w (also attached).

Can you have a try and see how you get on?

Regards,

--S

2000	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec
2001	Jan (2)	Feb (5)	Mar	Apr	May	Jun	Jul (1)	Aug	Sep (2)	Oct	Nov	Dec
2002	Jan (2)	Feb (2)	Mar (5)	Apr (3)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2003	Jan	Feb	Mar	Apr (2)	May	Jun	Jul	Aug (1)	Sep (1)	Oct	Nov (3)	Dec
2004	Jan (2)	Feb (1)	Mar (1)	Apr	May	Jun	Jul (1)	Aug (2)	Sep (3)	Oct	Nov	Dec (1)
2005	Jan	Feb	Mar (4)	Apr	May	Jun	Jul	Aug	Sep (1)	Oct (1)	Nov	Dec
2006	Jan (3)	Feb (2)	Mar (3)	Apr	May (5)	Jun (3)	Jul (2)	Aug (1)	Sep	Oct (1)	Nov (1)	Dec (11)
2007	Jan (7)	Feb (10)	Mar (8)	Apr (10)	May (16)	Jun (8)	Jul (27)	Aug (38)	Sep (7)	Oct (2)	Nov	Dec
2010	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2011	Jan	Feb	Mar	Apr (4)	May (4)	Jun (2)	Jul	Aug (1)	Sep	Oct	Nov	Dec
2012	Jan	Feb	Mar	Apr	May	Jun (5)	Jul	Aug	Sep	Oct	Nov	Dec
2019	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2024	Jan	Feb	Mar (12)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2025	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec

nuweb-users Mailing List for nuweb for Literate Programming

nuweb-users — nuweb users discussion list