CudaText VS other editors: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		# CudaText advantages over Sublime Text 3
2	2
3	3		- Open source, more operating systems are supported
4	4		- The Python API is easier to use
5	5		- The Python API allows management of dialogs and UI-controls, including the CudaText editor control
6	6		- Code-Tree for most of lexers (ST has only plugin for very limited set of languages)
7	7		- Powerful EControl lexer format, and it's easier to create/edit lexers (GUI in external program)
8	8		- Floating (separate window) mode of side panel and bottom panel
9	9		- Floating (separate window) groups of UI-tabs (in addition to normal 6 groups)
10	10		- [[CudaText\|Toolbar]], configurable via plugin
11	11		- [[CudaText\|Configurable statusbar]]
12	12		- Horizontal ruler above text
13	13		- [[CudaText\|Micromap]]
14	14		- [[CudaText\|Markers]] in editor
15	15		- [[CudaText\|Sessions system]]
16	16		- Caret position after end-of-line
17	17		- Better support for encodings, including UTF-32
18	18		- Better support national keyboards on Linux
19	19		- Correctly saves binary files
20	20		- API for inter-line gaps, helping to several plugins (Differ, Insert Pics, Embedded Editor)
21	21		- [[CudaText\|Viewer]] for files of unlimited size
22	22		- [[CudaText\|Hex display of special chars]]
23	23		- [[CudaText\|UI-tabs features]]: colored tabs, icons (Tab Icons plugin), tabs on the left/right
24	24		- Plugin "Options Editor" to configure CudaText via simple GUI
25	25		- [[CudaText\|Character Map dialog]]
26	26		- UI can be scaled by option (up to 500%)
27	27		- Single-instance mode is supported on all OS'es
28	28		- Scrolling after middle-button click (called "Autoscrolling" in Firefox)
29	29		- [[CudaText plugins\|Show pictures in the text]]
30	30		- [[CudaText plugins\|Colorize the text]]
31	31		- [[CudaText\|Activating internet links]]
32	32		- [[CudaText\|Automatic folding of comments]]
33	33		- [[CudaText\|HTML auto-completion suggests file/folder names]]
34	34		- [[CudaText\|File URI file:/// auto-completion]]
35	35		- [[CudaText\|HTML color codes underlining]]
36	36		- [[CudaText plugins\|Macros plugin]] also records actions performed in the Find/Replace dialog, and mouse clicks
37	37		- CudaText and its plugins support i18n (text strings can be translated)
38	38		- Function "Find in files" is [[CudaText plugins\|implemented in plugin]], with much more features
39	39		- [[CudaText\|Tab switcher]] dialog
40	40		- Can split single UI-tab, for single file or 2 different files (helps to work with Differ plugin)
41	41		- Color themes do not have per-lexer settings
42	42		- [[CudaText\|Picture file viewer]] supports zooming of a picture
43	43		- [[CudaText\|Dialog "Go to"]] gives more features
44	44		- Option "tab_smart" for smart-tabs, known from several other text editors
45	45		- Option "caret_proximity_vert" to set minimal distance of caret to top/bottom edge
46	46		- Option for "zebra" mode
47	47		- Windows version can use different Python engine (packages in add-ons)
48	48		- Add-ons do not disappear due to GitHub repository deletions
49	49		- Find/Replace dialog:
50	50		- Dialog has "Allowed syntax elements" option
51	51		- Dialog has "Find first" button (ST: only "Find" which means "Find next")
52	52		- Dialog has "Immediate search" option (ST: search is always immediate)
53	53
54	54		# CudaText advantages over Visual Studio Code
55	55
56	56		- VSCode has the option "maximal count of ui-tabs", because its ui-tabs are memory hungry. CudaText allows to open 1000+ ui-tabs without problems.
57	57		- VSCode is slow for file sizes 10M...100M, while CudaText allows this without problems. For size 2M+ CudaText disables lexers, but "lite lexers" (Log, XML, JSON) work always.
58	58		- VSCode doesn't have customizable toolbar.
59	59		- VSCode doesn't allow to show side-panels in floating (detached) window.
60	60		- VSCode has internal "find in files" but CudaText has FindInFiles-4 plugin with much more features.
61	61		- VSCode cannot show inter-line gaps with pictures. CudaText plugin "Insert Pics" is based on this feature.
62	62		- VSCode doesn't have the analog of CudaText "Color Text" plugin (not 100% sure here).
63	63		- VSCode doesn't have the analog of CudaText "Draw Lines" plugin.
64	64		- VSCode cannot place text caret beyond end-of-line (not 100% sure here).
65	65		- VSCode has the add-on "Macros", with it you need to create/configure command sequences by hands. Not simple task. CudaText has the plugin "Macros" and it records usual keypresses. Much eaiser to do.
66	66		- CudaText gives [[CudaText\|viewer for files of unlimited size]].
67	67		- CudaText plugins API is simpler.
68	68		- CudaText supports UTF-32 LE/BE encoding.
69	69
70	70		# CudaText disadvantages compared to Sublime Text / VSCode
71	71
72	72		- CudaText doesn't use 3D acceleration on rendering, so it may lag (and/or consume lot of CPU) if you scroll text, with big window size (not on Windows, Windows API works fast enough).
73	73		- CudaText doesn't provide "Go to anything" command, instead it gives several separate commands:
74	74		- Go to line number,
75	75		- Go to project file,
76	76		- Go to bookmark,
77	77		- Go to code-tree symbol, ...
78	78		- CudaText lexers are "simple": they don't parse text as deeply as ST/VSCode; so you need the LSP plugin if you need IntelliSense features.
79	79		- CudaText key bindings are simpler: commands don't have "arguments" and cannot be set per-project (but can be set per-lexer).
80	80		- CudaText plugins API doesn't support async events.
81	81		- CudaText doesn't support some encodings (e.g. Shift-JIS).
82	82
83	83		# CudaText performance
84	84
85	85		## Startup time
86	86
87	87		CudaText starts quite fast: about 0.3 sec with about 30 plugins (all preinstalled + some popular plugins), on Linux, on CPU x64 Intel Core i3 3GHz.
88	88
89	89		- If no additional plugins are installed, or Python engine is disabled (ie not configured on Unix, or Python DLL files are deleted on Windows), then it starts even faster.
90	90		- If configuration/history are clean, it starts faster.
91	91		- If bottom panel is hidden on start, via option "ui_bottom_on_start":2, it starts faster.
92	92
93	93		## Performance of loading huge files
94	94
95	95		How fast Linux editors open huge files?
96	96
97	97		Test file has about 300M size, it has 4M ASCII lines, it's created by Python script:
98	98
99	99		``` python
100	100		f = open("a.log", "w")
101	101		for n in range(410001000):
102	102		k = 120-n%100
103	103		f.write(str(n+1)+' '+chr(k%26+ord('a'))*k+'\n')
104	104		```
105	105
106	106		Testing on Ubuntu 20.04, CPU: Intel Core i3 3GHz, RAM: 12G. Each time is average of 2-3 tries in the same session.
107	107
108	108		- CudaText 1.211.0: 8 sec
109	109		- Sublime Text 4 4169: 8 sec
110	110		- Geany 1.36: hangs, waited for it 90 sec
111	111		- Kate 23.08.4: 5 sec, then go to end (Ctrl+End hotkey) took additional 30 sec
112	112		- Vim 8.1.1847: 2 sec
113	113		- Emacs GUI 29.2: 2 sec, after showing confirmation for big file
114	114		- gedit 3.36.2: 19 sec, then go to end (Ctrl+End hotkey) hangs: waited for it 100 sec
115	115
116	116		## Performance of editing huge lines
117	117
118	118		Tested several editors on Ubuntu 20.04 on Intel Core i3 CPU.
119	119
120	120		XML file: single line of length 4M. XML file contains line like \<id name="nnnnnnn"\> with the huge "name" value of 4M. Python script to generate XML file:
121	121
122	122		``` python
123	123		#!/usr/bin/python3
124	124		f = open("a.xml", "w")
125	125		f.write('<id name="')
126	126		for n in range(1, 4096):
127	127		f.write("n" * 1024)
128	128		f.write('">\n')
129	129		```
130	130
131	131		- CudaText 1.211.0. Opens file: 1 sec. Caret moves at the end of line: very fast (\<0.1 sec). Editing of this line: adding each char is about 0.1-0.2 sec.
132	132
133	133		- Sublime Text 4 4169. Opens file: 1 sec. Caret moves at the end of line: very fast (0.1-0.2 sec). Editing of this line: adding each char is about 0.1-0.2 sec.
134	134
135	135		- Geany 1.36. Opens file: 7 sec, then to go to end (Ctrl+End hotkey) it took 4 sec. Caret moves at line begin: fast, caret moves at line end: fast (delay about 0.3 sec after each Left/Right key). Moving up/down between 1st huge line and 2nd empty line: 3-4 sec. Editing at the end: adding each char is about 6 sec.
136	136
137	137		- Kate 23.08.4. Gives colored panel "The file ... was opened and contained lines longer than ... Those lines were wrapped and the document is set to read-only mode ...". Caret moves at the end of wrapped line: fast. But editing is disabled.
138	138
139	139		- Vim 8.1. Opens file: 1 sec. In word-wrapped mode and with partially colored line. Caret moves at the end of line: each Left/Right command (Vim hotkeys) is 2 sec delay. Editing of this line: adding each char is about 3 sec.
140	140
141	141		- Emacs 29.2 GUI. Opens file: 3 sec. Caret moves at the end of line: very fast. Editing of this line: adding each char is instant.
142	142
143	143		- gedit 3.36.2. Hanged on opening file (from command line and from GUI), waited it for 20 sec.
144	144
145	145		- Bluefish 2.2.11. On opening file, gives the warning about too long lines, on choosing "don't split lines" it hanged, waited for 30 sec.
146	146
147	147		## Performance of mass replace in huge lines
148	148
149	149		Compared a few editors in the task of replacing 25K single-char matches by two-chars-string in a 1.5MB file with a line with 800K chars. Running on Linux x64, CPU: Ryzen 5 1600, RAM: 32GB. Results:
150	150
151	151		- SciTE 5.4.1: after 6 min I could see the replaced text, but editor was still unresponsive (frozen). Awaited 6 more minutes and nothing changed, so I had to kill the window/process.
152	152		- Kate 23.08.4: complained about line length, took a long time to open the file, very poor performance while it was open... I couldn't even try replacing, it was unusable.
153	153		- Sublime Text 4 4169: crashed after 4 min processing the replace.
154	154		- Sublime Text 3.2.2: it took 2 min 30 sec to replace, the best one after CudaText.
155	155		- Notepad++ 8.6.4 with Wine: froze while replacing. I waited for 6 minutes but was still unable to do anything after that, so I had to quit.
156	156		- CudaText 1.211.0: did the task in 1 second.
157	157
158	158		## Performance of built-in sorting
159	159
160	160		Test on ~100M text file with short ASCII lines. Test on Ubuntu 19.10 on Intel i3 CPU.
161	161
162	162		CudaText 1.97:
163	163
164	164		- sort time of Command Palette command "(without undo) sort asc.": 18 sec
165	165		- sort time of Command Palette command "(without undo) sort asc., ignore case": 19 sec
166	166		- memory used after file loading: ~1.0 G
167	167		- peak memory used on sorting: the same (because sorting is inplace, in the same list)
168	168
169	169		Sublime Text 3.2:
170	170
171	171		- sort time: 14 sec
172	172		- sort time with ignoring case: 16 sec
173	173		- memory used after file loading: ~1.3 G
174	174		- peak memory used on sorting: ~3.3 G
175	175
176	176		# CudaText vs Sublime Text, different answers to questions
177	177
178	178		## How to call external programs/compilers?
179	179
180	180		ST3: Use feature of editor called "build systems".
181	181
182	182		CudaText: Use plugin "External Tools", which adds "Tools" item to the top menu. Or: use plugin "Runner". Both plugins are described here: [[CudaText plugins]].
183	183
184	184		Alternative answer for CudaText: Use plugin "Runner" which handles build-systems almost compatible with Sublime's build-systems.
185	185
186	186		## How to change settings for one OS only?
187	187
188	188		ST3: You need to use platform-specific config files. E.g. for macOS, platform-specific config is "Preferences (OSX).sublime-settings".
189	189
190	190		CudaText: You need to use the config user.json, but write there options with OS specific suffixes. E.g. Windows option is "font_name", and macOS option is "font_name__mac". Possible suffixes are listed in default.json: __linux, __mac, __freebsd etc. Only limited count of options support OS suffixes, this is marked in the default config (default.json).
191	191
192	192		## How to change settings for one syntax only?
193	193
194	194		ST3: To edit syntax-specific config, call "Preferences / Settings - Syntax Specific".
195	195
196	196		CudaText: To edit lexer-specific config, see [[CudaText\|CudaText#Configs]].
197	197
198	198		## How to add commands to top/context menu?
199	199
200	200		ST3: You need to create *.sublime-menu files: <https://www.sublimetext.com/docs/3/menus.html#available_menus>
201	201
202	202		CudaText: You need to install plugin "Configure Menu". In its dialog, create "menu.json" file which has default items of top menu and context menu. Then edit that file.
203	203
204	204		## How to find/replace text in many files?
205	205
206	206		ST3: Use built-in command "Find in files".
207	207
208	208		CudaText: Use plugin FindInFiles. It has 2 major versions: v3 is frozen, and new v4 is evolving.
209	209
210	210		## How to find file in a project?
211	211
212	212		ST3: Use "Goto Anything" (Ctrl+P on Windows/Linux, Command+P on macOS).
213	213
214	214		CudaText:
215	215
216	216		- To find file by name, use command "Plugins / Project Manager / Go to file...". After file is focused in project, press Enter to open it.
217	217		- To find file by contents, use plugin FindInFiles (v3) which allows to search in project files. Quote from its help:
218	218
219	219		Set special value "<Project Folders>" (in short <p>) for field "In folder" to search in project files.
220	220
221	221		## How to show vertical lines on some columns?
222	222
223	223		ST3: Use option
224	224
225		-	~~`"rulers": [40, 80, 120],`~~
	225	+	```text
	226	+	"rulers": [40, 80, 120],
	227	+	```
226	228
227	229		CudaText: Use option
228	230
229		-	~~`"margin_string": "40 80 120",`~~
	231	+	```text
	232	+	"margin_string": "40 80 120",
	233	+	```
230	234
231	235		## How to highlight pair brackets?
232	236
233	237		ST3: Brackets highlight is built-in feature, turned on by default.
234	238
235	239		CudaText: Brackets highlight is built-in, but it's off by default. Use several "bracket_" options, see comments in the "Options Editor" plugin.
236	240
237	241		## How to highlight pair HTML tags?
238	242
239	243		ST3: Use plugin, e.g. <https://packagecontrol.io/packages/BracketHighlighter>
240	244
241	245		CudaText: Use options for "dynamic highlighting", "lexer_dynamic_" in "Options Editor" plugin.
242	246
243	247		## How to add custom syntax support?
244	248
245	249		ST3: You need to create syntax file, <https://www.sublimetext.com/docs/3/syntax.html>
246	250
247	251		CudaText: You need to create lexer, see [[CudaText\|CudaText#Lexers]].
248	252
249	253		## How to customize hotkeys?
250	254
251	255		ST3: You need to edit keybinding files like "Default (Windows).sublime-keymap".
252	256
253	257		CudaText: In the Command Palette dialog, focus needed command item, press F9 - additional dialog will appear to set the hotkey. Method 2: install plugin "Configure Hotkeys" which gives alternative dialog.
254	258
255	259		## How to use Emmet?
256	260
257	261		ST3: Install plugin "Emmet". Emmet here is written in JavaScript.
258	262
259	263		CudaText: Use pre-installed plugin "Emmet". Emmet here is written in Pascal with minor differences (e.g. "lorem" works differently).
260	264
261	265		## How to show 2/3/4 files at once?
262	266
263	267		ST3: Use "View / Layout" menu.
264	268
265	269		CudaText: Use "=" item in the top menu.
266	270
267	271		## How to split window for single file?
268	272
269	273		ST3:
270	274
271	275		- menu "File / New View into File"
272	276		- menu "View / Layout / Columns: 2 (or Rows: 2)"
273	277		- drag the tab into another group
274	278
275	279		CudaText: menu "View / Split tab / Toggle split".
276	280
277	281		## How to detect syntax by first line of file?
278	282
279	283		ST3: It's configured in syntax file: <https://superuser.com/questions/752025/sublime-text-3-detect-syntax-based-on-file-header>
280	284
281	285		CudaText: Use config described in [[CudaText\|CudaText#Detection_by_first_file_line]].
282	286
283	287		## How to assign syntax to undetected file extension?
284	288
285	289		ST3: Open your file, click statusbar item for syntax, use item "Open all with current extension as...".
286	290
287	291		CudaText: Use "file types config", see [[CudaText\|CudaText#File_types_config]].
288	292
289	293		## How to select several occurrences of a word?
290	294
291	295		ST3: Use command "Selection / Expand selection to word".
292	296
293	297		CudaText: Use command "Selection / Add next occurrence of selected word".
294	298
295	299		There is a difference in CudaText implementation: CudaText command first checks, is first selection 'whole word' or not. If it's whole word, command adds selections which must be also whole words. In ST, command does not check 'whole word' state of next selections. You may switch to ST behaviour. How? CudaText "Command Palette" gives two commands:
296	300
297	301		- A: add next occurrence of selected word
298	302		- B: add next occurrence of selected text (not whole-word)
299	303
300	304		You can reassign hotkey from the command A to the command B, so hotkey will give the behaviour of Sublime Text.
301	305
302	306		## How to select all occurrences of a word?
303	307
304	308		ST3: In the Find dialog, enter a word, check "whole words", press "Find All".
305	309
306	310		CudaText:
307	311
308	312		- In the Find dialog, enter a word, check "whole words", press "Select all".
309	313		- Plugin "Highlights Occurrences" gives command "Select all occurrences".
310	314
311	315		## How to record macros?
312	316
313	317		ST3: Use menu items in the "Tools" menu.
314	318
315	319		CudaText: Install plugin "Macros", which adds item "Macros" to the top menu.
316	320
317	321		## How to use "Go to symbol"?
318	322
319	323		ST3: Use menu item "Go to symbol".
320	324
321	325		CudaText: It doesn't have "Go to anything" but it has "Go to symbol" for a lexer, if lexer finds such symbols for Code-Tree. Install plugin "CudaExt", which gives menu "Plugins / Cuda-Ext / Code-Tree" with several menu items. One item is "Symbols list" which shows Code-Tree items in the menu dialog.
322	326
323	327		## How to switch between C++ header/implementation files?
324	328
325	329		ST3: Use command "Switch header/implementation".
326	330
327	331		CudaText: Use plugin "Switch Header" (it's not only for C++, it's configurable for all lexers).
328	332
329	333		## How to jump to next/previous modified lines?
330	334
331	335		ST3: Use commands "Next modification", "Previous modification".
332	336
333	337		CudaText: Use plugin "CudaExt" which gives commands:
334	338
335	339		- "Jump: to next/previous changed lines",
336	340		- "Jump: to next/previous working lines",
337	341		- "Jump: to next/previous saved lines".
338	342
339	343		See [[CudaText\|CudaText#Line_states]].
340	344
341	345		## How to detect indentation characters in a file?
342	346
343	347		ST3: Menu item "View / Indentation / Guess settings from buffer".
344	348
345	349		CudaText: Plugin "Detect Indent" which does the same.
346	350
347	351		## How to change indentation characters in a file?
348	352
349	353		ST3: Click statusbar cell "Tab size..."/"Spaces...", it has menu items "Convert indentation to spaces", "Convert indentation to tabs".
350	354
351	355		CudaText: The same as for ST3.
352	356
353	357		## How to install plugins without package manager?
354	358
355	359		ST3: Open terminal, go to Packages folder, run "git clone" in that folder, or copy plugin there.
356	360
357	361		CudaText: Open terminal, go to "py" subfolder, run "git clone" in that folder, or copy "cuda_" plugin folder there.
358	362
359	363		## How to make vertical/column selection?
360	364
361	365		ST3: See the official documentation page "Column Selection".
362	366
363	367		CudaText:
364	368
365	369		- Mouse shortcuts: [[CudaText\|CudaText#Mouse shortcuts]].
366	370		- Keyboard commands: "column select: up / down / left / right / ....".
367	371		- Click the statusbar cell "-", it will toggle to "\\|\\|", and usual mouse selection will perform column selection.
368	372
369	373		## How to swap line up/down
370	374
371	375		ST3: Commands "Edit / Line / Swap Line Up/Down".
372	376
373	377		CudaText: Commands "Edit / Line operations / Move line(s) up/down".
374	378
375	379		## How to show menu of tabs, project files, symbols
376	380
377	381		ST3: "Goto anything" (Ctrl+P) for all stuff.
378	382
379	383		CudaText:
380	384
381	385		- List of opened tabs: command "ui: switch tab, dialog".
382	386		- List of files in the current project: "plugin: Project Manager: Go to file".
383	387		- List of "symbols" in the current document: "plugin: Cuda-Ext: Code-Tree: Symbols list" (shows the same symbols as code-tree can show).
384	388
385	389		## How to use 'atomic saving'
386	390
387	391		'Atomic' file saving is saving to a temporary file, then renaming that file to the destination. 'Atomic' saving is not implemented in CudaText, because users of Sublime Text 3 consider it as harmful feature.
388	392
389	393		- It drops extended file attributes (on NTFS on Windows; Unix-like have similar problem too?)
390	394		- It drops NTFS file streams, on Windows
391	395		- Problems with files located on Network drives, on Windows
392	396		- Problems with symlinks
393	397		- It needs additional options like "on which drives to use atomic saving"
394	398
395	399		# CudaText vs Notepad++
396	400
397	401		(From user dinkumoil, quote from the Notepad++ forum.)
398	402
399	403		But since this thread has the potential to be a useful information and I’m a user of CudaText as well, I respond to it (I also contributed to the CudaText source code, wrote a plugin similar to my AutoCodepage and AutoEolFormat plugins for Notepad++, helped to improve the SQL and VBScript lexers and currently maintain the German translation file).
400	404
401	405		Indeed, CudaText is a powerful text editor and its author is an experienced dev in writing text editors and software components needed for that as he is also the author of the discontinued SynWrite editor. Since the above feature list is only a usual catalog for text editors, I want to go a little bit into the details.
402	406
403	407		Advantages
404	408
405	409		- Quick evolving project.
406	410		- Quick responding and very active developer.
407	411		- Constant, nearly daily work at the project (have a look at the commit tracker).
408	412		- No political activities.
409	413		- Extensive and always up-to-date wiki and API documentation .
410	414		- The UI follows Windows settings for font size in menus and dialog boxes, important when using high-DPI monitors.
411	415		- The whole UI is themeable, not just the edit window.
412	416		- Up to 6 edit windows, each with an unlimited number of tabs. Even a single tab can be splitted in two areas.
413	417		- A plugin allows to fully customize the whole main menu.
414	418		- Very well working Code Tree (in Notepad++ called Function List) that supports automatically all languages which are supported by lexers.
415	419		- Monitoring of opened files for changes from other programs seems to work more reliable than in Notepad++.
416	420		- Separate lexer creation tool with sophisticated abilities. It supports using regular expressions.
417	421		- Plugins can be written in Python (but this has to be paid with lower execution speed for sophisticated tasks).
418	422		- Only for the records, no advantage over Notepad++: Lots of useful plugins available, one of them is a plugin manager. It allows installing, updating and removing of plugins.
419	423
420	424		Disadvantages
421	425
422	426		- In some details slightly slower working speed than Notepad++.
423	427		- Configuring the toolbar is a little bit tricky. It requires a plugin and needs intensive work.
424	428		- Translations for the UI into other languages are available but a lot of them are outdated.
425	429		- The Search & Replace feature uses a rather old regular expression engine which lacks some sophisticated features (IMO the biggest drawback). Edited by Alexey: RegEx engine was much improved since the time of this complain.
426	430		- There is no built-in preferences dialog. Instead you have to edit a JSON file (but that’s far better than writing CSS code like in Atom). There is a plugin available that tries to work like a preferences dialog but it’s only a tableized, textual view of all settings and a primitive UI to change them.
427	431		- Under Windows, a plugin installs an Explorer context menu. But since its only backed by a shell\CudaText\command registry entry and not with a real shell handler like Notepad++'s context menu entry, it is not possible to open more than 15 files at once using the CudaText Explorer context menu entry. That’s a common limitation for all non-shell-handler context menu entries (tested under Windows 7 x64). Edited by Alexey: this is not actual anymore, since we have dedicated Explorer shell extension DLL.
428	432		- Releases of CudaText are published only as ZIP files without an installer. So, updating means all plugins, custom icons, additional lexers, autocompletion files, language files, theme and lexer customizations and so forth have to be migrated to the directory of the new version. You need a file and directory based diff tool for that.
429	433		- Only a small community, the forum mostly is a lonely place. Like the developer a lot of the people commenting in the GitHub issue tracker are russian, thus they tend to write in cyrillic. But this is clearly an advantage for people from Russia which have to take the burden to write and read in English, written in latin letters here in the Notepad++ forum and in the GitHub repo.
430	434		- Somewhat chaotic project structure. Source code on GitHub, binary releases on SourceForge, forum on a SourceForge-hosted home page, lots of relations to the discontinued SynWrite editor (e.g. lexers are hosted in a separate SourceForge project called SynWrite add-ons, the lexer creation tool is an excerpt of that particular part of SynWrite).
431	435
432	436		Conclusion
433	437
434	438		All in all I would say CudaText is an excellent addition to Notepad++, but I personally will continue to use both editors since both of them have their strengths and weaknesses. And since I think the CudaText project deserves more support, I hereby appeal to participate in this project as well, if possible.
435	439
436	440		---
437	441		From the Free Pascal wiki, page "CudaText VS other editors", as it stood on 2024-04-18 after a change by Alextp, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).
438	442		Category: CudaText
439	443		Category: Tools

Back to history