pre/post scripting console callback/notification

Open
#4,865 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, python
Domain
api, developer-experience, tooling

Research direction

Start by reviewing the scripting-console API and the referenced startup.py documentation to understand how console commands are currently handled. Done means providing documented pre- and post-command callback or notification points that support the listed plugin use cases, including history, alternate scripting behavior, and autosave workflows.

Written by the indexing model from the issue text.

Description

Component: API Effort: Low Impact: Low UI: Python Console

It would be great if there was a callback for pre/post scripting console commands.

This could let you implement plugins to (among other things):

  • create a global scripting console history
  • implement your own templating/syntax/scripting (in particular you could do this for other scripting consoles that aren't python based, because startup.py gives you most of what you need for this for python itself
  • add something like an "autosave BNDB before running console" command
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.