Page 1 of 1

Replacing the DOS Shell

Posted: Tue Jan 08, 2008 11:02 am
by alin.elena
Hi,


I have got zeus 3.96m (trial) and I wanted to replace the DOS shell. (cmd.exe whith powershell (the new msh)).
http://www.microsoft.com/technet/script ... load2.mspx

I used COMSPEC variable to set it.
As OS I use vista enterprise

Now the problems
1. Tools->DOS Shell dies immediately after lunch
I have digged and the problem is the /k option. necessary for dos but not for msh.

2. xtags
with powershell as shell xtags will not run.
The error is "Unexpected Error Spawning xTags Executable"
I have checked and xtags is in the path.
I have suspected something wrong with the installation and I have tested xtags by hand
If I run the command in powershell
PS C:\Users\Alin M Elena\testZeus> xtags --c-types=+fp --excmd=p --fields=+afmikKlnsSz --sort=no -f test.f90.tag test.f90
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Unknown option: --

are there any other variables to set other than PATH? LIB etc?

3. Should I be worried that xtags uses --c-types on a fortran file?

Alin

Posted: Tue Jan 08, 2008 10:48 pm
by jussij
Hi Alin,
1. Tools->DOS Shell dies immediately after lunch I have digged and the problem is the /k option. necessary for dos but not for msh.
I will fix this so the /k option is only used for the cmd.exe command processor ;)
2. xtags with powershell as shell xtags will not run.
The xtags.exe is running being run via the cmd.exe command processor and this might be why it is not running :(

But it should be possible to change Zeus to run the xtags.exe directly which might fix the problem :?
Are there any other variables to set other than PATH? LIB etc?
I don't think you even need to set these. Zeus will find always find xtags.exe since it looks in the Zeus install directory ;)
If I run the command in powershell
PS C:\Users\Alin M Elena\testZeus>xtags --c-types=+fp --excmd=p --fields=+afmikKlnsSz --sort=no -f test.f90.tag test.f90
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Warning: invalid character range
xtags.exe: Unknown option: --
What the test.f90.tag tags file create :?:

I'm not sure why these invalid character range and unknown option messages are getting generated since these are just ctags command line options, for example:

Code: Select all

C:\Users\Alin M Elena\testZeus>xtags -?
In the Zeus install directory there is an xtags.ini file. You can edit this file to change the xtags.exe command line ;)
3. Should I be worried that xtags uses --c-types on a fortran file?
Probably not. This option is described by ctags as follows:
--<LANG>-kinds=[+|-]kinds
Enable/disable tag kinds for language <LANG>.
So it will only ever be triggered for C files.

Cheers Jussi

Posted: Wed Jan 09, 2008 2:40 pm
by alin.elena
Hi Jussi,

What the test.f90.tag tags file create
No

if i run

Code: Select all

xtags  -N -u -f test.f90.tag test.f90
the file gets created
it seems that it does not like --options

I have checked and the warning appears in cmd.exe, too but not the error.

Alin

Posted: Wed Jan 09, 2008 4:27 pm
by alin.elena
Hi Jussi,

it seems that the parameters get passed in a strange way to the program in msh

Code: Select all

./ctags --c-types=+fp --excmd=p --fields=+afmikKlnsSz --sort=no -f test.f90.tag test.f90

arg 0 C:\Users\Alin M Elena\ctags\ctags.exe
arg 1 c-types=+fp
arg 2 --
arg 3 excmd=p
arg 4 --
arg 5 fields=+afmikKlnsSz
arg 6 --
arg 7 sort=no
arg 8 -f
arg 9 test.f90.tag
arg 10 test.f90
the solution to the problem is to quote each parameter.
so xtags.ini becomes

Code: Select all

[xTags]
Arguments=\"--c-types=+fp\" \"--excmd=p\" \"--fields=+afmikKlnsSz\" \"--sort=no\"
from

Code: Select all

[xTags]
Arguments=--c-types=+fp --excmd=p --fields=+afmikKlnsSz --sort=no
Alin

Posted: Wed Jan 09, 2008 10:32 pm
by jussij
I have tracked down this warning message:
xtags.exe: Warning: invalid character range

It is generated by ctags.exe itself and is caused by a bad regular expression in the PHP parser.

Cheers Jussi