--termcmd option not recognized
See original GitHub issueI ran the command fvim --termcmd powershell
, here’s the stacktrace:
Exit code: 1
Exception message: neovim crashed
nvim.exe: Unknown option argument: "--termcmd" More info with "nvim.exe -h"
at Microsoft.FSharp.Core.PrintfModule.PrintFormatToStringThenFail@1433.Invoke(String message) in F:\workspace_work\1\s\src\fsharp\FSharp.Core\printf.fs:line 1433
at FVim.states.msg_dispatch(Event _arg1) in D:\a\1\s\states.fs:line 285
at FVim.model.Start@146.Invoke(Event arg1) in D:\a\1\s\model.fs:line 146
at FSharp.Control.Reactive.ObservableModule.subscribe@1674-2.Invoke(T delegateArg0)
at System.Reactive.AnonymousSafeObserver1.OnNext(T value) in /_/Rx.NET/Source/src/System.Reactive/AnonymousSafeObserver.cs:line 44 at System.Reactive.Sink
1.ForwardOnNext(TTarget value) in //Rx.NET/Source/src/System.Reactive/Internal/Sink.cs:line 50
at System.Reactive.Concurrency.ObserveOn1.Context._.OnNextPosted(Object value) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/Synchronization.ObserveOn.cs:line 118 at Avalonia.Threading.AvaloniaSynchronizationContext.<>c__DisplayClass8_0.<Post>b__0() at Avalonia.Threading.JobRunner.Job.Avalonia.Threading.JobRunner.IJob.Run() at Avalonia.Threading.JobRunner.RunJobs(Nullable
1 priority)
at Avalonia.Win32.Win32Platform.WndProc(IntPtr hWnd, UInt32 msg, IntPtr wParam, IntPtr lParam)
at Avalonia.Win32.Interop.UnmanagedMethods.DispatchMessage(MSG& lpmsg)
at Avalonia.Win32.Win32Platform.RunLoop(CancellationToken cancellationToken)
at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
at FVim.Program.app@126-1.Invoke(Window win) in D:\a\1\s\Program.fs:line 129
at FVim.Program.startMainWindow(FSharpFunc`2 app, ServerOptions serveropts_0, Boolean serveropts_1, Boolean serveropts_2) in D:\a\1\s\Program.fs:line 78
at FVim.Program.Main(String[] args) in D:\a\1\s\Program.fs:line 138
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (6 by maintainers)
thanks for confirming. I’ll figure out a fix.
Yes, now the line works