| |||||||||||||
a filename issue or a shell issue?a filename issue or a shell issue?Posted Mar 25, 2009 21:10 UTC (Wed) by renox (subscriber, #23785)Parent article: Wheeler: Fixing Unix/Linux/POSIX Filenames
As the biggest problem is linked to text interpretation, I think that a 'PowerShell' kind of shell which use objects instead of text for communication between programs would be more robust against 'weird' characters in the filenames.
(Log in to post comments)
a filename issue or a shell issue? Posted Mar 25, 2009 21:53 UTC (Wed) by alecs1 (guest, #46699) [Link]
noatime/relatime discussion
accelerated indirect rendering and combinations kernel mode setting "better than POSIX" restrictions on filenames Microsoft shell competes with Unix shell
Keep them coming :)
a filename issue or a shell issue? Posted Mar 26, 2009 18:30 UTC (Thu) by quotemstr (subscriber, #45331) [Link]
By making hell freeze over, we can win the global warming battle. :-)
a filename issue or a shell issue? Posted Mar 25, 2009 23:37 UTC (Wed) by dwheeler (guest, #1216) [Link] Perhaps, but even systems which have objects get burned. As noted earlier, the Python developers have had a hard time.... they've switched to Unicode as their main text representation, but Unix filenames aren't text... they are essentially binary blobs! If filenames were always UTF-8, there'd be no problems. Similarly, perl programs get trashed if filenames begin with <.
|
|||||||||||||