Ok, the readme was confising...
I plan to make 64bit ver, later after vacation.
Can you try this? download PyEnchant library WHEEL (it is zip) from PyPI.org. For Win 64bit. And unpack wheel/zip to plugin's folder (same dir name)
Missing functions...
pypl.org goes to a public library in Penn Yan, NY. A search for "PyEnchant library WHEEL" showed two versions:Alexey wrote:Ok, the readme was confising...
I plan to make 64bit ver, later after vacation.
Can you try this? download PyEnchant library WHEEL (it is zip) from PyPI.org. For Win 64bit. And unpack wheel/zip to plugin's folder (same dir name)
1.6.6
1.6.11
In both, the structure is:
/enchant/
/enchant/checker/
/enchant/lib/enchant/
/enchant/share/enchant/ispell/
/enchant/share/enchant/myspell/
/enchant/tokenize/
/pyenchant-1.6.x.dist-info/
Also, I don't have a /CudaText/Plugins/ folder; did you mean /CudaText/py/ ?
So, should this be unzipped to /CudaText/py/ giving:
/CudaText/py/enchant/
/CudaText/py/pyenchant-1.6.x.dist-info/
Or, to /CudaText/py/enchant/ giving:
/CudaText/py/enchant/enchant/
/CudaText/py/enchant/pyenchant-1.6.x.dist-info/
Note: everything else in /CudaText/py/ is /cuda_xxx/.
Also, this thread has no recent response from the author; is it dead/abandoned? No one has been able to get a 64-bit version to work. And stackoverflow also says there is no 64-bit version, but that perhaps a 32-bit version should work on a 64-bit architecture?
Please show exactly how you want it, and I will try it (I'm not a Python programmer.)
Alexey wrote:>And stackoverflow also says there is no 64-bit version
It is stopper. :-\
So, there will be no spell-checker for 64-bit CudaText?Alexey wrote:To use SpellChecker (32-bit) one must reinstall CudaText (cudatext.exe and *.pyd, *.dll, *.zip) from x32 build.
Understood that this is not your fault, since enchant developer won't do 64-bit. Is there any other work-around? Perhaps a different spelling engine?
These work, but in addition to moving the caret/cursor to the top/bottom line of the screen, they also move it to the first column (column 1). I quite like this, but it is actually a different command than what I was expecting, which was to keep the same column that the cursor was currently on, which is how I find it to be in other editors, because this facilitates other operations (just so you know, I always use "allow cursor past end of line" mode).Alexey wrote:Release 1.12: added also "go to screen top/ bottom"
(like Synwrite)
Perhaps two sets of commands? These present ones could be called "Screen Top/Left" and "Screen Bottom/Left"? I tend to think of these as an alternate-home/-end, like it used to be in some old DOS editors, like QEdit.
In the 1.14.4.0 default.json, I see the option is there (though it is marked as not yet ready). Just wanted to say thanks for working on this.Alexey wrote:>>thing is that in column select mode, moving the cursor up/down actually creates multiple carets. This is a bit of a distraction
Column-select, with and w/o new commands for columns select, is always making multi-carets. it's a problem? why?
column-select was w/o multi-carets long ago. Ppl asked to do it with carets.