starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Bug Report: weird cursor behaviour in Far Manager command line #3592

New Issue
Closed
opened 2026-01-30 23:25:07 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:25:07 +00:00
Owner
Copy Link

Originally created by @luzhkovvv on GitHub (Aug 27, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version: 0.4.2382.0
Far Manager - practically any available, last tested on Far Manager v3.0 build 5454 x64 (2019-08-23)

Steps to reproduce

  • install Far Manager from https://farmanager.com/download.php?l=en
  • run Far Manager inside Windows Terminal (from cmd session or by creating new profile)
  • type any text, look how cursor moves in command line while typing
  • press Ctrl-O, try to move cursor using directions keys
  • press "Enter" with any text entered in command line (no matter when in panels mode or in history mode, switched by Ctrl-O, no matter if correct command or any text)
  • type any text again, look how cursor moves while typing
  • press Ctrl-O, try to move cursor using directions keys

Expected behavior

  • cursor follows entered text
  • cursor moves when "left" or "right" button pressed
  • just like it is after fresh start

Actual behavior

  • cursor is displayed before last printed character, not after
  • cursor does not moves when left or right buttons are pressed (just not displayed, internal position gets updated)

P.S. As I get it, it has something to do with the way Far clears and redraw the screen or with the way commands are executed in Far, but I have no ways to localize that bug in Windows Terminal or in Far. At least same version of Far works OK in plain cmd.exe or ConEmu.

Originally created by @luzhkovvv on GitHub (Aug 27, 2019). # Environment ``` Windows build number: Microsoft Windows [Version 10.0.18362.295] Windows Terminal version: 0.4.2382.0 Far Manager - practically any available, last tested on Far Manager v3.0 build 5454 x64 (2019-08-23) ``` # Steps to reproduce - install Far Manager from https://farmanager.com/download.php?l=en - run Far Manager inside Windows Terminal (from cmd session or by creating new profile) - type any text, look how cursor moves in command line while typing - press Ctrl-O, try to move cursor using directions keys - press "Enter" with any text entered in command line (no matter when in panels mode or in history mode, switched by Ctrl-O, no matter if correct command or any text) - type any text again, look how cursor moves while typing - press Ctrl-O, try to move cursor using directions keys # Expected behavior - cursor follows entered text - cursor moves when "left" or "right" button pressed - just like it is after fresh start # Actual behavior - cursor is displayed before last printed character, not after - cursor does not moves when left or right buttons are pressed (just not displayed, internal position gets updated) P.S. As I get it, it has something to do with the way Far clears and redraw the screen or with the way commands are executed in Far, but I have no ways to localize that bug in Windows Terminal or in Far. At least same version of Far works OK in plain cmd.exe or ConEmu.
claunia commented 2026-01-30 23:25:08 +00:00
Author
Owner
Copy Link

@luzhkovvv commented on GitHub (Aug 27, 2019):

Oops, it seems to be fixed by "Use Virtual Terminal for rendering" Far Manager option. Just for me that's enough, don't know if that "bug" still worth investigation.

@luzhkovvv commented on GitHub (Aug 27, 2019): Oops, it seems to be fixed by "Use Virtual Terminal for rendering" Far Manager option. Just for me that's enough, don't know if that "bug" still worth investigation.
claunia commented 2026-01-30 23:25:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 29, 2020):

Note that this isn't fixed by #4372, and definitely still repros in 0.8 (and I suppose master (e8658cd) + #4372 as well)

@zadjii-msft commented on GitHub (Jan 29, 2020): Note that this _isn't_ fixed by #4372, and definitely still repros in 0.8 (and I suppose master (e8658cd) + #4372 as well)
claunia commented 2026-01-30 23:25:08 +00:00
Author
Owner
Copy Link

@oleksabor commented on GitHub (Jan 31, 2020):

I've just got the invisible cursor issue for Far manager.
I've installed the latest Windows 10 19009 build and can't see cursor in the Far window. I had used Windows 10 1803 before and there was no problem with cursor.

The problem is that it looks like cursor is shown however it has black colour.

I had to change Far shortcut Cursor colors option on the Terminal tab. I set Cursor color to inverse and white cursor started to blink as before.

@oleksabor commented on GitHub (Jan 31, 2020): I've just got the invisible cursor issue for Far manager. I've installed the latest Windows 10 19009 build and can't see cursor in the Far window. I had used Windows 10 1803 before and there was no problem with cursor. The problem is that it looks like cursor is shown however it has black colour. I had to change Far shortcut `Cursor colors` option on the `Terminal` tab. I set `Cursor color` to `inverse` and white cursor started to blink as before.
claunia commented 2026-01-30 23:25:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 4, 2022):

Hey so I know it's been few years, but I'm playing around with Far 3.0.5888.0 and Terminal 1.12, and this seems fixed to me. OP can you confirm? I suspect this was accidentally fixed by something else along the way.

@zadjii-msft commented on GitHub (Jan 4, 2022): Hey so I know it's been few years, but I'm playing around with Far 3.0.5888.0 and Terminal 1.12, and this seems fixed to me. OP can you confirm? I suspect this was accidentally fixed by something else along the way.
claunia commented 2026-01-30 23:25:09 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 8, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jan 8, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Output Issue-Bug Needs-Author-Feedback No-Recent-Activity Priority-2 Product-Conpty
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3592
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?