Penguin
Diff: SpacesInPathNames
EditPageHistoryDiffInfoLikePages

Differences between current version and predecessor to the previous major change of SpacesInPathNames.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 4 Last edited on Wednesday, March 22, 2006 5:36:20 pm by LawrenceDoliveiro
Older page: version 3 Last edited on Tuesday, March 21, 2006 8:09:38 pm by JohnMcPherson Revert
@@ -1,5 +1,5 @@
-Unix/Linux allows any character in a path name except __/__ or __[NUL]__. However, embedded spaces, newlines and the like can cause problems for carelessly-written [Shell] scripts (or scripts for carelessly-written shells), and cause some command [PipeLine]s to fail completely. 
+Unix/Linux allows any character in a file/directory name except __/__ or __[NUL]__. However, embedded spaces, newlines and the like can cause problems for carelessly-written [Shell] scripts (or scripts for [ carelessly-written shells|CshProgrammingConsideredHarmful] ), and cause some command [PipeLine]s to fail completely. 
  
 To get around this, the [GNU] versions of find(1) and xargs(1) incorporate special extensions that work together. The __-print0__ option to __find__ causes it to output matching pathnames terminated by __NUL__ characters rather than newlines, thereby avoiding confusion with any embedded newlines that might occur in the pathnames. Correspondingly, the __xargs__ command takes the option __--null__ (shorter synonym __-0__) to indicate that its input is delimited in this way; though on my [SUSE] system I also have to specify __--max-lines=1__ (shorter synonym __-L1__). 
  
 For instance, suppose I have the following files: