Enhance @EXPAND

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
#1
Please add support for exclusion ranges to @EXPAND. I just came across a
case when I had to manually edit the command line to remove all 16 filenames
matching P* for a Microsoft Word command line.
--
Steve
 
#3
rconn wrote:
| Steve Fábián wrote:
|
|
| ---Quote---
|| Please add support for exclusion ranges to @EXPAND. I just came
|| across a case when I had to manually edit the command line to remove
|| all 16 filenames matching P* for a Microsoft Word command line.
| ---End Quote---
| @EXPAND already supports ranges.

... but the range support excludes exclusion ranges!

>From Topic "f_expand.htm" last edited 9/28/2006. ©2009 JP Software, Inc.:
Exclusion ranges are not supported.

My usage yesterday showed the above statement to be correct.
--

Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,100
85
#4
Steve Fábián wrote:

> rconn wrote:
> | Steve Fábián wrote:
> |
> |
> | ---Quote---
> || Please add support for exclusion ranges to @EXPAND. I just came
> || across a case when I had to manually edit the command line to remove
> || all 16 filenames matching P* for a Microsoft Word command line.
> | ---End Quote---
> | @EXPAND already supports ranges.
>
> ... but the range support excludes exclusion ranges!
>
> ---Quote---
>>From Topic "f_expand.htm" last edited 9/28/2006. ©2009 JP Software, Inc.:
> ---End Quote---
> Exclusion ranges are not supported.
>
> My usage yesterday showed the above statement to be correct.
%@expand[[!p]*]

Rex Conn
JP Software
 
#5
rconn wrote:

| %@expand[[!p]*]

This works in my case, because exclusion can be reduced to a character
position, but exclusion ranges can be much more complex, e.g.
dir /[!descript.ion *.ini x.*] /a:-d /b
lists fewer files than what would be its equivalent
echo @expand[/[!descript.ion *.ini x.*] *,-d]

The same enhancement for @FILES (which has identical syntax) would also be
desirable.
--
Steve