Topic: Enhanced LATEX.VCS for filenames with spaces (1 of 6), Read 22 times, 2 File Attachments
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Sunday, June 19, 2011 03:28 PM

Hi,

I did succeed in enhancing LATEX.VCS to handle project files with spaces in their names.

Actually, this was a simple exercise after Christian made such enhancements to C-INIT.VDM and C-COMPILE.VDM members of this family. In fact, all that I did, was to enhance the Search() command in the EMERGENCY STOP part of LATEX.VCS.

Here are the details:

replace
search("|40|a:/|*.tex",reverse)
by
Search("{|40|a:/|*.tex",reverse,|40|a:/"|*.tex",reverse)})


In other words, I did replace a single search string by a set of two search strings. The new string added a double quote to the old string as per the Vedit on line Help File for long file names.

So, a big thank you to Christian for making this enhancement to the C-INIT.VDM and C-COMPILE.VDM macros.


I do hope that Fritz will have a chance to test my macro.

To avoid confusion with the original LATEX.VCS I called mine, MIKTEX.VCS I plan to upload right now. Actually, YAP.VDM also needed a small adjustment and I am uploading that too.

-peter

 
LATEX.VCS for long filenames
  YAP.VDM for long filenames

 


Topic: Enhanced LATEX.VCS for filenames with spaces (2 of 6), Read 14 times, 1 File Attachment
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Monday, June 20, 2011 12:24 AM

Hi,

I have found a typo in my previous file, MIKTEX.VDM.
I am uploading the new one:

Here is the corrected statement:

All that I did was to
replace
search("|40|a:/|*.tex",reverse) // look backward for
by
Search(`|{|40|a:/|*.tex",|40"|a:/|*.tex"}`,reverse) // look backward for

In other words, the new pattern set consists of the original string and a double quote adjusted version of the original string.
Each of these two strings is a "signature" of Miktex, like (C:/......tex"




-peter

 
LATEX.VCS for long filenames

 


Topic: Enhanced LATEX.VCS for filenames with spaces (3 of 6), Read 12 times
Conf: VEDIT Macro Library
From: Pauli Lindgren
Date: Monday, June 20, 2011 08:50 AM

On 6/20/2011 12:24:00 AM, peter rejto wrote:
>
> Here is the corrected statement:
>
> All that I did was to
> replace
> search("|40|a:/|*.tex",reverse) // look backward for
> by
> Search(`|{|40|a:/|*.tex",|40"|a:/|*.tex"}`,reverse) // look
> backward for
>
> In other words, the new
> pattern set consists of the
> original string and a double
> quote adjusted version of the
> original string.

I think the double quote at the end of the first string option (pathname without double quotes) should not be there.

Shouldn't you do the same change in WARNINGS section, too?

Maybe you could use single quotes as main delimiters instead of ` so that the syntax highlight would work correctly?

--
Pauli

 


Topic: Enhanced LATEX.VCS for filenames with spaces (4 of 6), Read 13 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Monday, June 20, 2011 09:20 PM

On 6/20/2011 8:50:21 AM, Pauli Lindgren wrote:
>On 6/20/2011 12:24:00 AM, peter rejto
>wrote:
>>
>> Here is the corrected statement:
>>
>> All that I did was to
>> replace
>> search("|40|a:/|*.tex",reverse) // look backward for
>> by
>> Search(`|{|40|a:/|*.tex",|40"|a:/|*.tex"}`,reverse) // look
>> backward for
>>
>> In other words, the new
>> pattern set consists of the
>> original string and a double
>> quote adjusted version of the
>> original string.
>

>Shouldn't you do the same change in
>WARNINGS section, too?
>
>Maybe you could use single quotes as
>main delimiters instead of ` so that the
>syntax highlight would work correctly?
>
>--
>Pauli


Pauli,

Thanks for your suggestion of:

>
>Maybe you could use single quotes as
>main delimiters instead of ` so that the
>syntax highlight would work correctly?


Syntax highlighting is above my head.
In fact, I would appreciate your explaining how this feeds into syntax highlighting.


>
>Shouldn't you do the same change in
>WARNINGS section, too?
>

Yes, of course. I was just to busy to make sure that the MIKTEX.VCS does not shut down, when in fact the Miktex compiler did work. This is that I have been testing for.


>I think the double quote at the end of
>the first string option (pathname
>without double quotes) should not be
>there.
>

I have been wondering about this too. But it seems to me that the 'Miktex Signature" does have a double quite, whether or not the project file is long or short.
So, I have a hunch that it is OK. Furthermore, I did some fair amount of testing for shut downs. It seemed to work.

I have a hunch that you did similar editing for the C Compliler support file, .VCS I would appreciate your uploading it, so I could use it as a model.

Even better, I would appreciate Ted's including these files in the Vedit 6.20.2 distribution. I noticed that the C-INT.VDM and C-COMPILE.VDM files were not updated. The same for the OPENCUR.VDM.

Thanks again,

-peter


Thanks again,

-peter

 


Topic: Enhanced LATEX.VCS for filenames with spaces (5 of 6), Read 19 times
Conf: VEDIT Macro Library
From: Pauli Lindgren
Date: Tuesday, June 21, 2011 04:51 AM

On 6/20/2011 9:20:25 PM, peter rejto wrote:
>Syntax highlighting is above my head.
>In fact, I would appreciate your
>explaining how this feeds into syntax
>highlighting.

Syntax highlighting displays strings in specific color. A string is any text that is between string delimiters. Vedit.syn specifies single quote and double quote as string delimiters, so only those are identified as strings. If you use some other string delimiters in the search command, the syntax highlighting may get confused, especially if there are single or double quotes inside the string.

>
>I have been wondering about this too.
>But it seems to me that the 'Miktex
>Signature" does have a double quite,
>whether or not the project file is long
>or short.
>So, I have a hunch that it is OK.
>Furthermore, I did some fair amount of
>testing for shut downs. It seemed to
>work.

The original search command (before your change) did not have a double quote at the end of search string.

If the pathname always has double quotes, then you would not need the no-double-quotes option at all.

--
Pauli

 


Topic: Enhanced LATEX.VCS for filenames with spaces (6 of 6), Read 13 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Tuesday, June 21, 2011 11:17 AM

On 6/21/2011 4:51:12 AM, Pauli Lindgren wrote:
>On 6/20/2011 9:20:25 PM, peter rejto
>wrote:
>>Syntax highlighting is above my head.
>>In fact, I would appreciate your
>>explaining how this feeds into syntax
>>highlighting.
>
>Syntax highlighting displays strings in
>specific color. A string is any text
>that is between string delimiters.
>Vedit.syn specifies single quote and
>double quote as string delimiters, so
>only those are identified as strings. If
>you use some other string delimiters in
>the search command, the syntax
>highlighting may get confused,
>especially if there are single or double
>quotes inside the string.
>
>>
>>I have been wondering about this too.
>>But it seems to me that the 'Miktex
>>Signature" does have a double quote,
>>whether or not the project file is long
>>or short.
>>So, I have a hunch that it is OK.
>>Furthermore, I did some fair amount of
>>testing for shut downs. It seemed to
>>work.
>
>The original search command (before your
>change) did not have a double quote at
>the end of search string.
>
>If the pathname always has double
>quotes, then you would not need the
>no-double-quotes option at all.
>--
Thanks Pauli,

Here I stand corrected. (Also, I double checked the Miktex signature. After all, it does not have a double quote at the end of the file name.

So, I changed my MIKTEX.VCS file as per your suggestion. Here it is:

You did not come back to my question about a generic .VCS file. You must have changed your .VCS file for your compiler. Or may be Christian did it when he updated C-INIT.VDM, C-COMPILE.VDM and friends ?

Thanks again,

-peter


-peter