UVviewsoft forums

Wrote wish about "Fill Block" cmd to Github of CudaExt.

Option for place of new tab - it is not good. Almost everytime place must be "last", but sometime need be "next" (same in the opposite situation). Switcher-option is too not comfortable. Need second command.

Agree that we all have our own preferences; for me, almost every time must be "next", but sometimes "last" .

If second command (that's okay with me, but...) what functions would use the new command? I would like everything to place tab "next", like when get results from text-statistics or from sum, or when open new file, etc. But I think you would like the opposite .

So that's why I think option is better than second command--I mean an option in user.json, so user can set it and forget it--NOT an option question that must be answered every time a tab is created (hope you didn't think that ). Why is option not good?

Alexey wrote:Added option ui_tab_new_near_current, since 1.14.1

Thank you.

Alexey wrote:Plugin "Column Marks" updated in Github (see Plugins/ Addon Manager/ Visit plugin homepage)
+ command "Set fixed margin"

Thank you, set margin works well.

What did you think about having setting the margin and column marks, also set the "margin" and "margin_string" options in user.json?

IMO no need - for plugin -to set margins also in user.json. Option here - better use Options Editor plugin.

Alexey wrote:IMO no need - for plugin -to set margins also in user.json. Option here - better use Options Editor plugin.

Okay. I guess because options in user.json are global, but plugin options are per file/tab?

Yes, it is right.

qwerky,
You stated in the big 11Kb review that spell-checking is
not capable to help writers. But it works ok on None lexer.
So for writers too with None lexer.
I checked it just now (Linux or Win32bit)

Alexey wrote:qwerky,
You stated in the big 11Kb review that spell-checking is
not capable to help writers. But it works ok on None lexer.
So for writers too with None lexer.
I checked it just now (Linux or Win32bit)

Hi Alexey, as I wrote, the spell-checker seems not to work on 64-bit, so I had only had the readme to go by, which says that not all text is checked, only comments and strings. If it does in fact check all text, I'm glad to hear it ! I'm looking forward to the 64-bit version .