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
|
|