From: "Frederick M. Muriithi" via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 58517@debbugs.gnu.org
Subject: bug#58517: Bug: Module for SXPath not Documented
Date: Fri, 14 Oct 2022 13:30:43 +0000 [thread overview]
Message-ID: <btaVANnfXsR58KLYdGCh4gf7fBG5aZtffezTv9yJyeAPZmtHbDURIXELuw7b5VBIBc3k0oOUrDI-oUfL5aA55zd5OYL3pvxq-MlBsIPepbI=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
The module that provides the interface to SXPath was not clearly documented in the manual.
I have provided a patch that does that to help future readers.
Muriithi Frederick Muriuki
https://fredmanglis.me.ke
PGP Key Fingerprint: F370 F409 854B 90E3 52F3 AB01 362B 0BB8 B81D 5A42
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Document-the-module-containing-the-SXPath-interface.patch --]
[-- Type: text/x-patch; name=0001-Document-the-module-containing-the-SXPath-interface.patch, Size: 868 bytes --]
From b77236cebea0b93211c2b082361ac44d5f80cc57 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi <fredmanglis@gmail.com>
Date: Fri, 14 Oct 2022 16:21:56 +0300
Subject: [PATCH] Document the module containing the SXPath interface
* doc/ref/sxml.texi: add paragraph.
---
doc/ref/sxml.texi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/ref/sxml.texi b/doc/ref/sxml.texi
index 003309d54..6576e2651 100644
--- a/doc/ref/sxml.texi
+++ b/doc/ref/sxml.texi
@@ -755,6 +755,8 @@ converter, applied to a node or a nodeset, yields a non-empty nodeset,
the converter-predicate is deemed satisfied. Likewise, an empty nodeset
is equivalent to @code{#f} in denoting failure.
+The @code{(sxml xpath)} module provides the interface for handling SXPath.
+
@deffn {Scheme Procedure} nodeset? x
Return @code{#t} if @var{x} is a nodeset.
@end deffn
--
2.37.2
reply other threads:[~2022-10-14 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='btaVANnfXsR58KLYdGCh4gf7fBG5aZtffezTv9yJyeAPZmtHbDURIXELuw7b5VBIBc3k0oOUrDI-oUfL5aA55zd5OYL3pvxq-MlBsIPepbI=@protonmail.com' \
--to=bug-guile@gnu.org \
--cc=58517@debbugs.gnu.org \
--cc=fredmanglis@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).