Take Command v10 beta build 39 uploaded

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
May 26, 2008
481
3
#4
One thing that's weird is the full TCMD takes over 5 seconds to appear after I acknowledge the beta expiration dialog. TCC starts instantly.
 
Jun 2, 2008
284
1
Newton, MA
#5
I just tried setting TCC to use local aliases, and even with build 39 it crashes upon loading my alias file -- same as previous builds.

-- Jay Sage

I've uploaded build 39 to the ftp beta area:

ftp://jpsoft.com/beta/tcmd.exe

This includes a fix for a problem with resizing local lists (alias, function, & history), a fix for a problem when defining ftype's with no file argument (i.e., %1), and some help updates.
 
May 20, 2008
110
0
CA
#8
Something wonky at home, will try to uninstall and re-install, here at work it installed fine over build 34, I'll let you know if it doesn't work at home later tonight

fromano wrote:



Not reproducible here. Anybody else seeing this?

Rex Conn
JP Software
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#9
Rod Savard wrote:

> One thing that's weird is the full TCMD takes over 5 seconds to appear after I acknowledge the beta expiration dialog. TCC starts instantly.
Assuming it's happening on every startup (the first one takes a couple
of seconds longer than subsequent ones), then you probably have a
disconnected drive or sharename that TCMD is trying to read at startup.

Rex Conn
JP Software
 
May 26, 2008
481
3
#10
Assuming it's happening on every startup (the first one takes a couple
of seconds longer than subsequent ones), then you probably have a
disconnected drive or sharename that TCMD is trying to read at startup.
It was on every startup. All mapped drives are connected, but I do have about 10 of them and one is across a WAN connection (which admittedly also slows down the opening of "My Computer" too). I'll do more testing tomorrow (it's my work system), but that's probably it.
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#11
That's most likely due to the fact that TCMD has to populate the directory
tree and list view windows. If you have any network shares mapped, those
typically can take awhile.

-Scott

Rod Savard <> wrote on 01/20/2009 03:14:38 PM:


> One thing that's weird is the full TCMD takes over 5 seconds to
> appear after I acknowledge the beta expiration dialog. TCC starts
instantly.
 
May 26, 2008
481
3
#12
It was on every startup. All mapped drives are connected, but I do have about 10 of them and one is across a WAN connection (which admittedly also slows down the opening of "My Computer" too). I'll do more testing tomorrow (it's my work system), but that's probably it.
Ok, I unmapped the drive that connects to a server across the WAN. This solves the slow opening of "My Computer", but it didn't make a difference for Take Command. I then unmapped all drives. Take Command still opens slowly. Takes 5 seconds after the beta prompt. I do think it is network-related though because I see activity on the network icon in the tray.
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#13
When I type a batch name at the command line I can leave off the extension
and it executes properly. However, if I want to debug my batch script I
have to specify the extension.

For example, IDE chksubst, does not work. I get a file not found error.
But, IDE chksubst.btm, does work.

Can IDE automatically look for the file with common batch extensions? E.g.
BAT,CMD,BTM.

TCC 10.00.39 Windows XP [Version 5.1.2600]
TCC Build 39 Windows XP Build 2600 Service Pack 3

-Scott
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#14
More IDE issues:

I have a fairly simple batch file that will show me my non-subst'ed local
drives.

Code:
unset /q sl & for /f "delims=" %d in ('subst') set sl=%[sl]%@left[1,%d]
CDD /A |! do d in @con
  :: networked and CD drives are skipped
  if %@remote[%d]==1 .or. %@cdrom[%d]==1 iterate
  :: subst'ed drives are skipped too
  if %@index[%sl,%@left[1,%d]] NE -1 iterate

  :: d is a valid drive letter
  echo %@left[2,%d]
enddo
If I attempt to step-into the 2nd line (the CDD /A line) the rest of the
batch file executes with no step-into executed. Note that line is using
the new local pipes mechanism.

-Scott

samintz <> wrote on 01/21/2009 01:25:25 PM:


> When I type a batch name at the command line I can leave off the
extension

> and it executes properly. However, if I want to debug my batch script I

> have to specify the extension.
>
> For example, IDE chksubst, does not work. I get a file not found error.

> But, IDE chksubst.btm, does work.
>
> Can IDE automatically look for the file with common batch extensions?
E.g.

> BAT,CMD,BTM.
>
> TCC 10.00.39 Windows XP [Version 5.1.2600]
> TCC Build 39 Windows XP Build 2600 Service Pack 3
>
> -Scott
>
>
>
>
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#15
samintz wrote:

> More IDE issues:
>
> I have a fairly simple batch file that will show me my non-subst'ed local
> drives.
>
>
> Code:
> ---------
> unset /q sl & for /f "delims=" %d in ('subst') set sl=%[sl]%@left[1,%d]
> CDD /A |! do d in @con
> :: networked and CD drives are skipped
> if %@remote[%d]==1 .or. %@cdrom[%d]==1 iterate
> :: subst'ed drives are skipped too
> if %@index[%sl,%@left[1,%d]] NE -1 iterate
>
> :: d is a valid drive letter
> echo %@left[2,%d]
> enddo
> ---------
> If I attempt to step-into the 2nd line (the CDD /A line) the rest of the
> batch file executes with no step-into executed. Note that line is using
> the new local pipes mechanism.
You cannot step into any kind of pipe. Whether the pipe is local is
irrelevant; the piping process used is hidden from the rest of TCC.

Rex Conn
JP Software
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#16
samintz wrote:

> When I type a batch name at the command line I can leave off the extension
> and it executes properly. However, if I want to debug my batch script I
> have to specify the extension.
>
> For example, IDE chksubst, does not work. I get a file not found error.
> But, IDE chksubst.btm, does work.
>
> Can IDE automatically look for the file with common batch extensions? E.g.
> BAT,CMD,BTM.
Definitely not through the IDE command -- the IDE supports editing many
other types of files.

I'll take a look at allowing that in the BDEBUGGER command.

Rex Conn
JP Software
 
#17
rconn wrote:
| samintz wrote:
|
|
| ---Quote---
|| When I type a batch name at the command line I can leave off the
|| extension and it executes properly. However, if I want to debug my
|| batch script I have to specify the extension.
||
|| For example, IDE chksubst, does not work. I get a file not found
|| error. But, IDE chksubst.btm, does work.
||
|| Can IDE automatically look for the file with common batch
|| extensions? E.g. BAT,CMD,BTM.
| ---End Quote---
| Definitely not through the IDE command -- the IDE supports editing
| many other types of files.
|
| I'll take a look at allowing that in the BDEBUGGER command.

I have a keystroke alias to insert "BDEBUGGER %@SEARCH[" - of course the
cursor has to be at the beginning of the line, and edit mode set to
"insert", and the matching "]" inserted manually. Perhaps the BDEBUGGER
command could be enhanced to perform the @SEARCH automatically if needed,
and report "file not found" only if the search fails.
--
Steve
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#18
So how can I debug all the statements in the DO loop? If I have to rewrite my batch script to make the debugger happy, that defeats the purpose of having a debugger.

-Scott

samintz wrote:

You cannot step into any kind of pipe. Whether the pipe is local is
irrelevant; the piping process used is hidden from the rest of TCC.

Rex Conn
JP Software
 

rconn

Administrator
Staff member
May 14, 2008
10,096
85
#19
samintz wrote:

> So how can I debug all the statements in the DO loop? If I have to rewrite my batch script to make the debugger happy, that defeats the purpose of having a debugger.
This doesn't have anything to do with v10; the batch debugger has never
supported debugging statements inside a pipe.

The easiest way to debug it would be to have the first command redirect
output to a file and the DO read its input from the file. When
everything is working as desired just change the redirection to a pipe.

Rex Conn
JP Software