I am using your iOS terminal to communicate with BASH and Powershell remote servers. When I connect to a BASH session, everything works as expected. But when I connect to a PowerShell session, every time I type something, only garbage characters are displayed. Yet when I press RETURN, the correct command executes. For instance:

I connect to a macOS 11 machine running PowerShell as its default shell. I get:

PowerShell 7.1.3
Copyright © Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

PS /Users/frios>

All is good until I start typing. I type d and I get d$<5> then I type i and the d disappears and I get $<$<5> then I type r and I get $<5$<5>

If I then hit return I get the proper directory output on the screen but if the screen is full, the cursor jumps to mid screen.

Anyone seen this type of behavior before?

The work in these commits is covered by the MIT license and I hope it can be of some use even if a lot is about extracting lines in a scroll-invariant way.

The UI views could run async from the actual engine.

While currently the engines already do the sort of frame-based rendering, there are situations where we can still be processing too much data in parse without triggering an update to the UI.

So I would like to fully move to frame-based rendering to be independent of the parsing happening in the background. For this, it would be important to add a modicum of synchronization, but that can happen entirely within the parse method, as no mutation would take place if that method suspends execution if the UI needs to update the display.

I'm having pretty great success with SwiftTerm but there is one app that is not rendered properly: when I run Emacs within SwiftTerm, it's layout is a bit off when I M-x help in a wide terminal so that you get a side by side split.

I've set the terminal to xterm-256color and xterm but that doesn't seem to make a difference.

The only hint I have is that SwiftTerm prints

Info: Unhandled Window command: [22, 0, 0]
Info: Unhandled Window command: [23, 0, 0]

What is the best place to lookup these codes? Maybe handling these commands is this is an improvement I can contribute?

Update: Note that the Unhandled Window command may be a red herring - I don't think it is happening during rendering. See comments.

I'm not sure this is the correct way to do this but here it is.

Currently UIScrollView does not work. And I don't think there is a possible way for it to work. The gestureRecognizers added will conflict with those inside UIScrollView, making UIScrollView totally unusable.

So I just make it plain UIView and put together scrolling logic. This way there'll be no fancy scrollbar or bouncing, but the scrolling will work.

Refactor terminal view options into single property: options. This property is intended to be modified by the user, and the view should apply the changes.

Put this snippet in TerminalView.setup() and see how it change colors:

DispatchQueue.main.asyncAfter(deadline: .now() + .seconds(5)) {
    let o = Options(font: Options.default.font, colors: Options.Colors(useSystemColors: true))
    self.options = o
}

I am trying to add this dependency through Xcode 11, but when I input the URL, there is no version information for the rules. Where do i get that? Pardon my naivte

Fixes #67

• [x] revert to fixed height/width for size, yet still draw glyphs that cross the lines
• [x] disable selection view (again) and fixes performance issue when updating selection
• [x] update caret view position along the lines
• [x] draw underline
• strikethrough doesn't (never did)

Fixes #54

In this PR:

• Selection highlight in pair with displayed glyphs

  • before

  • after

• dynamic line-height support

  • before

  • after

• Improved support for font metrics. Calculate lines positions based on used font (no more magic offset values)

• Sharp background frame - fullBackgroundColor attribute

  • before
  • after

This line: https://github.com/migueldeicaza/SwiftTerm/blob/main/Sources/SwiftTerm/iOS/iOSExtensions.swift#L15

causes a crash sometimes on iOS 14 with the error: Swift runtime failure: Double value cannot be converted to UInt16 because the result would be greater than UInt16.max

It seems to be a precision issue:

(lldb) p red
(CoreFoundation.CGFloat) $R3 = (native = 0.99990183115005493)
(lldb) p green
(CoreFoundation.CGFloat) $R4 = (native = 1.0000687837600708)
(lldb) p blue
(CoreFoundation.CGFloat) $R5 = (native = 0.99987989664077759)

I just updated to the latest build (I assume its 1.0.7) and am receiving the following error messages when building

'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead.

and 

'open(_:options:completionHandler:)' is unavailable in application extensions for iOS

at the following location

    public func requestOpenLink (source: TerminalView, link: String, params: [String:String])
    {
        if let fixedup = link.addingPercentEncoding(withAllowedCharacters: .urlQueryAllowed) {
            if let url = NSURLComponents(string: fixedup) {
                if let nested = url.url {
                    UIApplication.shared.open (nested)
                }
            }
        }
    }

at the line UIApplication.shared.open(nested)

This is an iOS app.

I caught the issue in the wild, the crash is:

    frame #3: 0x000000019475f134 libswiftCore.dylib`Swift._assertionFailure(_: Swift.StaticString, _: Swift.String, file: Swift.StaticString, line: Swift.UInt, flags: Swift.UInt32) -> Swift.Never + 652
    frame #4: 0x0000000102b7f84c LaTerminal`CircularList.shiftElements(start=47, count=3, offset=1, self=0x0000000280bf5680) at CircularList.swift:169:9
  * frame #5: 0x0000000102beebe4 LaTerminal`Terminal.reverseIndex(self=0x00000001043e4ed0) at Terminal.swift:4937:26
    frame #6: 0x0000000102bbeb98 LaTerminal`closure #84 in Terminal.configureParser(collect=0 values, flag=77, self=0x00000001043e4ed0) at Terminal.swift:868:76

The issue is that shiftElements is being called with start=47, but the buffer itself only has 42 lines. The 47 is a combination of buffer.y = 21 and buffer.base = 26. And also notice that buffer.y = buffer.scrollTop which is why this path is triggered at all, originMode=false, usingMargins() = false

I was running top, and messing up the display with debug output from a background process, and I had refreshed it a few times, and I had just attempted to go to the background with control-z

The data was: [0] = "\r" [1] = "\u{1b}" [2] = "[" [3] = "3" [4] = "4" [5] = "d" [6] = "\u{1b}" [7] = "[" [8] = "L" [9] = "\u{1b}" [10] = "[" [11] = "2" [12] = "2" [13] = ";" [14] = "2" [15] = "5" [16] = "r" [17] = "\u{1b}" [18] = "[" [19] = "2" [20] = "2" [21] = ";" [22] = "1" [23] = "H" [24] = "\u{1b}" [25] = "M" }

Cursor Vertical Absolute Position 34 Insert Line Set Top and Bottom Margin to 22;25 (sets buffer.scrollBottom = 24, buffer.scrollTop=21) Set Cursor Position 22;1 Reverse Index

Most likely, what we have here are two different buffers in action.

This allows option-tap to send cursor arrow movements to reach a destination, like Terminal.app does.

In application mode, this could send the sequence of cursor movements to get to the target location, in regular mode, it should probably only do left/right, as up/down navigates a command line history.

Hi,

I work on CodeEdit and there's a terminal rendering defect. We use SwiftTerm as the package for our terminal emulator

Click here to see the issue and please comment on it as soon as you can.