Re: Problem with 'rm -i' in ksh

On 11.01.2025 12:06, Lem Novantotto wrote:

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...

Yes, just these commands in a script work also in my environment.
(That was what I meant when I wrote: "constructing a test sample
from scratch"; it didn't lead me anywhere, since it just wasn't
reproducible in a primitive context like that.)

I think it must have to do with the shell environment that in
some way affects how 'rm -i' behaves. But I have no idea how an
external (shell-environment-)condition could look like that makes
an executed program like 'rm' behave as if all '-i' confirmations
are "magically" considered as being each answered by "no" (without
me typing anything).

Janis

 

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