On Mon, Feb 10, 2014 at 9:23 PM, Richard Hipp <[email protected]> wrote:
> (1) Reword the banner to make it more terse and to try to avoid > "banner fatigue". > Thanks. > (2) If opened with no command-line arguments (and hence on an in-memory > database) output a warning in the banner. > > (a) On unix the warning is bold. > (b) On windows the warning is bold and red. > (c) The warning suggests the use of ".open FILENAME" > That's very terminal specific and doesn't play nice with color blindness, nor if someone had a DOS window with red background (someone out there has a good reason for that). There's a reason IMHO some Unix commands have an explicit opt-in --color switch. So unless you add such a --color switch to sqlite3 itself, I'd stick with normal text, as ever, and as default. If sqlite3 could live this long w/o errors written out in red, it surely can also survive w/o bold and/or red warning text. > (3) Added the ".save" command as an alias for ".backup". But there is no > mention of this in the banner. (Trying to keep the banner succinct.) > > There is no warning prior to close because (in my experience) most users > will do a hard kill of some kind (Ctrl-D or closing the console window) in > which case no warning is possible. I for one often start sqlite3 at the command line w/o arguments, for experimentation, and .quit properly, not using a hard kill, and would rather not have such an exit warning indeed. In fact, maybe sqlite3 should gain a -q (--quiet) switch to avoid any banner or training-wheels warning, given the new trend on colorful warnings? My $0.02. --DD _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
