26
VS Code
770 readers
31 users here now
founded 1 year ago
MODERATORS
27
28
29
30
Hi everyone, I'm trying to try out F# via FSI in VS Code (Windows 10)
I have Ionide for F# installed, and have used it before, but now every time I try to start it I get a message "FSI :Start resulted in an error", it goes on to helpfully report "the option has no value".
dotnet is in path, dotnet works great. FSI? nothing.
I also have the .net workload installed for visual studio 2022 (if that matters).
I started up my Linux VM (KDE Neon) fired up vs codium and tried FSI Start...same error! So no tinkering in f# for me tonight. Does anyone have an idea what's happening, across two environments? Google is no help...
31
32
33
34
35
36
Here's an upcoming feature for those wanting to use multiple profiles in VSCode but don't enjoying micro managing settings across many different profiles. And good news: This feature is currently being developed!
The feature request is Extend from the Default Profile. The idea is to allow users to organize settings into various layers. Global settings in the default profile. Maybe python specific settings in a python profile. And then golang specific settings in a golang profile. Or however else you want to organize things! This will be a huge help when working with many different workspaces and languages which all need little adjustments.
This idea actually dates back all the way to November, 2016! While it has nearly 600 votes, nobody implemented the feature. Thankfully, the new feature (again, issue 156144 was requested about a year ago and was actually a part of the Iteration Plan for June 2023. Unfortunately, it wasn't completed in time (that's ok! Thanks devs!) and was pushed to the July 2023 iteration. Hopefully, we'll have this feature released soon.
If you're as excited as I am for this one, then vote for the feature with a thumbs up.
Yes, it's already in development but votes can make this feature a priority. You can also vote for specific implementation details too!
37
38
This is the first of a (hopefully) recurring series where we showcase extensions that are likely unknown to most users. Starting with patricklee.vsnotes!
Marketplace Description
VSNotes is a simple tool that takes care of the creation and management of plain text notes and harnesses the power of VS Code via the Command Palette.
Why I like it
VSNotes seems to be built for frequent note taking. E.g. Taking daily meeting notes and keeping them organized. There are quite a few alternative extensions like dendron.dendron that do this quite well but are much more complicated. I like VSNotes for its simplicity. It's easy to use.
More importantly, I don't want to create a large number of notes. I just want to manage a few organized files and have them accessible at all times. Here's a screenshot from my work laptop.
No date stamps. No tags. No subdirectories. Nice and simple. Having these notes embedded in VS Code gives me the expected benefits like markdown syntax and preview. But my favorite part is the Activity Bar icon (far right in my screenshot). These notes aren't stored in my active workspace. They can be but I choose to store these notes in ~/notes instead. This means that the files within that directory are globally available regardless of which workspace is active. If you work with many different repositories and workspaces, this is fantastic!
A few use cases
- Basic notes that are always open... duh. So you don't have to send yourself messages in Slack
- Commands.md: Some bash magic. Some kubectl favorites. Some fancy git commands. All copy/paste-able into the embedded terminal
- Diagram.d2: I manually set the file extension. Now I can preview terrastruct.d2 diagrams conveniently!
My Configuration
{
"vsnotes.defaultNotePath": "~/notes",
"vsnotes.defaultNoteTitle": "{title}.{ext}",
"vsnotes.noteTitleConvertSpaces": "-",
}
39
40