claude-re-setup/ghidra/preferences at main - claude-re-setup - JSAID Git Server

Linus/claude-re-setup

Files

T

LinusandClaude Opus 5.5 51573544a4 Really enable Ghidra's Developer plugins in both tools

A bare <PACKAGE NAME="Developer" /> only adds the package's RELEASED
plugins, so half of them (the STABLE ones) were missing and Configure
showed Developer unticked. The project window wasn't configured at all.

- CodeBrowser: insert ghidra/codebrowser-developer.xml, which lists the
  STABLE plugins explicitly, into the default CodeBrowser.tool in
  Public_Release.jar.
- Project window: it has no default config to patch, so ship
  ghidra/FrontEndTool.xml in the user settings with its three
  Developer plugins.
- Pre-creating the settings dir makes Ghidra show its user agreement;
  ghidra/preferences sets USER_AGREEMENT=ACCEPT, the value Ghidra
  writes by itself on a fresh start.

Verified by closing Ghidra cleanly: it rewrites FrontEndTool.xml from
the loaded plugins and kept all three Developer plugins.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-11-02 12:58:19 +01:00

5 lines

249 B

Plaintext

Raw Permalink Blame History

 # Same value Ghidra writes on its own on a fresh start (no settings dir).
 # Needed because the image pre-creates the settings dir for FrontEndTool.xml,
 # which otherwise makes Ghidra show its user agreement dialog every start.
 USER_AGREEMENT=ACCEPT