SynWrite (Syn2)

[Alextp]

64Bit version is 3.X. No later updates. http://www.totalcmd.net/plugring/SynWrite_x64.html

@Petermad, do u know Python?

[petermad]

Ahh - I installed it using TotalUpdater, and didn't notice that it was the 32-bit only version that I got.

After installing separate 64-bit version I have no crash anymore

[MarianD]

It is nice that Visual Basic lexer finish each unfinished “If” statement with “End if” after pressing Enter (new line), but the part “if” of “End if” is considered as the begin of the new “If” block, so it constanly writes “End if” after each Enter. A pity, because this behavior makes it useless.

[Alextp]

I dont see that VB or VBS finishes If. I see VBS has property "Auto closing txt" OFF for "If". So If not closes.

[Alextp]

Btw; I unsubscribe here, so pls use forum...

[MarianD]

Thanks for your answer – but where is that forum? I followed the link in your SynWrite at TotalCmd.net, and it brought me here.

In VBS lexer there is not a mentioned problem, but in VB lexer is. (I used VB lexer from your SynWrite_Addons.rar (2015.03.06) with the default settings.)

I tried to find the property "Auto closing txt" OFF for "If" both in VB and VBA lexers – in VBA it is OK but in VB there is no “Begin if” in the upper left list of the “Rules” tab.

Try copy this code:

Code: Select all

    Do While (Not rs.EOF)
        If f1.Value <> f2.Value Then
            Debug.Print (rs!Number & ": " & f2.Value & "->" & f1.Value)
        End If

        f2.Value = f1.Value
        rs.Update
        rs.MoveNext
    Loop

and press Enter after the last but one line (in VB lexer).

[fenix_productions]

2Alextp
Is it possible to define file types for extensions to use?

My problem is: too many elements in Plugins menu.
It would be better to have such menu limited for some file types, i.e.
I don't need to see all HTML related plugins if I work with simple text file.

[tosbsas]

I need 64bit version - 32 crashes here

[thomasmo]

I need 64bit version - 32 crashes here

yeah! itis a good wlx plugins, please comblined a x64 version!!

[sqa_wizard]

There is a 64-Bit version

[iana]

There is a 64-Bit version

that version is ancient, abandoned has bugs and missing a lot of features

@author I wanted to ask can CudaText be implemented as a wlx plugin, also can it be compiled in native x64 mode

[AntonyD]

for further discussions please use another forum as developer asked.
http://synwrite.sourceforge.net/forums/

btw developer now is rapidly creating a new text editor.
is should be a "replacement" for SynWrite tool.

http://wiki.freepascal.org/CudaText#About

The plan is to continue Cuda. very limited support for Synw. Cuda support will be ok. i hope. I spend time on Cuda. not Synw.

[TychoBarfy]

Code: Select all

Access violation at address 000000001ECA9FA5
in module 'Syn2.wlx64'. Read of address 0000000000000001

or

Access violation at address 000000001EEF2B60 in
module 'Syn2.wlx64'. Read of address 0000000000000001

If TC shows something like this viewing a particular file with SynWrite, just open the settings of currently used Lexer, go to tab Styles and look for one of these styles using "Custom font". Change this to "Font style & colors" or what ever, apply and exit with OK to save your Lexer library! The access violation will never appear any more.

[Horst.Epp]

Years ago, Syn2 was my favorite viewer and editor in TC.
Last Version for me is 6.15.0
Never had major problems with it, but it's only x32, so I stopped using the viewer part.
I still use the editor for certain jobs.

Today, there are other source code viewer and editor plugins.
For example:
TC Akelpad
CodeViewer
CudaLister

[TychoBarfy]

Years ago, Syn2 ...

Hi Horst! I deactivated TC Akelpad 3 days ago. I have CodeViewer in Listerprugin.ini (or TC Section respectively) with n_detect=SIZE<10000000 and CudaLister without any _detect string.

I loved Synplus but this is a really 32-bit one. So I went to SynWrite (at first I disabed edit mode in SynWrite's settings because I use Notepad++ as editor) and it's OK for me. Was updating Lexers 2 nights ago on Alexey-T's CudaText Lexers site on Github (thumbs up for it's work and there are many Lexers newer than 2021).

Created a new bigger LexLib.LXL and struggled over this access violations.

My syn2.wlx64 and Syn64.exe both have version 1.0.0.0 and are from 2012. But it works fine with empty n_detect= string at proper position of my INI (until yesterday I used n_detect=([0]!="M"|[1]!="Z")).