中国DOS联盟

-- 联合DOS 推动DOS 发展DOS --

联盟域名：www.cn-dos.net 论坛域名：www.cn-dos.net/forum
DOS，代表着自由开放与发展，我们努力起来，学习FreeDOS和Linux的自由开放与GNU精神，共同创造和发展美好的自由与GNU GPL世界吧！

游客: 注册 | 登录 | 命令行 | 搜索 | 上传 | 帮助 »

中国DOS联盟论坛 » DOS批处理 & 脚本技术（批处理室） » [讨论]********findstr/a之用法质疑********

English/Chinese Fix Translation

作者:

标题: [讨论]********findstr/a之用法质疑********

上一主题 | 下一主题

s11ss
银牌会员

积分 2098
发帖 566
注册 2007-9-11
状态离线

『楼主』: [讨论]********findstr/a之用法质疑******** 使用 LLM 解释/回答一下

看到electronixtar兄发的ColorDemo.cmd（http://www.cn-dos.net/forum/viewthread.php?tid=35609&fpage=1）中有一句代码是用findstr来实现显示彩色字符，很佩服前辈的才华啊。我findstr用得少，今晚发现这个命令的/a参数使用有点奇怪，通过findstr/?查看帮助，解释是：

/A:attr 指定有十六进位数字的颜色属性。请见 "color /?"

再看color/?，解释是：

attr 指定控制台输出的颜色属性

颜色属性由两个十六进制数字指定 -- 第一个为背景，第二个则为
前景。

这么说来，对于findstr的参数/a，就应该是输入两个十六进制数字啰。但是实际情况不是，我尝试了n次，发现4个十六进制数字有效（多于4个的取最后4个），而在color命令后则不行。这四位中的后两位数好理解，就是如上述的“指定控制台输出的颜色属性“，而前两位是干什么用的呢？我发现是用来控制所显示的文件名字符串（包括之后的冒号）之间的横线和竖线的显示的（包括其有无及粗细），但又好像不全是，因为有时前两位数会影响到后两位数，致使后两位数失去它们的指定颜色的作用（比如2c04）。

TEST:(似乎构成等差数列，公差为4)
1.（横线）

findstr /a:040a . %systemdrive%\boot.ini*

2.（竖线）

findstr /a:080a . %systemdrive%\boot.ini*

3.（横线+竖线）

findstr /a:0c0a . %systemdrive%\boot.ini*

4.（竖线，注意与第2种情况对比）

findstr /a:100a . %systemdrive%\boot.ini*

5.（横线+竖线，注意与第3种情况对比）

findstr /a:140a . %systemdrive%\boot.ini*

6.（竖线，注意与第2,4种情况对比）

findstr /a:180a . %systemdrive%\boot.ini*

7.（横线+竖线，注意与第3,5种情况对比）

findstr /a:1c0a . %systemdrive%\boot.ini*

8.换成200a就没有横线和竖线了。

9.后面还有，如：(貌似和1c0a一样)

findstr /a:dd0a . %systemdrive%\boot.ini*

10.还有些情况是“表格”里居然什么都没有，或者表格最右端出现一条很粗的竖线，另外注意表格边框上的横线和竖线（不同的参数下会导致边框线有时显示，有时又不显示）。还有有时当你把cmd窗口滚动条向上滑动去看上边的命令执行结果然后回过来看，会发现下面的刚执行过的命令的结果居然变了！灵异事件！（比如5c0a）

再来个测试用批处理：

@echo off

setlocal

set begin=%1

set end=%2

set step=%3

set colo=%4

if "%4" equ "" (

	echo 四个参数：

	echo 1.起始值（两位16进制）：如04

	echo 2.终值（两位16进制）：如2c

	echo 3.公差（10进制）：如4

	echo 4.后两位颜色设置（两位16进制）：如0a

	echo 例如：%0 04 2c 4 0a

	set begin=04

	set end=2c

	set step=4

	set colo=0a

)

set/a n=0x%begin%

set t=test.tmp

pushd %tmp%

if exist %t% goto :test

for /l %%a in (1,1,5) do echo.^ >>%t%

:test

call :10to16 %n%

if %n% lss 16 (set v=0%r%%colo%) else (set v=%r%%colo%)

echo %v%

findstr/a:%v% . %t%*

echo.

set/a n+=%step%

if not %n% gtr 0x%end% goto :test

popd

pause

goto :eof

:10to16

set/a q=%1

	:1c

	set/a r=%q%%%16

	set/a q=%q%/16

	call set r=%%r:10=A%%

	call set r=%%r:11=B%%

	call set r=%%r:12=C%%

	call set r=%%r:13=D%%

	call set r=%%r:14=E%%

	call set r=%%r:15=F%%

	call set r%1=%r%%%r%1%%

if not %q% equ 0 goto :1c

call set r=%%r%1%%

set r%1=

*********************************
注：
以上结论纯粹是我个人观点，大家也来试试，这到底是怎么回事呢？
我的操作系统是:
XP Professional 5.1.2600

Last edited by s11ss on 2007-11-23 at 10:35 PM ]

Seeing that Brother electronixtar posted the ColorDemo.cmd ( http://www.cn-dos.net/forum/viewthread.php?tid=35609&fpage=1 ), there is a line of code that uses findstr to display colorful characters. I really admire the senior's talent. I use findstr rarely. Tonight I found that the use of the /a parameter of this command is a bit strange. By checking the help with findstr /?, the explanation is:

/A:attr Specify the color attribute with hexadecimal digits. Please see "color /?"

Then look at color /?, the explanation is:

attr Specify the color attribute of console output

The color attribute is specified by two hexadecimal digits -- the first is the background, and the second is the foreground.

So, for the /a parameter of findstr, it should be entering two hexadecimal digits. But the actual situation is not like that. I have tried many times and found that four hexadecimal digits are valid (take the last four if there are more than four), while it is not the case after the color command. The latter two digits of these four are easy to understand, that is, as mentioned above, "specify the color attribute of console output", and the first two digits are for what? I found that they are used to control the display of the horizontal lines and vertical lines between the file name strings (including the following colon) (including whether they are present and thickness), but it doesn't seem to be all, because sometimes the first two digits will affect the latter two digits, causing the latter two digits to lose their specified color function (such as 2c04).

TEST: (It seems to form an arithmetic sequence with a common difference of 4)
1. (Horizontal line)

findstr /a:040a . %systemdrive%\boot.ini*

2. (Vertical line)

findstr /a:080a . %systemdrive%\boot.ini*

3. (Horizontal line + vertical line)

findstr /a:0c0a . %systemdrive%\boot.ini*

4. (Vertical line, note the comparison with the second case)

findstr /a:100a . %systemdrive%\boot.ini*

5. (Horizontal line + vertical line, note the comparison with the third case)

findstr /a:140a . %systemdrive%\boot.ini*

6. (Vertical line, note the comparison with the second and fourth cases)

findstr /a:180a . %systemdrive%\boot.ini*

7. (Horizontal line + vertical line, note the comparison with the third and fifth cases)

findstr /a:1c0a . %systemdrive%\boot.ini*

8. Changing to 200a has no horizontal and vertical lines.

9. There are more behind, such as: (it seems to be the same as 1c0a)

findstr /a:dd0a . %systemdrive%\boot.ini*

10. There are also some situations where "the table" has nothing at all, or a very thick vertical line appears at the far right end of the table. Also pay attention to the horizontal and vertical lines on the table border (under different parameters, the border lines may or may not be displayed). Also, sometimes when you slide the scroll bar of the cmd window up to look at the command execution results above and then look back, you will find that the results of the just-executed command below have actually changed! Paranormal event! (such as 5c0a)

Here is another test batch:

@echo off

setlocal

set begin=%1

set end=%2

set step=%3

set colo=%4

if "%4" equ "" (

	echo Four parameters:

	echo 1. Start value (two hexadecimal): such as 04

	echo 2. End value (two hexadecimal): such as 2c

	echo 3. Common difference (decimal): such as 4

	echo 4. Setting of the last two digits color (two hexadecimal): such as 0a

	echo For example: %0 04 2c 4 0a

	set begin=04

	set end=2c

	set step=4

	set colo=0a

)

set/a n=0x%begin%

set t=test.tmp

pushd %tmp%

if exist %t% goto :test

for /l %%a in (1,1,5) do echo.^ >>%t%

:test

call :10to16 %n%

if %n% lss 16 (set v=0%r%%colo%) else (set v=%r%%colo%)

echo %v%

findstr/a:%v% . %t%*

echo.

set/a n+=%step%

if not %n% gtr 0x%end% goto :test

popd

pause

goto :eof

:10to16

set/a q=%1

	:1c

	set/a r=%q%%%16

	set/a q=%q%/16

	call set r=%%r:10=A%%

	call set r=%%r:11=B%%

	call set r=%%r:12=C%%

	call set r=%%r:13=D%%

	call set r=%%r:14=E%%

	call set r=%%r:15=F%%

	call set r%1=%r%%%r%1%%

if not %q% equ 0 goto :1c

call set r=%%r%1%%

set r%1=

*********************************
Note:
The above conclusions are purely my personal views. Everyone can also try it. What is going on here?
My operating system is:
XP Professional 5.1.2600

Last edited by s11ss on 2007-11-23 at 10:35 PM ]

2007-11-23 22:19