Humza Shahid 886f384490 when deleting inside pair, instead of searching either for either chr1 or chr2 and stopping at first match, search instead for openChr and closeChr, and keep an integer tracking what level of nesting we are at. This gives us the behaviour we want, which is to delete the pair at the correct level of nesting. When we encounter openChr, we increment the nesting counter by 1 and continue searching. When we encounter closeChr, if the nesting counter is 0, we return the current index, but if the nesting counter is higher than 0 when encounter closeChr, we decrement the nesting counter by 1 and continue searching.

2026-01-02 18:50:04 +00:00

..

make-normal-delete.sml

when deleting inside pair, instead of searching either for either chr1 or chr2 and stopping at first match, search instead for openChr and closeChr, and keep an integer tracking what level of nesting we are at. This gives us the behaviour we want, which is to delete the pair at the correct level of nesting. When we encounter openChr, we increment the nesting counter by 1 and continue searching. When we encounter closeChr, if the nesting counter is 0, we return the current index, but if the nesting counter is higher than 0 when encounter closeChr, we decrement the nesting counter by 1 and continue searching.

2026-01-02 18:50:04 +00:00

normal-delete.sml

functorise NormalDelete structure so we can use share the same deletion logic and code for NormalDelete and NormalYankDelete (the latter which is not yet implemented)

2025-09-06 03:43:45 +01:00

normal-finish.sml

remove usage of concurrent ml, deciding that we prefer to run everything in the main thread instead

2025-10-17 23:08:16 +01:00

normal-mode-with.sml

remove 'searchString' field from app_type, because the same role is fulfilled by new 'dfa' field

2025-10-08 05:40:29 +01:00

normal-mode.sml

when deleting inside pair, instead of searching either for either chr1 or chr2 and stopping at first match, search instead for openChr and closeChr, and keep an integer tracking what level of nesting we are at. This gives us the behaviour we want, which is to delete the pair at the correct level of nesting. When we encounter openChr, we increment the nesting counter by 1 and continue searching. When we encounter closeChr, if the nesting counter is 0, we return the current index, but if the nesting counter is higher than 0 when encounter closeChr, we decrement the nesting counter by 1 and continue searching.

2026-01-02 18:50:04 +00:00

normal-move.sml

reimplement '/home/humza/Downloads/sml/shf/todo.md' motion so that it has the same behaviour as Vim. (If the cursor is not at a pair character, then check after the cursor to see if we find a pair-character there. If some location after the cursor has a pair-character, then move the cursor to it and find the pair of the character, if any.)

2026-01-01 06:58:30 +00:00

normal-search-finish.sml

pass DFA to 'SearchList.buildRange' function, so that we don't need to parse search string into DFA each time

2025-10-08 05:20:33 +01:00

normal-search-mode-with.sml

remove 'searchString' field from app_type, because the same role is fulfilled by new 'dfa' field

2025-10-08 05:40:29 +01:00

normal-search-mode.sml

fix bug when saving search from NORMAL_SEARCH_MODE. Previously, when pressing <Enter> to save the search, the tempSearchList (which searches against a subset of the buffer's text instead of all of it, to ensure we do not spend too much time was spent while the user was entering the regex/search string) was being saved instead of the newly built searchList (which executes the DFA against all of the text)

2025-12-02 17:55:25 +00:00

normal-yank-delete.sml

add yank-delete motions like 'ydw' and so on

2025-09-06 03:53:47 +01:00

normal-yank.sml

remove 'Cursor.tillPrevChr', replacing usages of that function with 'Cursor.toPrevChr'

2025-10-19 14:30:26 +01:00