Yes I can reproduce it too with notes, guess that we’ll have to wait for Apple on this one then. Looks like it has been around for quite some time. Thanks

OK just checked too with an ipad mini with ios 26.2 and textastic 10.7, other bluetooth keyboard cover attached to the mini, textastic welcome text : same issue.

I’m selecting the whole line with shift+cursor and found an interesting thing : it only behaves like this if the cursor up / down move after the copy is the opposite of the cursor move used to select the line :

- select with shift+cursor+up, command-c, cursor down -> move to end of file

- select with shift+cursor+up, command-c, cursor up -> cursor up one line

- select with shift+cursor+down, command-c, cursor up -> move to start of file

- select with shift+cursor+down, command-c, cursor down -> move down one line

Hope that helps,

Hi Alexander, thanks for the quick reply. I just tested again : 

- Select whole line with shift + cursor up

- Command + c

- Count to 3 😁

- Cursor up : moves to top of file

- Cursor down : returns to insertion point

I also re-tested directly after that with the magic keyboard attached to confirm that I was able to have the same behaviour

All files are remote (shellfish) if that changes anything, and I also have a magic trackpad connected

I have other iPads to test with too if needed, I tried activating the log too but nothing of interest was written.

Version 10.7 for textastic but I had this issue before, just wasn’t able to replicate.

iPad OS 18.5

Test file is a 700 lines JS file, changes to the configuration done were to make all characters visible & soft tab with 4 spaces.

Happy to help / send video or whatever would be useful.

If there’s provision for local LLMs (ollama endpoint for example) then count me in ! 

Not that simple for the UI side as there’s a lot to think about even outside of configuration, like providing context elements : whole file, selected part if any, question, maybe more… and results filtering (code blocks, explanations)