The problem is not that we allow spaces in file names, it is that we overload their meaning. We use them both as argument seperators as well as within file names. The proper solution is to use a different character as the argument seperator. Then we could type commands that would be very clear, such as, for#i#in#*.ram;#do#if#[#-f#../done/$i#]#;#then#rm#$i;#fi;#done Eric#:-) On Saturday 01 November 2003 19:20, Steve Swantz wrote: > Kent Schumacher wrote: > >>> (I would love to beat the person soundly who decided to allow spaces > >>> and quote characters in file names). > >> > >> File_names_without_spaces_would_make_a_computer_far_less_friendly_for_th > >>e_gr eat_majority_of_desktop_users. ;-) > >> > >> Steve_Swantz > > > > I-fail-to-comprehend-your-point. > > > > Kent ;_) > > What_I_meant_was,_you're_right_that_spaces_in_file_names_make_life_more_dif >f > icult_for_the_programmer._In_fact,_Apple_had_bug_in_an_installer_that_cause >d > _the_loss_of_files_on_drives_that_had_spaces_in_the_file_name._But_putting_ >u > nderscores_in_file_names_is_as_natural_for_the_average_Joe_as_reading_this_ >i > s_for_us._So_we_adapt_our_work_to_the_user_rather_than_them_adapting_to_us. > > Steve > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list