Quickly and easily remove all .s# and .b# files

Travis G wrote on Wed, 11 November 2009 16:13

FOR /F "tokens=*" %%G IN ('DIR /B /A-D /S .s#') DO del "%%G"

FOR /F "tokens=*" %%G IN ('DIR /B /A-D /S .b#') DO del "%%G"

I don't see the advantage over the simpler and more obvious:del .s# .b#

/q /sI use the even simpler:del # /q /s

--

Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

I don't see the advantage over the simpler and more obvious:del .s# .b#

/q /sI use the even simpler:del # /q /s

 

It's only obvious if you know about it

I didn't realize that the del command had a recursive switch, and that

method didn't come up in any of my google searches at the time...

I learn something new all the time... Now if I can just remember it for

next time

"Travis G" <fightspammers@gmail.com> wrote in message

news:hfk1fi$4ci$1@cheetah.cadsoft.de...

I don't see the advantage over the simpler and more obvious:del .s#

.b#

/q /sI use the even simpler:del # /q /s

 

 

It's only obvious if you know about it

I didn't realize that the del command had a recursive switch, and that

method didn't come up in any of my google searches at the time...

 

I learn something new all the time... Now if I can just remember it for

next time

If you want to use windows to quickly do this then:

open windows explorer

right-click on the directory

select search

type .#*

left-click in right pane

ctrl A

del

This can do all your projects if you select the directory high enough up the

tree.

Greg Erskine wrote on Wed, 09 December 2009 01:00

If you want to use windows to quickly do this then:

I was talking about Windows, the command I mentioned is specifically for

CMD.EXE, the standard Windows command line shell.  No penguins or red fruit

were mentioned or implied in my message.

Quote:

open windows explorer

right-click on the directory

select search

type .#*

left-click in right pane

ctrl A

del

I wouldn't call this "quick" compared to a single line command, but yes

that should work too.  You can't script it, include it automatically in

your back procedure, and you have to put up with all that

clickety-clicking, but it would work.

--

Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

"Olin Lathrop" <eagle@embedinc.com> wrote in message

news:hfp2c4$lb1$1@cheetah.cadsoft.de...

Greg Erskine wrote on Wed, 09 December 2009 01:00

If you want to use windows to quickly do this then:

 

I was talking about Windows, the command I mentioned is specifically for

CMD.EXE, the standard Windows command line shell.  No penguins or red

fruit

were mentioned or implied in my message.

 

Quote:

open windows explorer

right-click on the directory

select search

type .#*

left-click in right pane

ctrl A

del

 

I wouldn't call this "quick" compared to a single line command, but yes

that should work too.  You can't script it, include it automatically in

your back procedure, and you have to put up with all that

clickety-clicking, but it would work.

--

Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

Thanks for the clarifaction but I understood what you meant. I use bat or

perl scripts to automate my tasks but that is not normal practice anymore.

Most people prefer Window interfaces. In some work environments you are not

given access to CMD.exe

Greg Erskine wrote:

"Olin Lathrop" <eagle@embedinc.com> wrote in message

In some work environments you are not

given access to CMD.exe

Maybe direct access (via Start->Programs->... or Start->Run) is

disabled. However, the following line inside a .cmd-file always allowed

me to use the command line interactively:

cmd.exe /K

Don't tell your sysadmins

Regards,

Christoph

"Christoph Wurzinger" <christoph.wurzinger@tugraz.at> wrote in message

news:hfq7fa$1un$1@cheetah.cadsoft.de...

Greg Erskine wrote:

"Olin Lathrop" <eagle@embedinc.com> wrote in message In some work

environments you are not given access to CMD.exe

 

Maybe direct access (via Start->Programs->... or Start->Run) is disabled.

However, the following line inside a .cmd-file always allowed me to use

the command line interactively:

cmd.exe /K

 

Don't tell your sysadmins

 

Regards,

Christoph

Shhhh. I worked that one out many years ago. Don't tell anyone.

Greg Erskine wrote on Thu, 10 December 2009 01:32

I use bat or

perl scripts to automate my tasks but that is not normal practice

anymore.

Most people prefer Window interfaces.

That is only because most people don't have a clue about computers and are

afraid of the command line because it looks too computer-ish.  We are on a

technical forum here, specifically for people that know how to design

circuits and can use a complicated program to help with that.  Don't judge

everyone here by what the average idiot does.  Remeber that we are the

people designing the stuff so that the average idiot can continue to be a

idiot.

One of the really nice and important features of Eagle is that it is

essentially command based, with the clickety-click interface mostly layered

on that.  That allows you to use the mouse for some interactions that are

inherently graphical where a pointing device adds real value, but also

allows scripting and encapsulating canned procedures.

Quote:

In some work environments you are not

given access to CMD.exe

I have never been exposed to that and wasn't aware of that, but as has

already been pointed out anyone with enough smarts to run Eagle can

trivially get around that.  It's really more of a intelligence test that

anyone who is here should be able to pass, else they don't really belong

here.

--

Browser access to CadSoft Support Forums at http://www.eaglecentral.ca