When running "pulseview -i foo.sr" users generally expect that PV loads that file (and that file only) in a new/empty session/window. Currently however, that'll generally yield two sessions, the "old" saved one from the last PV run and the new one that the user actually wanted (-i foo.sr), which requires some annoying manual work to get rid of the unwanted "old" session.
I'd like PV to perform non-destructive actions by default, meaning that -i should append the file to the current set of sessions. Instead of changing the behavior for -i, I'd like to implement a switch -n (for --no-sessions) that, when supplied, prevents the previous set of sessions from being restored. This way, supplying -i doesn't destroy the session storage when users don't expect it and if they do want to only show the file supplied by -i, they can supply -n as well. Destroying the session storage then becomes an intended action and won't surprise the user.
Note: -n can then also be used by those who (unfortunately) encounter the issue where PV crashes when the session storage contains invalid data. Before, users would have to locate the session storage and move/delete the file manually - and in the case of OSX, also manually trigger a rebuild of the settings cache.
Fixed in 156f06e95f10587063b97b6b453a603751a0007c, thanks! The new CLI options is -c, and there's bug #973 for potentially adding an -n option as well.