From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: jgart <jgart@dismail.de>, 56478@debbugs.gnu.org
Subject: [bug#56478] [PATCH v2] gnu: Add cl-string-pokemonize.
Date: Tue, 12 Jul 2022 12:02:58 +0200 [thread overview]
Message-ID: <6c4c7b53c409fc2ee7572b5e8b5a277486e7c0f7.camel@ist.tugraz.at> (raw)
In-Reply-To: <20220710174140.17951-1-jgart@dismail.de>
Am Sonntag, dem 10.07.2022 um 12:41 -0500 schrieb jgart:
> * gnu/packages/lisp-xyz.scm (cl-string-pokemonize): New variable.
>
> Fixes a redundant wording in the description.
> ---
> gnu/packages/lisp-xyz.scm | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/gnu/packages/lisp-xyz.scm b/gnu/packages/lisp-xyz.scm
> index 129b99e485..60000a504a 100644
> --- a/gnu/packages/lisp-xyz.scm
> +++ b/gnu/packages/lisp-xyz.scm
> @@ -22647,6 +22647,41 @@ (define-public cl-sketch
> (define-public ecl-sketch
> (sbcl-package->ecl-package sbcl-sketch))
>
> +(define-public sbcl-string-pokemonize
> + (let ((commit "2dc01643defb497e4d1eb833def71dfc1e8d5da6")
> + (revision "0"))
> + (package
> + (name "sbcl-string-pokemonize")
> + (version (git-version "20210503" revision commit))
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/phoe/string-pokemonize")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> "1zk5klc94pxv7mhx6qrp93rk4ypwd6wfijap7gf9l0wpphg90r9x"))))
> + (build-system asdf-build-system/sbcl)
> + (arguments
> + `(#:tests? #f ; There are no tests.
> + #:asd-files '("string-pokemonize.asd")
> + #:asd-systems '("string-pokemonize")))
> + (synopsis "Function to alternate uppercase and lowercase
> characters")
SiMpLiFy tO "aLtErNaTe uPpEr aNd lOwErCaSe".
> + (description
> +"Provides a function, @code{string-pokemonize} that alternates
> uppercase
> +and lowercase characters for a given string. The code base is also
> +entirely stylized in alternating uppercase and lowercase characters
> +exemplifying Common Lisp's case insensitivity.")
ThE DeScRiPtIoN Of a pAcKaGe sHoUlD CoNsIsT Of cOmPlEtE SeNtEnCeS OnLy.
aLsO DoN'T FoRgEt tO PrOpErLy iNdEnT iT.
ChEeRs
next prev parent reply other threads:[~2022-07-12 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 8:41 [bug#56478] [PATCH] gnu: Add cl-string-pokemonize jgart via Guix-patches via
2022-07-10 17:41 ` [bug#56478] [PATCH v2] " jgart via Guix-patches via
2022-07-12 10:02 ` Liliana Marie Prikler [this message]
2022-07-20 5:12 ` jgart via Guix-patches via
2022-07-20 16:58 ` Liliana Marie Prikler
2022-07-21 23:08 ` jgart via Guix-patches via
2022-08-16 19:28 ` bug#56478: " Liliana Marie Prikler
2022-08-16 19:52 ` [bug#56478] [PATCH] " jgart via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c4c7b53c409fc2ee7572b5e8b5a277486e7c0f7.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56478@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.