unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Vijay Marupudi <vijay@vijaymarupudi.com>
To: guile-devel@gnu.org
Subject: doc: fix documented keyword argument default to match code
Date: Wed, 17 Aug 2022 09:34:37 -0400	[thread overview]
Message-ID: <87o7wj6ljm.fsf@vijaymarupudi.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 138 bytes --]

Hello,

I've attached a simple documentation bugfix patch for getopt-long,
`#:stop-at-first-non-option' defaults to #f, not #t.

~ Vijay


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-doc-fix-documented-keyword-argument-default-to-match.patch --]
[-- Type: text/x-patch, Size: 989 bytes --]

From 852d9eee636a0be61ea3e0fab88a5780971d33c2 Mon Sep 17 00:00:00 2001
From: Vijay Marupudi <vijay@vijaymarupudi.com>
Date: Wed, 17 Aug 2022 09:13:18 -0400
Subject: [PATCH] doc: fix documented keyword argument default to match code
 default

---
 doc/ref/mod-getopt-long.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/ref/mod-getopt-long.texi b/doc/ref/mod-getopt-long.texi
index cf043418f..e3dcc33e8 100644
--- a/doc/ref/mod-getopt-long.texi
+++ b/doc/ref/mod-getopt-long.texi
@@ -261,7 +261,7 @@ as ordinary argument strings.
 @node getopt-long Reference
 @subsection Reference Documentation for @code{getopt-long}
 
-@deffn {Scheme Procedure} getopt-long args grammar [#:stop-at-first-non-option #t]
+@deffn {Scheme Procedure} getopt-long args grammar [#:stop-at-first-non-option #f]
 Parse the command line given in @var{args} (which must be a list of
 strings) according to the option specification @var{grammar}.
 
-- 
2.37.2


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]

             reply	other threads:[~2022-08-17 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 13:34 Vijay Marupudi [this message]
2022-12-15 17:45 ` doc: fix documented keyword argument default to match code Vijay Marupudi
2022-12-15 18:02   ` Aleix Conchillo Flaqué
2022-12-21  7:31     ` N. Dal

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=87o7wj6ljm.fsf@vijaymarupudi.com \
    --to=vijay@vijaymarupudi.com \
    --cc=guile-devel@gnu.org \
    /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).