- Aug
- 294
- 1
I don't think I'm cheating with the timer at all, the work is done in the
loop
I like the one liner idea, but its not going to happen with a batch file or
any plugin if we are talking ONE LINE
the creation can't be measured the deletion doesn't really matter
loop
I like the one liner idea, but its not going to happen with a batch file or
any plugin if we are talking ONE LINE
the creation can't be measured the deletion doesn't really matter
> |setlocal
> |set >%@unique[]
> |set data=%@execstr[*dir /a:-d /h /o:-t /f]
> |timer on
> | do r=0 to %@lines[%data]
> | echo %@field["=",-1,%@line[%data,%r]]
> | enddo
> |timer off
> |del /q %data
> |endlocal
>
> You're cheating with the timing by not counting the time to
> create/delete the file.
>
> |Still to much ?
>
> I really think it should be a one-liner.
>
>
> Code:
> ---------
> v:\> do v in /T"=" /L %@varnames[] ( echo %v )
> ALLUSERSPROFILE
> APPDATA
> CLIENTNAME
> CommonProgramFiles
> (snip)
> ---------
> In its latest incarnation, @VARNAMES[[regex]] returns an =-sepatated
> list of variable names [matching regex]. I want a way to reverse the
> sense of the regex matching (i.e., process a non-match). That's not
> built-into regexes themselves. Some syntaxes allow embedded comments,
> like Perl's (?#comment) which I could use, but that's not universal. I
> could use something as simple as prefixing the regex with '!' to
> reverse the match sense. If the user wanted to start the regex with a
> real '!' he'd just have to use an extra one. Sound good?
>
>
>
>