Tags command doesn't raise an error when the file is not stored

[botherder]

If a user tries to add tags to a file which is not stored, the tags command currently doesn't display any error. This is a corner case, as normally a user should understand the mechanics of Viper storage and repository, but a better error handling is required.

[GelosSnake]

I wonder why not automatically storing every new file?

[botherder]

Because I don't want to pollute my projects or repositories with files I'm inspecting and turn out to not be interesting. Also, sessions are used for temporary analysis of files and binary data extracted through other modules (like PE32 resources, email attachments and what not).
If we were to automatically store every file, the repository would be complete mess.

[botherder]

Fixed with 1d4273f.