[sed] did not replace correctly

Open
#225 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript, shell
Domain
cli

Research direction

Reproduce the provided command with the example test.file and compare shx sed with macOS sed. Start by tracing shx's sed command entry point and its handling of the substitution expression, then verify that both lines produce the expected escaped ampersand output.

Written by the indexing model from the issue text.

Description

low priority sed

With the following test.file:

[&_*]:foobar
"[&_*]:foobar"

With actual sed on macOS:

$ sed 's/\[\([^\&]*\)\&/\[\1\&/g' test.file
[&_*]:foobar
"[&_*]:foobar"

With shx sed:

npx shx sed 's/\[\([^\&]*\)\&/\[\1\&/g' test.txt                             
[&_*]:foobar
"[&_*]:foobar"

Node version: v20.12.2

Dominant language
JavaScript
Stars
1.9k
Forks
52
Avg merge
3d 2h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shelljs/shx

All issues in shelljs/shx

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.