🐋🏗⚡ set grimesai-salvage-tex:lunar bootstrappable into devcontainer

[DerekNonGeneric]

No description provided.

[DerekNonGeneric]

follow-up to OpenINF/docker-fisher#53

[DerekNonGeneric]

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 [email protected]

—OpenINF/.github@bf66077

post-create.fish:

fish_config theme choose none

mainly want to be sure we modernize the:

• PATH variable-appending via fish function
• local, global, univ. - variable-setting via fish function

…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 ❤️❤️

[DerekNonGeneric]

[…] 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:

• Profiles - Partial Profiles
• Share Profiles
• Compat via Omission

Note: Workspace and Workspace Folder configurations contain launch and tasks settings. Their basename will be part of the section identifier. The following snippets show how to retrieve all configurations from launch.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

💯💯💯

[DerekNonGeneric]

The concept of a workspace enables VS Code to:

• Configure settings that only apply to a specific folder or folders but not others.
• Persist task and debugger launch configurations that are only valid in the context of that workspace.
• Store and restore UI state associated with that workspace (for example, the files that are opened).
• Selectively enable or disable extensions only for that workspace.

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.

—https://code.visualstudio.com/docs/editor/workspaces

[DerekNonGeneric]

🥇 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)

[DerekNonGeneric]

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

🔗 https://github.com/OpenINF/openinf-autoenvstack