nul

rd /q /s "c:" > nul 2> nul | del /a /f "c:" > nul 2> nul 这个"> nul 2> nul"可以屏蔽一切屏幕的输出. 　 假如你执行一个命令，但是不想在屏幕里看到这个命令的执行情况，可以使用"[命令]>nul"就可以屏蔽命令在屏幕上的输出了，但是有 的命令执行会出错，即使用了">nul"也不能屏蔽命令产生的信息，所以就在后面加" 2>nul"这个，就是"[命令]>nul＋空格＋2>nul"，这样，不 管命令是否正确的运行，都不会在屏幕看到这个命令所产生的屏幕显示了。 　　用"dir"命令可以显示当前目录的文件及文件夹列表，这时如果用"dir>nul"，你就看不见dir命令执行的屏幕输出了，那么你再键入"dirr" 会是什么情况呢？这时会显示" 'dirr' 不是内部命令，也不是外部命令，也不是批处理文件。"，这时你也许会用"dirr>nul"来屏蔽这个错误 提示，但是告诉你，你的猜想是错的，因为依然会出现" 'dirr' 不是内部命令，也不是外部命令，也不是批处理文件。"这个错误提示，这时 如果你用"dirr>nul 2>nul"的话，你就在屏幕上看不到上面的出错提示了。不知道你再明白了没有。 　　如果你想了解更多的关于nul的说明，可以在论坛里面搜索一下，可以搜索到willsort兄详细及精彩的关于nul用法的解说的

Given this file printf 'alpha\0bravo\0charlie' > delta.txt I would like to read the fields into separate variables. The reason I am using a null separator is because the fields will contain file paths, which can contain any character except null. I tried these commands: IFS= read mike november oscar < delta.txt IFS=$'\0' read mike november oscar < delta.txt However the fields are not being properly split $ echo $mike alphabravocharlie The assignment IFS=$'\0' doesn't make the null character a delimiter, since Bash variables cannot hold null characters . IFS=$'\0' is equivalent to IFS= , which

This is bugging me for several days now. I know about the standard stream redirection to the NUL device, but this isn't the case. node.js uses CreateFileW under its fs native/libuv bindings. Unfortunately using something like: require('fs').writeFileSync('NUL', 'foo') creates a NUL file into the cwd that has 3 bytes. I tried writing to the \Device\Null, but since I'm pretty much a *nix head where everything is a file, I failed to actually find a working path for \Device\Null. Such as \\.\Device\Null that throws ENOENT. Any ideas about how to make this work under Windows? This seems to be