again from a private discuassion with Pancake.. he asked me to raise
this issue on the list:
copy pasted from the conversation... it is about the search command ("/")
the command should be something like in vim with escape characters
that would change the normal behaviour, in vim you have
/foobar\c the \c ignores case
in case of radare for cache based search:
/function\k ; as \c you would also use for case sensitive.
If we are at this chapter, personally I find it a bit misleading the
"overloading" of the / command. I would have made somethinglike
/\s[string]; instead of /s ...
what happens if I want to search for the string "a [opcode]"...
or for pattern of len p:
//l=100
the one above has two slashes, again more compatible with vim, and a
bit more intuitive (at least for me...)...
the idea is that search commands would have a search string and then
some further definition as where, how much, how etc., so:
/.*function.*/length=100/domain=keys
or
/.*function.*/l=100/d=cache/
--
rgrds,
mobi phil
being mobile, but including technology
http://mobiphil.com
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
