desed - GitLite

KO | EN

gitlite — search

#javascript #python #react #go #android #machine-learning #docker #java #windows #awesome #kubernetes #pytorch #openai #open-source

desed

(★ 1,215)

Debugger for Sed: demystify and debug your sed scripts, from comfort of your terminal.

파일 탐색기

최종 버전 다운로드 (.zip)

- - rust.yml
- launch.json
- update-desed-git-pkgbuild.sh
- update-desed-pkgbuild.sh
- desed.gif
- graph-challenge.txt
- graph-problem.sed
- README.md
- sedtris.sed
- test.sed
- test.txt
- - inotify.rs
  - kqueue.rs
  - mock.rs
  - mod.rs
- - communication.rs
  - debugger.rs
  - mod.rs
  - parser.rs
- - generic.rs
  - mod.rs
  - tui.rs
- cli.rs
- main.rs
.gitignore
Cargo.lock
Cargo.toml
desed.1
LICENSE
publish.sh
README.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/SoptikHa2/desed

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd desed

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. 공식 설치 스크립트

쉬움 추천

사전 준비물

Rust (rustup) cargo 명령어를 쓰려면 Rust가 필요합니다.

cargo install --path .

이 명령어를 터미널에 그대로 입력해 실행하세요.

cargo install desed

crates.io에 배포된 패키지를 빌드해서 설치합니다. 레포를 직접 클론할 필요가 없습니다.

✅ 설치 후 새 터미널을 열고, 프로그램의 버전 확인 명령(예: --version)으로 정상 설치됐는지 확인하세요.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

3. Rust

보통

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Rust (rustup) rustup으로 설치하면 cargo도 함께 설치됩니다.

cargo install --path .

이 명령어를 터미널에 그대로 입력해 실행하세요.

cargo install desed

crates.io에 배포된 패키지를 빌드해서 설치합니다. 레포를 직접 클론할 필요가 없습니다.

✅ cargo build가 에러 없이 끝나면 성공입니다. target/ 폴더에 실행 파일이 생성됩니다.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Desed
Demystify and debug your sed scripts, from comfort of your terminal.

![desed usage example](https://raw.githubusercontent.com/SoptikHa2/desed/master/img/desed.gif)

Desed is a command line tool with beautiful TUI that provides users with comfortable interface and practical debugger, used to step through complex sed scripts.

Some of the notable features include:

- Preview variable values, both of them!
- See how will a substitute command affect pattern space before it runs
- Step through sed script - both forward and backwards!
- Place breakpoints and examine program state
- Hot reload and see what changes as you edit source code
- Its name is a palindrome

## Install

### Alpine Linux

`aports/testing/desed`

### Arch Linux

Via AUR: [desed-git](https://aur.archlinux.org/packages/desed-git/) or [desed](https://aur.archlinux.org/packages/desed/) as stable version.

### DragonFly BSD

```sh
pkg install desed
```

### Fedora

```sh
dnf install desed
```

### FreeBSD

```sh
pkg install desed
```

### Void Linux

```sh
xbps-install -S desed
```

### Source

```sh
git clone https://github.com/soptikha2/desed
cd desed
cargo install --path .
cp "desed.1" "$(manpath | cut -d':' -f1)/man1"
```

### Cargo

```
cargo install desed
```

### Precompiled binaries

See [releases](https://github.com/SoptikHa2/desed/releases).

### Dependencies:

Development: `rust`, `cargo` (>= 1.38.0)

Runtime: `sed` (GNU version, >= 4.6) (desed works on BSD if you installed `gsed`)

## Controls

- Mouse scroll to scroll through source code, click on line to toggle breakpoint
- `j`, `k`, `g`, `G`, just as in Vim. Prefixing with numbers works too.
- `b` to toggle breakpoint (prefix with number to toggle breakpoint on target line)
- `s` to step forward, `a` to step backwards
- `r` to run to next breakpoint or end of script, `R` to do the same but backwards
- `l` to instantly reload code and continue debugging in the exactly same place as before
- `q` to [quit](https://github.com/hakluke/how-to-exit-vim)

# Contributing

This codebase is currently not under active development (I'll hopefully get to rewriting the parser, fr. I have written this as my first rust project, and it really shows in the code quality.), but I'm reviewing and accepting PRs. Note that this codebase is human-written. I do not mind LLM-assisted/written code, but if you do not write it by hand, please do review it by hand. Thank you!

# FAQ

## How does it work?
GNU sed actually provides pretty useful debugging interface, try it yourself with `--debug` flag. However the interface is not interactive and I wanted something closer to traditional debugger.

## Does it really work?
Depends. Sed actually doesn't tell me which line number is it currently executing, so I have to emulate parts of sed to guess that. Which might not be bulletproof. But it certainly worked good enough to debug tetris without issues.

## Why sed??

Sed is the perfect programming language, [especially for graph problems](https://tildes.net/~comp/b2k/programming_challenge_find_path_from_city_a_to_city_b_with_least_traffic_controls_inbetween#comment-2run). It's plain and simple and doesn't clutter your screen with useless identifiers like `if`, `for`, `while`, or `int`. Furthermore since it doesn't have things like numbers, it's very simple to use.

## But why?

I wanted to program in sed but it lacked good tooling up to this point, so I had to do something about it.

## Why?

Because it's the standard stream editor for filtering and transforming text. And someone wrote [tetris](https://github.com/uuner/sedtris) in it!

## Is this a joke?

I thought it was. But apparently it's actually useful for some people.

# What people say about desed

> Amusingly, in French, "desed" sounds like "décéde", which means die / decease. That's quite a fitting name for a tool one would use in "I need to debug a sed script" situations!
- [mlegendre](https://news.ycombinator.com/item?id=41455667)