cursor tracking with a screen reader

[douglangley]

I am trying to use micro with a screen reader.
Is there a way to have cursor move the physical system cursor instead of the fake cursor? I have tried setting fakecursor to true and false with no difference in functionality. The main system cursor always stays on the status line.
Is there a setting I can set to use the real system cursor, and if not, is this something that can be easily added?

[JoeKar]

I would expect that fakecursor does make the difference between both. By default it is inactive and the terminals cursor should be the one controlled, which is the reason why it isn't colored by the color scheme. Activating the fakecursor would draw micro's SW cursor.
Is it possible for you to record a small screen cast video/GIF? This would help to understand what is going on/wrong.

[dmaluka]

@douglangley are you using Windows? Micro forces enabling fakecursor on Windows, except for Windows Terminal (#1900).

So you might try compiling micro with the following change (although, according to comments in the code, it is gonna make the cursor very slow):

--- a/internal/util/util.go
+++ b/internal/util/util.go
@@ -93,10 +93,6 @@ func init() {
 		fmt.Println("Invalid version: ", Version, err)
 	}
 
-	_, wt := os.LookupEnv("WT_SESSION")
-	if runtime.GOOS == "windows" && !wt {
-		FakeCursor = true
-	}
 	Stdout = new(bytes.Buffer)
 }
 

[douglangley]

You solved it. it was because I tested in windows first.
This works fine in linux.

[JoeKar]

Ah, ok...so the forced fakecursor in non-WT was the reason.
Good catch @dmaluka!

Maybe it is better to force the default of the global setting under Windows instead of hard coding it. This makes it easier for the user to override the default via the settings.json. 🤔

[dmaluka]

Maybe it is better to force the default of the global setting under Windows instead of hard coding it. This makes it easier for the user to override the default via the settings.json. 🤔

Sounds like a good idea.