If you use #vim to edit #Ghidra sources, beware that some build scripts try to handle all files in a directory, so .swp’s can cause build errors.

#ProTIp

(Neovim stores swap files under your config directory by default, so the situation is better there)

@buherator lol

@pancake Now that I think about it, IIRC this is also related to the certification.manifest issue I described in the other post: it seems like a way to ensure that no intellectual property of dubious origin ends up in the code. You have to explicitly state that new files are OK to be included in the project (kind of an inverse .gitignore).

@pancake @buherator How is this a reason not to use ghidra?

@joxean @buherator because I use vim all the time, i dont feel comfortable in any other editor, and even if this is solvable with custom configuration in vim or other editors, it feels like a ver inconvient place to script anything. Ida is way worse for scripting, but my experience in ghidra is totally out of my workflow

@pancake @joxean To be fair the issue I brought up only comes up during more "low-level" development (specifically Processor modules), certainly not during scripting. With Python scripts you can just configure a script directory and write your scripts there with any editor, and you can even fire up a headless instance from some vim command to run it. Java is more cumbersome (as Java usually is) but one of my side-quests is to document how to set up a proper devenv for it.

@buherator @pancake @joxean why not invest that time on switching to @radareorg?

@astralia @pancake @joxean @radareorg I like the warm fuzzy feeling of running NSA code (financed by US taxpayers) on my machine :)

@buherator @pancake @joxean @radareorg uuuuuuuu risky trisky! 😜