Open DerekNonGeneric opened 7 months ago
the missing pieces off the top of my head:
postCreateCommand
-> ./_tools/devenv/post-create.fish
🏗🚮:rm post-create.fish
This file was somewhat of a rough draft; much of which should not be taken seriously as should likely take place in the creation of the container image. We will now have removed it [temporarily] not to be replaced unnecessarily.
Signed-off-by: Derek Lewis dereknongeneric@open.inf.is
—https://github.com/OpenINF/.github/commit/bf66077b254ddd8f251d51827fbc3b0e88eb425f
fish_config theme choose none
mainly want to be sure we modernize the:
…of course, vscode config is a necessary evil here; i am going to try to be minimal unless we can centralize the vscode config in org-level dotfile repo for easily sharing ❤️❤️
[…] a necessary evil here; […] centralize the vscode config […] for easily sharing ❤️❤️
already tough enough keeping two projects' vscode workspace settings somewhat aligned and current; a dope solution has presented itself:
Note: Workspace and Workspace Folder configurations contain
launch
andtasks
settings. Their basename will be part of the section identifier. The following snippets show how to retrieve all configurations fromlaunch.json
:
// launch.json configuration
const config = workspace.getConfiguration(
'launch',
vscode.workspace.workspaceFolders[0].uri
);
// retrieve values
const values = config.get('configurations');
🔗 https://code.visualstudio.com/api/references/vscode-api#WorkspaceConfiguration
💯💯💯
The concept of a workspace enables VS Code to:
You may see the terms "folder" and "workspace" used interchangeably in VS Code documentation, issues, and community discussions. Think of a workspace as the root of a project with extra VS Code knowledge and capabilities.
🥇 Workspace tasks and launch configurations — sounds like project bootstrapping temptation (must've been main reason) 🤔 — settles it for me gonna knock 'em out & also might wanna look into the fish env stuff (will hopefully know more soon)
also might wanna look into the fish env stuff (will hopefully know more soon)
mercky, mercky, but; we even own the stuff (do we like it):
fish env stuff
follow-up to https://github.com/OpenINF/docker-fisher/issues/53