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 see the entire output of the session.
One workaround is to use a cygwin-compiled sqlite3.exe. Perhaps hacking the sqlite shell not to buffer its console output would also do the trick. --- rahed <[EMAIL PROTECTED]> wrote: > 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 > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
