* Fix wording, whitespacing and other minor stuff
* cmd.c: ellaborated yy syntax, improved descriptions
- replace "srcoff" with "origin"
* cmd.c(cmd_autocomplete):
- refactor help into function: render autocomplete types with generic
help subsystem;
- "Types" heading now follow the "Usage" style by not being prefixed
by a pipe character;
* cmd_anal.c: fix whitespaces & help text
* cmd_info.c: fix help text capitalization.
* cmd_print.c:
- fix `pf` cmd help;
- TODO: what pz? is doing here?
* cons.c:
- refactor & better document r_cons_cmd_help();
- fix whitespaces;
* visual & panels modes:
- as of commit 46187fe4e1, '!' no longer
launches the r2048 game. The game itself it broken anyway, even when
running from the Help menu in panels mode;
- transitioning from panels to visual is not 'entering' but actually
swapping/replacing visual panels with just panels, thus...
- reword 'enter into the' to 'swap into' or even just 'enter', e.g.:
"enter into the visual panels mode" -> "enter visual panels mode".
- remove the "(dwm style)" words from a fortune tip, because I have no
idea what it is, and it does not appear to be a valid command in any
of the r2 modes.
- update global help text.
* [WIP 2] Fix wording, whitespacing and other minor stuff
* visual.c:
- r_core_visual_append_help(): first steps merging with
r_cons_cmd_help from cons.c; use consistent colors for headers.
* [WIP 3] Fix wording, whitespacing and other minor stuff
* panels.c(__update_help):
- shorten code and titles;
- add comment to clarify that it is not a copy-paste error;
* [WIP 4] Fix wording, whitespacing and other minor stuff
panels.c, visual.c: tweak help text;
* [WIP 5] Fix wording, whitespacing and other minor stuff
* cmd_help.c: update global help text about visual mode -- it was
outdated and overloaded.
* vmenus.c:
- rename stuff, shuffle around static consts to reflect an actual
ordering when viewing as a help text;
- slightly improve help text rendering;
- fix whitespaces;
* [WIP 6] Fix wording, whitespacing and other minor stuff
* lots of help text changed. still working on proper commit message.
These fortunes make a lot of people unconfortable and can be trigering
for some. Even if they are not active by default, they should have no
place here if you are trying to be a welcoming project.
There are a lot of other ways to be quirky and fun, I see no logical
reason to have these fortunes knowing they will negatively impact
people.
Signed-off-by: Filipe Laíns <lains@riseup.net>
* Use meson install instead of manual installation in meson.py
* Update AppVeyor and docs to use the new meson.py flag format
* Meson.py should use --prefix for install paths and --install is a boolean for Windows and Unix now.
* Removed windows specific restrictions from meson.py
* Ensure that the prefix path is an absolute path
* Fix install options syntax
* Added an optional rootdir path for the meson setup command
Co-authored-by: yossizap <yossizap@users.noreply.github.com>
* Introduce the "devmode" confinement
* Switch base to "core18"
* Install ninja and acr as build dependencies
* Add documentation on how to install from Snap
Co-authored-by: Simos Xenitellis <simos.lists@googlemail.com>
Provide a proper package ID to get rid of the following error:
`No receipt for 'radare2.pkg' found at '/'.`
Prepend a `/` for each returned path by the `pkgutil` command, to make
it an absolute path instead of a relative one.
Avoid invoking the `sudo` command for each file, which speeds up the
command significantly.
Avoid ambiguous signing certificates on macOS.
If a user manually installed a new code signing certificate into the
login keychain as documented, the install script will fail to sign r2
because the `sys/macos-cert.sh` script generates a new certificate in
the System keychain. This results in the following error when signing:
```
org.radare.radare2: ambiguous (matches "org.radare.radare2" in /Users/user/Library/Keychains/login.keychain-db and "org.radare.radare2" in /Library/Keychains/System.keychain)
```
To be constistent with `sys/macos-cert.sh`, change manual certificate
generation steps to install to System keychain instead of login
keychain.
Mention that code signing certificate generation is automated by the
install script before listing the manual steps to generate a new
code signing certificate.
* The image is generated with Gimp, saving as .data (RGB)
* This is 128(W) * 3(RGB) * ?(H) .. the height is computed with the blocksize
* r2 -e hex.cols=128 -qqfcpri doc/cows128.data
