Re: [sqlite] sqlite in a shell

The MSYS "start" command just circumvents the problem by starting a new clunky Windows cmd window. The Cygwin, Emacs and remote users logging into a Windows box via telnet/ssh who prefer to work in their native terminal program either have to hack the sqlite3 shell.c code to force an interactive

Re: [sqlite] sqlite in a shell

[EMAIL PROTECTED] wrote: The shell likely does not believe that it is running interactively for some reason, and so is not presenting prompts. Look at the documentation for the shell to figure out how to tell it to go into interactive mode. Derrell You are correct. This is a common probl

Re: [sqlite] sqlite in a shell

This problem stems from the fact that isatty() is not reliable on Windows for non-cmd.exe terminals. Postgres has the same problem, for what it is worth: http://archives.postgresql.org/pgsql-hackers/2005-09/msg01446.php A commandline flag should probably be added to shell.c to force an interact

Re: [sqlite] sqlite in a shell

rahed <[EMAIL PROTECTED]> writes: > Joe Wilson <[EMAIL PROTECTED]> writes: > >> I've seen this same behavior when running a MinGW-compiled sqlite3.exe in >> the cygwin shell. It has >> something to do with the lack of flushing of information written to stdout >> (until close() anyway). >> If you

Re: [sqlite] sqlite in a shell

It seems that the sqlite3.exe shell buffers output of some shell directives (.help) when compiled with a non-cygwin compiler and run in a non cmd.exe Windows shell - but oddly, it does not buffer the output of errors, other directives (.dump), or any SQL commands: cygwin$ sqlite3.exe .help some

Re: [sqlite] sqlite in a shell

Joe Wilson <[EMAIL PROTECTED]> writes: > I've seen this same behavior when running a MinGW-compiled sqlite3.exe in the > cygwin shell. It has > something to do with the lack of flushing of information written to stdout > (until close() anyway). > If you blindly type in the sqlite commands - it d

Re: [sqlite] sqlite in a shell

I've seen this same behavior when running a MinGW-compiled sqlite3.exe in the cygwin shell. It has something to do with the lack of flushing of information written to stdout (until close() anyway). If you blindly type in the sqlite commands - it does work. Once you exit the shell via .q you can

[sqlite] sqlite in a shell

I can run sqlite3 from a windows cmd but running it from msys shell or emacs shell doesn't work. No sqlite prompt and I have to interrupt the process with Ctrl c. Does anyone know the cause? Thank you. -- Radek