radareorg/radare2

Show prompt/visual/graph/disasm/hexdump with 0xff..%x instead

Open

#10,751 opened on Jul 16, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C (23,826 stars) (3,229 forks)batch import
Hacktoberfestenhancementgood first issue

Description

think in improvements that can be done here

https://twitter.com/bezjaje/status/1018787596506451968

see what rax2 does

Contributor guide

Tech stack
cshell
Domain
clitooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
C programmingradare2 internalshexdump formatting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue links to a tweet showing a desired output format and references rax2. Examine rax2's behavior (likely a radare2 tool) to understand the expected '0xff..%x' format. Search the radare2 codebase for hexdump, visual, and prompt formatting code, likely in libr/core/visual.c, libr/core/disasm.c, or shlr/hexdump. Review any existing comments or linked PRs for context. The goal is to modify the format string to use %x instead of the current hexadecimal representation.