timeout option for read that restarts on type

2006-04-08 Thread Juuso Alasuutari 
From: iuso
To: bug-bash@gnu.org
Subject: timeout option for read that restarts on type

Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation 
CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' 
-DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' 
-DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H  -I.  
-I. -I./include -I./lib   -O2 -march=pentium-m -pipe -fomit-frame-pointer
uname output: Linux kamayuq 2.6.16-ck3 #1 PREEMPT Wed Apr 5 01:04:13 EEST 2006 
i686 GNU/Linux
Machine Type: i686-pc-linux-gnu

Bash Version: 3.0
Patch Level: 16
Release Status: release

Description:
The read command should have an option to use timeout which 
restarts every time a character is typed.

Repeat-By:
Source Mage GNU/Linux uses 'read -t' with a configurable timeout 
value for some of its core operations. It is frustrating to have 
the timeout exceed just as user is in mid-sentence.
The present hack to get around this is to use 'read -t  
-n 1' to capture the first typed char, and then continue after 
that with a second read command without a timeout value.
The downsides to this are obvious. First of all it's impossible 
to backspace the first character typed. It also prevents the use 
of the -e option, which enables arrow, home, and end key usage, 
and lets the user to back up to the previous rows of typed text.

Fix:
[Description of how to fix the problem.  If you don't know a
fix for the problem, don't include this section.]


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

comment

2006-04-08 Thread lyubo hristov 
Hello,

I have a question for you.
How to comment a paragraph in bash file ?
I read a lot of documentation and I dont find anything. May be I miss
It but i need to know.
Thanks in advance


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

[Fwd: [KDE Bug 124960] konsole/bash must not execute CR unconfirmed prompt commands on exit signals]

2006-04-08 Thread thomas schorpp 
From: schorpp
To: bug-bash@gnu.org,[EMAIL PROTECTED]
Subject: -see mail subject-

Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H  -I.  -I../bash -I../bash/include 
-I../bash/lib  -g -O2
uname output: Linux tom1.schorpp.dyndns.dk 2.6.16 #1 PREEMPT Tue Mar 21 
01:38:42 CET 2006 i686 GNU/Linux
Machine Type: i386-pc-linux-gnu

Bash Version: 2.05b
Patch Level: 0
Release Status: release

Description:
-see attachments-

Repeat-By:
-see attachments-

y
tom



--- Begin Message ---
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
 
http://bugs.kde.org/show_bug.cgi?id=124960 




--- Additional Comments From t.schorpp gmx de  2006-04-07 08:59 ---
yes:

tom1:~# ls -l konsole.txt
-rw-r--r--  1 root root 5 Apr  7 08:29 konsole.txt

tom1:~# grep konsole.txt .bash_history
echo shit > konsole.txt

tom1:~# tail .bash_history
...
echo shit > konsole.txt

schorpp tom1:~$ tail .bash_history
...
su -

now is konsole firing the echo on signal or bash on signal?
i cant see it clearly in the konsole sources.
should i forward a copy of this bug to bashbugs gnu org just 
to be sure the gnu guys are investigating this too?


--- End Message ---
--- Begin Message ---
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
 
http://bugs.kde.org/show_bug.cgi?id=124960 
phil kde org changed:

   What|Removed |Added

   Severity|crash   |normal
 Status|UNCONFIRMED |NEW
  everconfirmed|0   |1



--- Additional Comments From phil kde org  2006-04-06 23:51 ---
Same here. Only occurs when 'su' has been used. I didn't try 'su -' though. Do 
you get the same problem with 'su -'?


--- End Message ---
--- Begin Message ---
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
 
http://bugs.kde.org/show_bug.cgi?id=124960 




--- Additional Comments From t.schorpp gmx de  2006-04-05 21:01 ---
CR=Carriage Return, Enter Key

1. open konsole
2. su to root
3. type some exe/script call like "echo shit_happens > 124960.txt" -dont press 
enter-
4. shutdown system with kde logout.

the command written at the prompt gets executed without confirmation 
by enter.


--- End Message ---
--- Begin Message ---
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
 
http://bugs.kde.org/show_bug.cgi?id=124960 




--- Additional Comments From phil kde org  2006-04-05 18:31 ---
I don't understand what you mean by CR confirmation. Could you explain more 
fully, and give the steps I would need to take to reproduce the bug?


--- End Message ---
--- Begin Message ---
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
 
http://bugs.kde.org/show_bug.cgi?id=124960 




--- Additional Comments From t.schorpp gmx de  2006-04-05 11:25 ---
bash version is 2.05b-26 debian stable.


--- End Message ---
--- Begin Message ---
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
 
http://bugs.kde.org/show_bug.cgi?id=124960 
   Summary: konsole must not execute CR unconfirmed prompt commands
on exit signals
   Product: konsole
   Version: unspecified
  Platform: Debian testing
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: konsole-devel kde org
ReportedBy: t.schorpp gmx de


Version:(using KDE KDE 3.5.2)
Installed from:Debian testing/unstable Packages
OS:Linux

tom1:~# hdlock (without CR execution confirmation!), a customer script to lock 
the hd drives with ata-security is executed on kde logout->system shutdown and 
respective signals.

konsole must not execute scripts or call any CR-unconfirmed 
commands/executables at exit 
signals in any case.

bug severity was set to maximum cause this is a system security hazard that 
leaves 
the system in a broken state.

y
tom


--- End Message ---
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash