Show terminal persistent sessions setting when searching for "history"

[miguelsolorio]

I'm always returning to projects and see the terminal messages filled with the same repeated message and would like to clean them up and not be shown as I see no value in them for myself.

Current

Desired

[Tyriar]

This bugs me too, #142855 tracks only showing it once in this case by avoiding saving new parts if there is no terminal input, similar to how it only saves and restored in the first place if the terminal has been interacted with. I don't think we should be hiding the message all together as it's misleading what is part of this shell's session, command decorations would be broken for the ones that aren't part of this session (look like a bug) and it would show up like this which is a bit weird:

[miguelsolorio]

Would it be possible to have an option to hide the previous session altogether and just show a new session? That would be a simple approach that would work for me personally, similar to debug.terminal.clearBeforeReusing

[meganrogge]

@misolori you can just create a new terminal altogether by setting terminal.integrated.enablePersistentSessions to false

[miguelsolorio]

@meganrogge thank you! I was searching for a setting and didn't ever find that one, kept looking for "terminal history" and "terminal clear"

[meganrogge]

the name is definitely not discoverable. I wonder if we should change it @Tyriar

[miguelsolorio]

or can we add any meta data or keywords to settings that will be picked up by search? cc @rzhao271

[Tyriar]

tags I guess?

vscode/src/vs/platform/configuration/common/configurationRegistry.ts

Lines 164 to 169 in 82222d6

	/**
	* List of tags associated to the property.
	* - A tag can be used for filtering
	* - Use `experimental` tag for marking the setting as experimental. **Note:** Defaults of experimental settings can be changed by the running experiments.
	*/
	tags?: string[];

[Tyriar]

Oh that doesn't work, @rzhao271 do we have a way to do search keywords?

[Tyriar]

@misolori you actually want terminal.integrated.persistentSessionReviveProcess, the enablePersistentSessions setting will disable process reconnect across window reloads.