Closed radare closed 3 years ago
I really got used to \
for io, especially in r2frida. Not a big fun of suddenly changing all these commands, but any change will be well accepted by me. Why is there this need of changing it? Lets keep only \
?
\ is used for escaping especial chars, it's problematic for the new shell parser because it makes it more complex (one extra exception.
I really got used to
\
for io, especially in r2frida. Not a big fun of suddenly changing all these commands, but any change will be well accepted by me. Why is there this need of changing it? Lets keep only\
?
@enovella what do you mean? I don't see any command that has \
. Does r2frida adds commands with \
?
I prefer ‘ than . In ES layout is 1 key instead of 2. Backslash conflicts with escaping
On 22 Apr 2020, at 09:22, Riccardo Schirone notifications@github.com wrote:
I really got used to \ for io, especially in r2frida. Not a big fun of suddenly changing all these commands, but any change will be well accepted by me. Why is there this need of changing it? Lets keep only \?
@enovella what do you mean? I don't see any command that has . Does r2frida adds commands with \?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I have removed it from the 4.6 milestone because I think it's not an urgent issue to fix and it requires further discussion and feedback from the community.
At least \
seems really bad.
I think that the current use of ':' is not fair enough to be that accessilble, and can be easily delegated to #: for example without making the command parser more complicated.
The idea is to have a single char to run commands thru io->system. this is heavily used in r2frida and will be good to have it easy to use from any keyboard layout.
The problem i see is with
.:
because we would want to run the output of that command and right now .: is for tcp :this one can be probably renamed to
.=9090
. see also:here we have a conflict but maybe we can just ignore the = ones. and make those commands like this: (consistent with = and not using :
The problem with =! is that is confusing with != and =!= and !=!. so we can probably remove them despite it is useful to enter into a remote io shell