Re: doc bug in string-null?
> "Thien-Thi" == Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: Neil>BTW, did you fix this in stable as well? [...] Thien-Thi> hmmm i'm confused by your suggestion. All I meant was that the situation was confused by me not applying these docstring.el fixes to the stable branch as well; I'll do that now. (There's currently no reason for docstring.el to differ at all between the stable and unstable branches.) Thien-Thi> in any case, in both branches, i fixed libguile/strop.c Thien-Thi> only. Thien-Thi> [munge munge] i've just tweaked docstring.el (unstable) Thien-Thi> to use an env var for some of its directory inits and Thien-Thi> will be trying it out soon. Great! Neil ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: doc bug in string-null?
> "Thien-Thi" == Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: Thien-Thi> if the commands above are invoked automatically by cron Thien-Thi> on some machine under your control, i'll just sit back Thien-Thi> and watch. :-> No cron, I'm afraid; it just happens every now and then. Thien-Thi> one thing i'd like to request is that generated docs Thien-Thi> have some "@c generated" comment near each item (or Thien-Thi> perhaps, less verbosely, a similar one-time hint at the Thien-Thi> top of the file, to remind people to look at Thien-Thi> ../libguile files instead of editing the texi directly. Hmm... this relates to the question of whether the docs _ought_ to be identical in the manual, and there's quite a strong argument that they shouldn't. They mostly are for now, 'cos it's easier, but that probably shouldn't be the case for ever, and I'm not sure that I want to discourage anyone from making the manual version of the docs more suited to the manual context. Neil ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: doc bug in string-null?
From: Neil Jerram <[EMAIL PROTECTED]> Date: 11 Nov 2001 21:46:45 + M-x load-file RET .../doc/maint/docstring.el RET M-x docstring-process-module RET (guile) RET Save all modified .texi files and copy the current libguile/guile.texi to doc/maint/guile.texi, then commit. Unless other stuff has changed since the auto update that I checked in today, the "*Docstring Results*" output buffer should only mention changes for docstrings that you think you've actually changed - i.e. string-null?. if the commands above are invoked automatically by cron on some machine under your control, i'll just sit back and watch. :-> one thing i'd like to request is that generated docs have some "@c generated" comment near each item (or perhaps, less verbosely, a similar one-time hint at the top of the file, to remind people to look at ../libguile files instead of editing the texi directly. BTW, did you fix this in stable as well? I just fixed docstring.el to cope with the moving of the reference manual into the ref subdirectory, but haven't yet copied this change to the unstable branch; so you might want to grab docstring.el from unstable. hmmm i'm confused by your suggestion. in any case, in both branches, i fixed libguile/strop.c only. [munge munge] i've just tweaked docstring.el (unstable) to use an env var for some of its directory inits and will be trying it out soon. thi ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: doc bug in string-null?
From: Neil Jerram <[EMAIL PROTECTED]> Date: 11 Nov 2001 21:46:45 + M-x load-file RET .../doc/maint/docstring.el RET M-x docstring-process-module RET (guile) RET Save all modified .texi files and copy the current libguile/guile.texi to doc/maint/guile.texi, then commit. Unless other stuff has changed since the auto update that I checked in today, the "*Docstring Results*" output buffer should only mention changes for docstrings that you think you've actually changed - i.e. string-null?. if the commands above are invoked automatically by cron on some machine under your control, i'll just sit back and watch. :-> one thing i'd like to request is that generated docs have some "@c generated" comment near each item (or perhaps, less verbosely, a similar one-time hint at the top of the file, to remind people to look at ../libguile files instead of editing the texi directly. BTW, did you fix this in stable as well? I just fixed docstring.el to cope with the moving of the reference manual into the ref subdirectory, but haven't yet copied this change to the unstable branch; so you might want to grab docstring.el from unstable. hmmm i'm confused by your suggestion. in any case, in both branches, i fixed libguile/strop.c only. thi ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: doc bug in string-null?
> "Thien-Thi" == Thien-Thi Nguyen <[EMAIL PROTECTED]> writes: Thien-Thi>From: Scott Lenser <[EMAIL PROTECTED]> Thien-Thi> Date: Sun, 11 Nov 2001 06:05:29 -0500 Thien-Thi>Part of the documentation for string-null? is Thien-Thi> incorrect where it says nonzero, it means zero. Thien-Thi> thanks for the bug report. Thien-Thi> fixed in libguile/strop.c -- however, i need to Thien-Thi> familiarize myself w/ doc snarfing procedures to figure Thien-Thi> out how this is to propagate to the texi file... M-x load-file RET .../doc/maint/docstring.el RET M-x docstring-process-module RET (guile) RET Save all modified .texi files and copy the current libguile/guile.texi to doc/maint/guile.texi, then commit. Unless other stuff has changed since the auto update that I checked in today, the "*Docstring Results*" output buffer should only mention changes for docstrings that you think you've actually changed - i.e. string-null?. BTW, did you fix this in stable as well? I just fixed docstring.el to cope with the moving of the reference manual into the ref subdirectory, but haven't yet copied this change to the unstable branch; so you might want to grab docstring.el from unstable. Neil ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
Re: doc bug in string-null?
From: Scott Lenser <[EMAIL PROTECTED]> Date: Sun, 11 Nov 2001 06:05:29 -0500 Part of the documentation for string-null? is incorrect where it says nonzero, it means zero. thanks for the bug report. fixed in libguile/strop.c -- however, i need to familiarize myself w/ doc snarfing procedures to figure out how this is to propagate to the texi file... thi ___ Bug-guile mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-guile
