From: Herbert Xu <herbert@gondor.apana.org.au>
To: DASH Mailing List <dash@vger.kernel.org>
Subject: [v2 PATCH 0/8] Add multi-byte support
Date: Sun, 28 Apr 2024 11:56:55 +0800 [thread overview]
Message-ID: <cover.1714276539.git.herbert@gondor.apana.org.au> (raw)
v2 fixes a bug in scanright.
This patch series adds multi-byte support to dash. For now only
fnmatch is supported as the native pmatch function has not been
modified to support multi-byte characters.
Herbert Xu (8):
shell: Call setlocale
shell: Use strcoll instead of strcmp where applicable
expand: Count multi-byte characters for VSLENGTH
expand: Process multi-byte characters in subevalvar
expand: Process multi-byte characters in expmeta
expand: Support multi-byte characters during field splitting
input: Allow MB_LEN_MAX calls to pungetc
parser: Add support for multi-byte characters
src/bltin/test.c | 8 +-
src/expand.c | 487 +++++++++++++++++++++++++++++++++++------------
src/expand.h | 1 +
src/input.c | 58 ++++--
src/input.h | 11 +-
src/main.c | 4 +
src/mystring.c | 2 +-
src/parser.c | 127 +++++++++---
src/parser.h | 1 +
9 files changed, 517 insertions(+), 182 deletions(-)
--
2.39.2
next reply other threads:[~2024-04-28 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 3:56 Herbert Xu [this message]
2024-04-28 3:56 ` [v2 PATCH 1/8] shell: Call setlocale Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 2/8] shell: Use strcoll instead of strcmp where applicable Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 3/8] expand: Count multi-byte characters for VSLENGTH Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 4/8] expand: Process multi-byte characters in subevalvar Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 5/8] expand: Process multi-byte characters in expmeta Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 6/8] expand: Support multi-byte characters during field splitting Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 7/8] input: Allow MB_LEN_MAX calls to pungetc Herbert Xu
2024-04-28 3:57 ` [v2 PATCH 8/8] parser: Add support for multi-byte characters Herbert Xu
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=cover.1714276539.git.herbert@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dash@vger.kernel.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 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.