Page 1 of 2
hilite is a problem
Posted: 04.12.2017 13:51
by powerpcer
lexer_delayed_parsing_size and lexer_delayed_parsing_pause should not happen, this no matter in Ultraedit or notepad++ or sublime or ...
no one wants to see refresh when he is typing.
and HiliteOccurrences i set to 20, but still got lag.
Posted: 04.12.2017 14:05
by Alexey
1- options are needed for big files. You can set big values. so delay will be only on big files.
2- Show all config file of HiliteOccurences here
Posted: 05.12.2017 01:47
by powerpcer
1. no matter how are big file, it should not refresh like that, likely in akelpad, ultraedit
2. config of HiliteOccurences
[op]
min_len=1
sel_allow=1
sel_allow_white_space=0
sel_case_sensitive=0
sel_words_only=0
sel_whole_words=0
caret_allow=1
caret_case_sensitive=1
caret_whole_words=1
max_lines=20
Posted: 05.12.2017 08:30
by Alexey
Config of plugin is ok [but plugin dont work if file has >20 lines]. maybe it's not plugin who is slow.
Posted: 05.12.2017 15:35
by powerpcer
as i said before, syntax analysis should not do it for entire file just do incremental update
Posted: 05.12.2017 19:33
by Alexey
I cannot make fast update for Big files. So options (2) exist. lexer_delayed_nnnnn.
Posted: 06.12.2017 03:06
by powerpcer
Alexey, just take a global view of how the future of lexer should look like.
akelpad and tagsview can be a reference
but hilite on word selected, that's no need tell users how much in entire file, just show them the same word in user view.
Posted: 06.12.2017 09:54
by Alexey
I don't understand u. About Hilite plugin: its good that it hilites words in entire file.
Posted: 06.12.2017 14:06
by powerpcer
but i cannot see the entire file, if file large then screen.
so just show what i can see, don't need entire.
also don't need count, if i want count it up, i think i will use find function.
Posted: 10.12.2017 06:58
by Alexey
This is wish about HiliteOccurences? It's ok that all file is hilited. i want to scroll file, and see all matches.