Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lem Novantotto <Lem@none.invalid>
Newsgroups: comp.unix.shell
Subject: Re: Problem with 'rm -i' in ksh
Date: Sat, 11 Jan 2025 11:06:43 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <vltjc3$htgh$1@dont-email.me>
References: <vlsqmt$fem4$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 11 Jan 2025 12:06:43 +0100 (CET)
Injection-Info: dont-email.me; posting-host="ae3d9ff2231833ddad4ddf3a2d69e45c";
	logging-data="587281"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19mKjPu4Pe1P6oFQ3zx7CnNPXdBJ2M9yqk="
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:nQtinnxU8wgI0TlB4NxpSWKPG98=
Bytes: 2045

Il Sat, 11 Jan 2025 05:05:48 +0100, Janis Papanagnou ha scritto:

> Does that effect - interaction of rm -i behavior with non-interactive
> ksh, flushing the confirmation messages! - sound familiar to anybody?
> 
> (I get the same behavior with 'ksh 93u' and 'ksh 93u+m', BTW.)

Uhmmm... here it works. But maybe I'm missing something...

>11:59:35<lem@biggy:/tmp/prova$ cat mioscript
#!/bin/ksh
unset f_names
typeset -A f_names
f_names["file1"]=
f_names["file2"]=
f_names["file3 3"]=
echo "${!f_names[@]}"
rm -i "${!f_names[@]}"
>11:59:43<lem@biggy:/tmp/prova$ ./mioscript
file1 file2 file3 3
rm: rimuovere file regolare vuoto 'file1'? n  
rm: rimuovere file regolare vuoto 'file2'? n
rm: rimuovere file regolare vuoto 'file3 3'? n
>12:00:28<lem@biggy:/tmp/prova$ ksh ./mioscript
file1 file2 file3 3
rm: rimuovere file regolare vuoto 'file1'? n
rm: rimuovere file regolare vuoto 'file2'? n
rm: rimuovere file regolare vuoto 'file3 3'? n
>12:00:38<lem@biggy:/tmp/prova$ ksh --version
  version         sh (AT&T Research) 93u+m/1.0.8 2024-01-01
-- 
Bye, Lem
		Talis erit dies qualem egeris