Github messages for voidlinux
 help / color / mirror / Atom feed
From: chase-net <chase-net@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [[:space:]] and [[:blank:] character classes not working as expected in nvi
Date: Wed, 17 Aug 2022 19:29:12 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38742@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

New issue by chase-net on void-packages repository

https://github.com/void-linux/void-packages/issues/38742

Description:
### Is this a new report?

Yes

### System Info

Void 5.18.17_1 x86_64-musl GenuineIntel notuptodate hold rFFF

### Package(s) Affected

nvi-1.81.6_17

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Searching should match space and tab characters when using the POSIX character classes [:space:] and [:blank:].

### Actual behaviour

[:space:] and [:blank:] seem to match the [:alnum:] character class.

### Steps to reproduce

1. Start vi. `EXINIT= vi`
2. Insert some text including spaces and alphanumeric characters and return to normal mode. `ia b c d<esc>`
3. Search for the character classes [:space:] or [:blank:]. `/[[:space:]]`
4. Cycle through matches with `n`.

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 17:29 chase-net [this message]
2022-08-19 13:48 ` abenson
2022-08-19 13:49 ` [ISSUE] [CLOSED] " abenson
2022-08-19 16:19 ` sgn
2022-08-19 16:20 ` sgn
2022-08-19 17:32 ` sgn
2022-08-19 17:43 ` chase-net
2022-08-19 18:04 ` sgn
2022-08-19 18:40 ` chase-net

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38742@inbox.vuxu.org \
    --to=chase-net@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).