Menu
▾
▴
nuweb-users
|
From: Paul H. <pau...@hu...> - 2011-04-20 10:01:44
|
Dear nuwebbers, I was very pleased to see that nuweb is still being maintained and upgraded. I use nuweb intensively (see e.g. <http://cli.vu/~paul/webcom/>). Thank you! Today I tried the latest version nuweb 1.55 on an existing nuweb file. It seems that the comment character sequence "@%" has a different meaning than previously. For instance, the macro @o foo @{@% bar @} expands to a file with a single line in the older versions of nuweb, but in the latest version it expands to a file that starts with an empty line. Is that a bug or feature? A second point concerning the comment character: I would like to use the comment character sequence "@%" inside as well as outside of macro's (code scraps). To this end I had modifies nuweb1.0b1 long ago. Would it be helpful to you if I send you the diffs of my modification, or is it a feature that "@%" is not valid ouside macro's? Thanks, Paul Huygen |
|
From: Simon W. <sim...@ma...> - 2011-04-20 18:12:41
|
Paul, On your first point, you're quite right. I was sure that it worked, indeed I'd reworked one of my webs to use the feature. Can't have checked the result very well :-( On the second point, do you mean outside as well as inside? Is this the same bug as 631095 (https://sourceforge.net/tracker/?func=detail&aid=631095&group_id=7449&atid=107449)? I guess so, because in 2005 you added a note very like this one. I'll do something about it Real Soon Now. Best wishes, --S On 20 Apr 2011, at 10:37, Paul Huygen wrote: > Dear nuwebbers, > > I was very pleased to see that nuweb is still being maintained and upgraded. I > use nuweb intensively (see e.g. <http://cli.vu/~paul/webcom/>). Thank you! > > Today I tried the latest version nuweb 1.55 on an existing nuweb file. It > seems that the comment character sequence "@%" has a different meaning than > previously. For instance, the macro > > @o foo @{@% > bar > @} > > expands to a file with a single line in the older versions of nuweb, but in > the latest version it expands to a file that starts with an empty line. Is > that a bug or feature? > > A second point concerning the comment character: I would like to use the > comment character sequence "@%" inside as well as outside of macro's (code > scraps). To this end I had modifies nuweb1.0b1 long ago. Would it be helpful > to you if I send you the diffs of my modification, or is it a feature that > "@%" is not valid ouside macro's? > > Thanks, > > Paul Huygen > > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Nuweb-users mailing list > Nuw...@li... > https://lists.sourceforge.net/lists/listinfo/nuweb-users |
|
From: Paul H. <pau...@hu...> - 2011-04-20 21:12:25
|
Thank you for your prompt reaction. On Wed, 20 Apr 2011 19:12:30 +0100, Simon Wright wrote > Paul, > > On your first point, you're quite right. I was sure that it worked, > indeed I'd reworked one of my webs to use the feature. Can't have > checked the result very well :-( > > On the second point, do you mean outside as well as inside? Is this > the same bug as 631095 > (https://sourceforge.net/tracker/? func=detail&aid=631095&group_id=7449&atid=107449)? I guess so, because in 2005 you added a note very like this one. I'll do something about it Real Soon Now. That is indeed the same thing. Thanks. Paul Huygen > Best wishes, > > --S > > On 20 Apr 2011, at 10:37, Paul Huygen wrote: > > > Dear nuwebbers, > > > > I was very pleased to see that nuweb is still being maintained and upgraded. I > > use nuweb intensively (see e.g. <http://cli.vu/~paul/webcom/>). Thank you! > > > > Today I tried the latest version nuweb 1.55 on an existing nuweb file. It > > seems that the comment character sequence "@%" has a different meaning than > > previously. For instance, the macro > > > > @o foo @{@% > > bar > > @} > > > > expands to a file with a single line in the older versions of nuweb, but in > > the latest version it expands to a file that starts with an empty line. Is > > that a bug or feature? > > > > A second point concerning the comment character: I would like to use the > > comment character sequence "@%" inside as well as outside of macro's (code > > scraps). To this end I had modifies nuweb1.0b1 long ago. Would it be helpful > > to you if I send you the diffs of my modification, or is it a feature that > > "@%" is not valid ouside macro's? > > > > Thanks, > > > > Paul Huygen > > > > > > -------------------------------------------------------------------------- ---- > > Benefiting from Server Virtualization: Beyond Initial Workload > > Consolidation -- Increasing the use of server virtualization is a top > > priority.Virtualization can reduce costs, simplify management, and improve > > application availability and disaster protection. Learn more about boosting > > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > > _______________________________________________ > > Nuweb-users mailing list > > Nuw...@li... > > https://lists.sourceforge.net/lists/listinfo/nuweb-users > > ---------------------------------------------------------------------------- -- > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and > improve application availability and disaster protection. Learn more > about boosting the value of server virtualization. > http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ > Nuweb-users mailing list > Nuw...@li... > https://lists.sourceforge.net/lists/listinfo/nuweb-users -- Paul Huygen |
|
From: John H H. <jhh...@un...> - 2011-04-20 20:19:57
|
Hello Simon and Paul,
I was not aware of the @% command, but I will definitely use it in the
future, if we can get the bug fixed. Preston Briggs, in the Nuweb
manual, says
Nuweb provides the command
@%
only to be used inside scraps. It behaves exactly the same as % in the
normal LaTeX text body.
So the use outside of macros is /not/ intended -- probably reasoning
that you can already use a lone % character, and let LaTeX do the
comment and line splice.
Best
John H. Harris
------------------------------------
Unencumbered Design, LLC
Research and design engineering,
technical writing and copy editing,
software development.
572 Union Village Rd
Norwich VT 05055
43.7437N,72.2942W
UnencumberedDesign.com
office (802) 649-8130
JHH...@un...
|
|
From: Simon W. <sim...@ma...> - 2011-05-09 17:10:41
|
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 |
|
From: Paul H. <pau...@hu...> - 2011-05-10 12:07:28
|
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.
|
|
From: Simon W. <sim...@ma...> - 2011-05-14 17:06:58
|
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.
>
>
>
>
|
|
From: Paul H. <pau...@hu...> - 2011-05-16 19:24:01
|
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. |
Thanks for helping keep SourceForge clean.
X