No way to clear command history in RPC console or reset the console without restarting the node

[waketraindev]

Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo

• I still think this issue should be opened here

Report

No way to clear the command history of a RPC console. With the history remaining until client reset.

Please add a way to either clear the command history or fully reset the console.

Thanks in advance

[achow101]

There's already a clear history button in the top right corner of the console window, next to the font size buttons. It works fine for me.

[waketraindev]

There's already a clear history button in the top right corner of the console window, next to the font size buttons. It works fine for me.

Hello and thank you for the reply. I'm actually talking about the command input history in RPC console, the one in the input box where you use the arrow keys to browse and not the output/results/scrollback window that actually gets cleared.

The output gets cleared and the input remains regardless if you close wallet, RPC console. It only resets by restarting the node

Hope that clears it

[waketraindev]

My take on the fix,

#882

[Geremia]

Restarting bitcoin-qt doesn't clear the command history for me.

[1440000bytes]

The output gets cleared and the input remains regardless if you close wallet, RPC console. It only resets by restarting the node

This is a bug and core does not clear the history for migratewallet RPC from the console.

// don't add private key handling cmd's to the history
const QStringList historyFilter = QStringList()
    << "signmessagewithprivkey"
    << "signrawtransactionwithkey"
    << "walletpassphrase"
    << "walletpassphrasechange"
    << "encryptwallet";


}

https://github.com/bitcoin-core/gui/blob/master/src/qt/rpcconsole.cpp#L73C1-L81C2

[1440000bytes]

Related pull request: #901

[waketraindev]

A note that some rpc commands like importdescriptors, getdescriptorinfo do not get filtered or their parameters hidden.
They might contain corrections by the user and linger in the history until shutdown.

A way to fully reset the console without restarting the node seems necessary.