bug#20288: 24.4; password management in sql-oracle

[Jean-Louis ABRAHAM]

"Is there a command-line switch for
> sqlplus that causes it to use unbuffered I/O? Or maybe some variable
> you can set once connected to SQL?"

 

=> I don't know, I've not set any special settings.

 

"But if you are saying that Emacs 24.3 on the same system and with the
> same version of SQL didn't have that problem, then I don't see how's
> that possible due to buffering. Maybe I'm missing something"

 

=> Could it be a problem in the "comint" functions?

=> I can reproduce the problem a french and swiss-german Windows Version: May be language settings matter?

 

> > Message du 10/04/15 09:40
> > De : "Eli Zaretskii" <eliz@gnu.org>
> > A : "Jean-Louis ABRAHAM" <j-l.abraham@orange.fr>
> > Copie à : 20288@debbugs.gnu.org
> > Objet : Re: bug#20288: 24.4; password management in sql-oracle
> > 
> > > Date: Thu, 9 Apr 2015 23:26:21 +0200 (CEST)
> > > From: Jean-Louis ABRAHAM <j-l.abraham@orange.fr>
> > > Cc: 20288@debbugs.gnu.org
> > > 
> > > In the cmd box I enter:
> > > emacs -Q
> > > 
> > > In Emacs 24.4.1:
> > > 
> > > M-x sql-oracle
> > > User: 
> > > Password: 
> > > Database: 
> > > 
> > > The *SQL* buffer looks like:
> > > 
> > > SQL*Plus: Release 12.1.0.2.0 Production on Thu Apr 9 23:07:25 2015
> > > 
> > > Copyright (c) 1982, 2014, Oracle. All rights reserved.
> > > 
> > > Connected to:
> > > Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
> > > 
> > > SQL> host
> > > Microsoft Windows [version 6.1.7601]
> > > Copyright (c) 2009 Microsoft Corporation. Tous droits r serv s.
> > > 
> > > exit
> > > c:\Users\jean-louis\AppData\Roaming>exit
> > > 
> > > SQL>
> > > 
> > > The problem is that after I enter the "host" command the prompt doesn't
> > > display, only after I hit the key
> > 
> > Most probably, a buffering issue. Is there a command-line switch for
> > sqlplus that causes it to use unbuffered I/O? Or maybe some variable
> > you can set once connected to SQL?
> > 
> > But if you are saying that Emacs 24.3 on the same system and with the
> > same version of SQL didn't have that problem, then I don't see how's
> > that possible due to buffering. Maybe I'm missing something.
> >