ScriptingConsoleEdit text is turn red after incorrect backward-searching is done

Open
#7,154 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
desktop, reverse-engineering

Research direction

Start with the ScriptingConsoleEdit and its LineEdit behavior when Ctrl-R backward search finds no history entry. Reproduce the sequence in the issue, then verify that executing the unmatched command does not leave subsequent console text red and that normal backward-search exit behavior still works.

Written by the indexing model from the issue text.

Description

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

Version and Platform (required):

  • Binary Ninja Version: 5.1.7982-dev Personal (227f8a61)
  • OS: macOS

Bug Description:
Text in the python's scripting console turning red after backward-searching

Steps To Reproduce:

  1. Ctrl-R in scripting console
  2. Type command that is not in the history, so the text goes red
  3. Execute this command (press enter)
  4. Now all your text inside of LineEdit of console is red, until you use backward-search again and exit it in a "right" way

Screenshots/Video Recording:
Image

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.