Amateur radio related code written in go
used for comparing symbol sizes in binaries
MGRS/UTM/UPS Coordinate Converter (partial port of NGA's geotrans)
A tool to extract gitlab issues in text and CSV format
prompt library in go inspired by networking equipment shells
go wrapper around the pico text to speech engine
AirSpy's usemode driver and associated tools
A modern text indexing library for go
A React-based UI toolkit for the web
A React tiling window manager
fork in 19 days
PR opened radareorg/radare2
Add the missing return flag inversion so reading from stdin and a regular file both return zero on success.
pr created time in a month
UNIX-like reverse engineering framework and command-line toolset
fork in a month
Yes, but grep/curl have process exit codes that can be used to determine if an error occurred. As far as I could tell, there's no way to identify if a command was successful other than by adding support for parsing the possible outputs of each individual command.
comment created time in a month
started time in a month
Is your feature request related to a problem? Please describe.
I was working on a r2-pipe Go wrapper that read radare2's stderr to detect and report errors. This mostly works, except there are a lot of places where eprintf is used for non-error messages:
Describe the solution you'd like Replace some non-error usages of eprintf with r_cons_printf
Would there be interest in merging some commits in that do that, or is there a better solution?
created time in a month
started time in 4 months