Hello - Is there a way to have your ~/.bas

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Read ~/.bashrc When Running A .fsx Script? about ionide-vscode-fsharp HOT 7 CLOSED

eatobin commented on September 18, 2024

Read ~/.bashrc When Running A .fsx Script?

from ionide-vscode-fsharp.

Comments (7)

MangelMaxime commented on September 18, 2024

To me it looks like there is a mix happening here. Because, you are trying to setup a Powershell configuration from inside a .bashrc which is in general associated to bash and not Powershell.

I think customisation of Powershell should be done inside the $PROFILE code.

Exemple: notepad $PROFILE

https://learn.microsoft.com/en-us/windows/terminal/tutorials/custom-prompt-setup#choose-and-apply-a-powershell-prompt-theme

from ionide-vscode-fsharp.

eatobin commented on September 18, 2024

@MangelMaxime Thank you - but I don't understand. Where does Powershell come in? I am on Linux (Ubuntu) and use bash. Is Powershell used by Ionide-VSCode to run a .fsx script?

from ionide-vscode-fsharp.

MangelMaxime commented on September 18, 2024

Oops sorry I thought PS1 was related to PowerShell as when quickly looking at the screenshot I thought that the window I took for a window terminal (Sublime Text) looked similar to Windows Terminal.

I was probably not properly awake this morning 😅

from ionide-vscode-fsharp.

eatobin commented on September 18, 2024

No problem. Any thoughts on how to read the .bashrc file before running a .fsx in ionide? Sent from my rotaryPhone.

…

On Tue, Feb 6, 2024, 10:45 Maxime Mangel ***@***.***> wrote: Oops sorry I thought PS1 was related to PowerShell as when quickly looking at the screenshot I thought that the window I took for a window terminal (Sublime Text) looked similar to Windows Terminal. I was probably not properly awake this morning 😅 — Reply to this email directly, view it on GitHub <#1983 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGUSKUFEKQCLMJ64EQRDC3YSJT3DAVCNFSM6AAAAABC25KMHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZQGQ2TONRWGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

from ionide-vscode-fsharp.

MangelMaxime commented on September 18, 2024

We don't spawn the terminal ourself, it is given to use by VSCode API.

ionide-vscode-fsharp/src/Components/Fsi.fs

Lines 419 to 455 in 29205de

 let private start () = 

 promise { 

 let ctok = vscode.CancellationTokenSource.Create().token 

 let! profile = 

 match provider.provideTerminalProfile (ctok) with 

 | None -> promise.Return None 

 | Some work -> work |> Promise.ofMaybeThenable Some 

 let profile = 

 match profile with 

 | Some opts -> opts 

 | None -> 

 window.showErrorMessage ("Unable to spawn FSI") |> ignore 

 failwith "unable to spawn FSI" 

 // this coercion could be to either type - TerminalOptions _or_ ExtensionTerminalOptions 

 // we don't actually care here so I picked the first Case on the U2 here. 

 let terminal = window.createTerminal (!!profile.options: TerminalOptions) 

 // Wait for the new terminal to be ready 

 let! newTerminal = 

 Promise.create (fun resolve reject -> 

 window.onDidOpenTerminal.Invoke(fun (terminal: Terminal) -> 

 if terminal.name = fsiNetCoreName || terminal.name = fsiNetFrameworkName then 

 // It can happens that a new terminal is created before the old one is closed 

 // In that case, we need to close the old one first 

 // This case occures when user invoke "FSI: Start" commands with an existing FSI terminal 

 match fsiTerminal with 

 | Some fsiOutput -> fsiOutput.dispose () 

 | None -> () 

 // Return the new terminal 

 resolve terminal 

 None) 

 |> ignore)

I don't know if there any arguments or configuration can be made for it.

from ionide-vscode-fsharp.

eatobin commented on September 18, 2024

@MangelMaxime Thank you. I'll just live with it. :-)

from ionide-vscode-fsharp.

eatobin commented on September 18, 2024

Bye.

from ionide-vscode-fsharp.

Read ~/.bashrc When Running A .fsx Script? about ionide-vscode-fsharp HOT 7 CLOSED

Comments (7)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	let private start () =
	promise {
	let ctok = vscode.CancellationTokenSource.Create().token

	let! profile =
	match provider.provideTerminalProfile (ctok) with
	\| None -> promise.Return None
	\| Some work -> work \|> Promise.ofMaybeThenable Some

	let profile =
	match profile with
	\| Some opts -> opts
	\| None ->
	window.showErrorMessage ("Unable to spawn FSI") \|> ignore

	failwith "unable to spawn FSI"
	// this coercion could be to either type - TerminalOptions _or_ ExtensionTerminalOptions
	// we don't actually care here so I picked the first Case on the U2 here.
	let terminal = window.createTerminal (!!profile.options: TerminalOptions)

	// Wait for the new terminal to be ready
	let! newTerminal =
	Promise.create (fun resolve reject ->
	window.onDidOpenTerminal.Invoke(fun (terminal: Terminal) ->
	if terminal.name = fsiNetCoreName \|\| terminal.name = fsiNetFrameworkName then
	// It can happens that a new terminal is created before the old one is closed
	// In that case, we need to close the old one first
	// This case occures when user invoke "FSI: Start" commands with an existing FSI terminal
	match fsiTerminal with
	\| Some fsiOutput -> fsiOutput.dispose ()
	\| None -> ()

	// Return the new terminal
	resolve terminal

	None)
	\|> ignore)