Problem Starting Vim & gVIM

Jan 15, 2009
5
0
Running TCC LE version 10.00.76 on XP SP2

Since I upgrated to Version 75 (on 76 now) I have had problems launching gVim & vim with parameters and basically any part of Vim which calls out to the system.

If I attempt to Launch Vim with a filename or execute a plugin which sends commands out to the shell, causes the following problem:

a) A new TCC LE command window opens outside of TCC LE

b) The following message appears in red "TCC: Unknown command "files\JPSoft\TCMDLE10\TCC.EXE"

c) Vim will 'hang' until the command window is closed.

I have noticed that the path is truncated and is the cause of the problem .

My question is: Why is this happening?

Thanks,

Eric
 
May 20, 2008
3,515
4
Elkridge, MD, USA
Telly wrote:
| Running TCC LE version 10.00.76 on XP SP2

Technically, your question belongs to the LE support NG, it is generic
enough to warrant an anser here.

| Since I upgrated to Version 75 (on 76 now) I have had problems
| launching gVim & vim with parameters and basically any part of Vim
| which calls out to the system.

Is the new build of TCC in the same directory as the previous one? Are you
using the same installation of gVim and vim as before the TCC upgrade?
Reinstalling or upgrading may change the paths where VIM and TCC expect to
find each other.

| If I attempt to Launch Vim with a filename or execute a plugin which
| sends commands out to the shell, causes the following problem:
|
| a) A new TCC LE command window opens outside of TCC LE

I assume this did not happen previously, or you would not have mentioned it.
Have any of the configuration files used by VIM changed? Is VIM running in
the same console window as TCC? A new TCC window usually means that TCC was
not started directly by VIM, but by Windows, possibly through a file
association.

| b) The following message appears in red "TCC: Unknown command
| "files\JPSoft\TCMDLE10\TCC.EXE"
|
| c) Vim will 'hang' until the command window is closed.
|
| I have noticed that the path is truncated and is the cause of the
| problem .
|
| My question is: Why is this happening?

It is best policy to install all console programs in "plain path"
directories, regardless of installer defaults driven by Microsoft's insane
Vista certification criteria. Many programs fail to surround path names
containing spaces or other special characters by quotation marks ("), esp.
when starting another program. My guess is that you installed TCMDLE 10.0.76
in "C:\Program files\JPSoft\TCMDLE10\", that VIM successfully starts a 2nd
TCC instance, and passes it a command which should start a 3rd TCC instance
to do the actual work, which command contains the full unquoted path of
TCC.EXE for that purpose. The 2nd instance TCC parser makes makes hash out
of the incorrect command it receives.

BTW, you did not mention how VIM is started - is it running in a TCMDLE tab?

There are more questions here than answers, but hopefully they will point
you in the right direction.
--
HTH, Steve
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
4,423
85
Albuquerque, NM
prospero.unm.edu
Re: Problem Starting Vim & gVIM

It is best policy to install all console programs in "plain path"
directories, regardless of installer defaults driven by Microsoft's insane
Vista certification criteria.

Amen. But if you have installed in a path containing a space, you can often work around problems by adding a line

Code:
set comspec=%@sfn[%comspec]

to your TCSTART.BTM file.
 
Jan 15, 2009
5
0
Charles,

Thank you. This resolved my problem.

Eric

Amen. But if you have installed in a path containing a space, you can often work around problems by adding a line

Code:
set comspec=%@sfn[%comspec]
to your TCSTART.BTM file.
 
Jan 15, 2009
5
0
Steve,

I normally try to NOT install apps with a path containing spaces. However I didn't for TCC LE. Yes I was launching Vim & gVim from a tab. Yes, your analysis appeared to match my problem.

The member who responded to your post, provided a workaround for my problem.

Next time there is a TCC LE update, I will install it into a directory structure containing no spaces. Lesson Learnt.

Thanks,

Eric

Telly wrote:
| Running TCC LE version 10.00.76 on XP SP2

Technically, your question belongs to the LE support NG, it is generic
enough to warrant an anser here.

| Since I upgrated to Version 75 (on 76 now) I have had problems
| launching gVim & vim with parameters and basically any part of Vim
| which calls out to the system.

Is the new build of TCC in the same directory as the previous one? Are you
using the same installation of gVim and vim as before the TCC upgrade?
Reinstalling or upgrading may change the paths where VIM and TCC expect to
find each other.

| If I attempt to Launch Vim with a filename or execute a plugin which
| sends commands out to the shell, causes the following problem:
|
| a) A new TCC LE command window opens outside of TCC LE

I assume this did not happen previously, or you would not have mentioned it.
Have any of the configuration files used by VIM changed? Is VIM running in
the same console window as TCC? A new TCC window usually means that TCC was
not started directly by VIM, but by Windows, possibly through a file
association.

| b) The following message appears in red "TCC: Unknown command
| "files\JPSoft\TCMDLE10\TCC.EXE"
|
| c) Vim will 'hang' until the command window is closed.
|
| I have noticed that the path is truncated and is the cause of the
| problem .
|
| My question is: Why is this happening?

It is best policy to install all console programs in "plain path"
directories, regardless of installer defaults driven by Microsoft's insane
Vista certification criteria. Many programs fail to surround path names
containing spaces or other special characters by quotation marks ("), esp.
when starting another program. My guess is that you installed TCMDLE 10.0.76
in "C:\Program files\JPSoft\TCMDLE10\", that VIM successfully starts a 2nd
TCC instance, and passes it a command which should start a 3rd TCC instance
to do the actual work, which command contains the full unquoted path of
TCC.EXE for that purpose. The 2nd instance TCC parser makes makes hash out
of the incorrect command it receives.

BTW, you did not mention how VIM is started - is it running in a TCMDLE tab?

There are more questions here than answers, but hopefully they will point
you in the right direction.
--
HTH, Steve
 
May 20, 2008
3,515
4
Elkridge, MD, USA
Charles Dye wrote:
| Amen. But if you have installed in a path containing a space, you
| can often work around problems by adding a line
| set comspec=%@sfn[%comspec]
| to your TCSTART.BTM file.

Never having installed JPsoft products in default locations, I never thought
of this possibility. Maybe it should be done automatically by TCC.EXE?
Looking at the output of FTYPE, and also using the SHORTCUT command to
examine .lnk files, I see that many products use the SFN!
--
Steve
 
Similar threads
Thread starter Title Forum Replies Date
D Folders pane display problem when starting Support 4
fishman@panix.com Problem with 27.15 Support 2
M Problem with VSDevCmd.bat in VS 16.7.3 Support 0
R Problem with @INT[ value] in V26 Support 9
M Selecting test "off by one" problem in Take command Support 4
Alpengreis UTF-8 problem in TCC related to Python Support 7
K_Meinhard Small problem in german IDE 26 Support 3
B Problem with color in nested shells Support 1
Joe Caverly Problem creating and switching to a DESKTOP Support 9
vefatica Another popup problem Support 10
Alpengreis ffind dialog (/W) problem Support 4
Alpengreis [TCMD v25.00.24] Small space problem with the DE translation in Prefs-GUI Support 1
Alpengreis [TCMD v25.00.24] Problem with copy and paste and the # char via mouse in TCC Support 6
A Problem with functions @int @decimal and identifying Powershell as a shell. Support 12
B IF command problem in tcexit.btm Support 9
fishman@panix.com Problem at Startup of TCC Support 3
P Problem with SFTP copies Support 7
P Problem with FTP copies Support 10
Jay Sage Problem with Context Menu Copy+Paste+Run Key Assignment Support 7
R Problem with %_do_loop in nested do loops Support 2
fishman@panix.com New Problem with later Windows 10 Support 10
Peter Murschall A little problem with LEAVE and COMMENT Support 5
M Handling of %~I problem Support 4
WinLanEm FOR problem Support 18
K Problem With SCRPUT /u Support 3
vefatica What's TCMD's problem with ^e[0m? Support 13
Peter Murschall IDE: RTL with non-English resources-problem is back in Build 28 Support 4
rps Regex problem: \xnn not recognized as a hex character Support 0
rps PRIORITY LOW problem Support 1
old coot Regex problem: \xnn not recognized as a hex character Support 12
vefatica Another problem with build 22. Support 3
Alpengreis [23.x] Download-Problem Support 2
S Problem with " Support 3
C Problem navigating forums Support 11
x13 Problem listing repository files using DIR http(s)://... Support 8
Joe Caverly Problem with TEE in v22 Support 2
Alpengreis Problem with thousands delimiter and colors Support 17
M Take Command 18, migrating to another machine, license problem. Support 1
B TCC 21.01.50 Problem with ALIAS /r and SET /r Support 2
rps How to? @search problem Support 2
WinLanEm @SELECT problem Support 6
T Fixed Problem with use of Batch parameters in the IDE Support 1
Oz Solomon Problem with "list" Support 14
S V21.24 theme problem Support 2
Alpengreis Problem if command prompt is not legacy Support 4
Alpengreis TCMD.INI: The "super hidden" problem ... Support 6
G Odd problem - screen brightness Support 4
rps V20 In-process pipes problem Support 8
Alpengreis Again theme problem [v20.0.21]? Support 11
WinLanEm INPUT problem Support 1

Similar threads