![]() A profile can contain a single importDefaultsFromLnk field and nothing else, and all settings will come from the shell link and its NT_CONSOLE_PROPS and NT_FE_CONSOLE_PROPS data blocks (except those that don't make sense for Terminal, of course, like NT_CONSOLE_PROPS::dwWindowOrigin) the name field would default to the file's display name ( IShellItem::GetDisplayName), so that it would automatically hide the extension and/or load a localized description that might be present. I propose a new key for profile dictionaries, let's call it " importDefaultsFromLnk", which can specify a path to a shell link (.lnk) file. Until Terminal has a UI for creating and editing profiles, this feature will simply involve changes to the schema of profiles.json Terminal should do it automatically, either on a shortcut-by-shortcut basis, or even better letting you dynamically import a whole directory of shortcuts Proposed technical implementation details It's tedious and error prone to copy settings from these shortcuts. "圆4 Native Tools Command Prompt for VS 2019"). install shortcuts that open command prompts with a pre-configured environment (e.g. Development environments, such as Visual Studio, SDKs, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |