Topic: Possible and harmless typo in COMPILE.CNF (1 of 14), Read 44 times
Conf: Compiler support
From: Peter Rejto
Date: Wednesday, May 14, 2008 11:46 AM

At the beginning of the file COMPILE.CNF the instructions are:

SUPPORTPATH=C:\VEDIT\COMPILE
// Use VEDIT-Home-Directory\COMPILE if none specified
// E.g the default is "C:\VEDIT\COMPILE"

Later, in the Additional Documentation section it says that

"It only needs to be set when these files are not in "VEDIT-Home-Directory\COMPILE", e.g.
if you moved them to "C:\TOOLS\VEDIT\COMPILE". "

To run my TeX compiler I did need to set the Vedit-Home-Directory path.

Finally a wish:

I would like to use the Configuration String HOME
in this file. I tried

SUPPORTPATH=HOME\COMPILE

However, this did not work for me.


Thanks,

-peter.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (2 of 14), Read 39 times
Conf: Compiler support
From: Fritz Heberlein
Date: Wednesday, May 14, 2008 12:00 PM

>
> SUPPORTPATH=HOME\COMPILE
>

What about "|(HOME)" ?

Fritz

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (4 of 14), Read 38 times
Conf: Compiler support
From: Peter Rejto
Date: Wednesday, May 14, 2008 04:27 PM

On 5/14/2008 12:00:21 PM, Fritz Heberlein wrote:
>>
>> SUPPORTPATH=HOME\COMPILE
>>
>
>What about "|(HOME)" ?
>
>Fritz
>


Thanks Fritz,

You suggestion works like a charm. I do hope
that Ted reads this message so he need not look at
COMPILE.CNF again.


Incidentally, I tried |HOME|\COMPILE and that did not work either.

Thanks again,

-peter.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (3 of 14), Read 40 times
Conf: Compiler support
From: Ted Green
Date: Wednesday, May 14, 2008 12:13 PM

At 11:47 AM 5/14/2008, you wrote:
>From: "Peter Rejto"
>
>At the beginning of the file COMPILE.CNF the instructions are:
>
>SUPPORTPATH=C:\VEDIT\COMPILE
> // Use VEDIT-Home-Directory\COMPILE if none specified
> // E.g the default is "C:\VEDIT\COMPILE"
>
>Later, in the Additional Documentation section it says that
>
>"It only needs to be set when these files are not in "VEDIT-Home-Directory\COMPILE", e.g.
>if you moved them to "C:\TOOLS\VEDIT\COMPILE". "

OK, I changed that to "c:\tools\compile" to hopefully reduce confusion. I suspect that very few people ever change this, and if they do, set it to the correct directory.

>Finally a wish:
>
>I would like to use the Configuration String HOME
>in this file. I tried
>
>SUPPORTPATH=HOME\COMPILE

I will try to make "|(HOME)\COMPILE" work (assuming it doesn't already).

Ted.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (5 of 14), Read 38 times
Conf: Compiler support
From: Peter Rejto
Date: Wednesday, May 14, 2008 04:32 PM


>I will try to make
>"|(HOME)\COMPILE" work
>(assuming it doesn't already).
>
>Ted.
>

Thanks Ted,

Actually,

"|(HOME)\COMPILE"

does work. Sorry for not thinking about it myself.

-peter.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (6 of 14), Read 36 times
Conf: Compiler support
From: Ted Green
Date: Wednesday, May 14, 2008 05:19 PM

At 04:33 PM 5/14/2008, you wrote:
>Actually,
>
>"|(HOME)\COMPILE"
>
>does work. Sorry for not thinking about it myself.

OK. Perhaps I should change that to be the default.

Ted.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (7 of 14), Read 36 times
Conf: Compiler support
From: Peter Rejto
Date: Wednesday, May 14, 2008 05:36 PM

On 5/14/2008 5:19:00 PM, Ted Green wrote:
>At 04:33 PM 5/14/2008, you
>wrote:
>>Actually,
>>
>>"|(HOME)\COMPILE"
>>
>>does work. Sorry for not thinking about it myself.
>
>OK. Perhaps I should change
>that to be the default.
>
>Ted.
>

Thanks Ted for your generous offer.

Most likely, I am the only Vedit user who would benefit from this.

Now let me give you a self-survey concerning my benefits:

1.: I could use COMPILE.CNF as a tutorial on the Vedit Configuration Strings.

2.: I do have two hard drives and sometimes I do boot from my second hard drive. I have installed Vedit on each of them. This way I can use the same COMPILE.CNF file for each my Vedit installations.

I already have learned quite a bit from your suggestions.

Thanks again,

-peter.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (8 of 14), Read 41 times
Conf: Compiler support
From: Pauli Lindgren
Date: Thursday, May 15, 2008 11:45 AM

On 5/14/2008 5:19:00 PM, Ted Green wrote:
>>Actually,
>>
>>"|(HOME)\COMPILE"
>>
>>does work. Sorry for not thinking about it myself.
>
>OK. Perhaps I should change
>that to be the default.

But isn't it already the default?
It is set at line 301 in c-init.vdm.

So, if the compiler support files are located in "compile" subdirectory of Vedit home directory, you do not need to set anything in SUPPORTPATH.

-

However, what I would like to see is the ability to use more than one compiler. In DOS version, you could have compiler configuration file in "current directory". But that does not work in Windows.
This is another place where "project directory" would be needed. Then you could use different compiler for each project.

--
Pauli

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (9 of 14), Read 36 times
Conf: Compiler support
From: Peter Rejto
Date: Friday, May 16, 2008 01:36 AM

On 5/15/2008 11:45:26 AM, Pauli Lindgren wrote:
>On 5/14/2008 5:19:00 PM, Ted Green
>wrote:
>>>Actually,
>>>
>>>"|(HOME)\COMPILE"
>>>
>>>does work. Sorry for not thinking about it myself.
>>
>>OK. Perhaps I should change
>>that to be the default.
>
>But isn't it already the default?
>It is set at line 301 in c-init.vdm.
>
>So, if the compiler support files are
>located in "compile" subdirectory of
>Vedit home directory, you do not need to
>set anything in SUPPORTPATH.

Thanks Pauli,

I did go back to my COMPILE.CNF file and did some more experiments. This is that I came up with:

SUPPORTPATH //OK
SUPPORTPATH= // Not OK!
SUPPORTPATH=|(HOME)\COMPILE //OK

So, my personal preference is :

SUPPORTPATH=|(HOME)\COMPILE

This way I have the option of using another directory for the compiler, as per the instructions.

A big thank you for pointing out the C-INIT.VDM reference.
If you can find the line number where my "File Not Found" error message came from, I would appreciate it. But please do not loose any sleep over this.

Thanks again for everything.

-peter.

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (10 of 14), Read 25 times
Conf: Compiler support
From: Pauli Lindgren
Date: Friday, May 16, 2008 11:18 AM

On 5/16/2008 1:36:35 AM, Peter Rejto wrote:
>
>SUPPORTPATH //OK
>SUPPORTPATH= // Not OK!
>SUPPORTPATH=|(HOME)\COMPILE //OK

Do you have a whitespace after '=' in the middle case?
If not, C-INIT.VDM tries to read the pathname. If '=' is not followed by the pathname but for example a comment, that would not work of course.
But if there is space after "SUPPORTPATH=", then the macro goes to else part and sets the default to |(HOME)\COMPILE.

Maybe that part of C-INIT.VDM would need some refining, for example to check for comment.
Also, it looks like it can not handle pathnames that contain spaces.

--
Pauli

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (12 of 14), Read 27 times, 1 File Attachment
Conf: Compiler support
From: Christian Ziemski
Date: Monday, May 19, 2008 05:02 PM

On 5/16/2008 11:18:55 AM, Pauli Lindgren wrote:
>
>Maybe that part of C-INIT.VDM would need
>some refining, for example to check for
>comment.
>Also, it looks like it can not handle
>pathnames that contain spaces.

Today I modified C-INIT.VDM a bit to be more flexible regarding this. Comments, pathes with spaces with or without double quotes should be handled now.

My current version of that file is attached.
(It contains some more changes from 2006 (see discussion about syntax highlighting two threads above).)

Due to time limitations I wasn't able to test todays changes in the complete compile environment yet - I simply haven't used that for two years now.


Christian

 
C-INIT(6).VDM (27KB)

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (13 of 14), Read 18 times
Conf: Compiler support
From: Pauli Lindgren
Date: Tuesday, May 20, 2008 11:03 AM

On 5/19/2008 5:02:05 PM, Christian Ziemski wrote:
>
>Today I modified C-INIT.VDM a bit to be
>more flexible regarding this. Comments,
>pathes with spaces with or without
>double quotes should be handled now.

I tested a bit your C-INIT.VDM.
I don't have working compiler environment for Vedit either, so I just used the default Visual C. It only gives one error message since it can not find include files, so the test was not very comprehensive.

Anyway, I wrote about some findings in the other thread.

But there is another problem with compiler support that I noticed just some time ago when trying to use it.
It seems that the length of path causes problem here also.
Our projects use quite deep directory structure, so the pathname easily becomes too long and the compiler can not be run at all.

Looks like this is because the file vcs-tmp.bat is stored in the project directory.
If it would be stored for example in vedit\compile directory, the length of pathname would not be a problem.

--
Pauli

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (14 of 14), Read 19 times
Conf: Compiler support
From: Christian Ziemski
Date: Wednesday, May 21, 2008 08:56 AM

On 5/20/2008 11:03:49 AM, Pauli Lindgren wrote:
>
>But there is another problem with
>compiler support that I noticed just
>some time ago when trying to use it.
>It seems that the length of path causes
>problem here also.
>Our projects use quite deep directory
>structure, so the pathname easily
>becomes too long and the compiler can
>not be run at all.

Should be fixed now.
See thread "compiler support and syntax highlighting".

Christian

 


Topic: Re: Possible and harmless typo in COMPILE.CNF (11 of 14), Read 27 times
Conf: Compiler support
From: Ted Green
Date: Monday, May 19, 2008 12:27 PM

At 11:45 AM 5/15/2008, you wrote:
>From: "Pauli Lindgren"
>
>On 5/14/2008 5:19:00 PM, Ted Green wrote:
>>>Actually,
>>>
>>>"|(HOME)\COMPILE"
>>>
>>>does work. Sorry for not thinking about it myself.
>>
>>OK. Perhaps I should change
>>that to be the default.
>
>But isn't it already the default?
>It is set at line 301 in c-init.vdm.

You are correct.

>However, what I would like to see is the ability to use more than one compiler. In DOS version, you could have compiler configuration file in "current directory". But that does not work in Windows.
>This is another place where "project directory" would be needed. Then you could use different compiler for each project.

Yes, a separate compile.cnf file for each project would solve this. I will implement a Project directory ASAP and review your previous comments on this, or you can email them to me again.

Ted.