starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Icon and background image fields should reference parent process directory (if checked) -- Wildcards disabled #17252

New Issue
Closed
opened 2026-01-31 05:36:45 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 05:36:45 +00:00
Owner
Copy Link

Originally created by @0xJonasDev on GitHub (Apr 16, 2022).

Windows Terminal version

1.12.10732.0

Windows build number

19043.1645

Other Software

No response

Steps to reproduce

Forgive me if this has been addressed already somewhere else, but I realized that when Use parent process directory is checked, Command line is able to run testrun.bat which is located in the parent process directory but Icon is unable to access test_icon.ico which is also located in the parent process directory. Is there a reference (such as %USERPROFILE% is to the home folder) to point to the parent process directory so that I can access the test_icon.ico file? Something along the lines of %CD%\test_icon.ico(%CD% is a windows environment variable which outputs current directory path. See source but terminal does not recognize %CD%. Any idea how to deal with this situation? The intent here is to have wt dynamically locate whatever test_icon.ico file that is present in the current parent process directory for the icon or background image settings.

image

Expected Behavior

test_icon.ico in the Icon field, Loads the .ico file as the icon. Same goes for the background image in the Appearance tab.

Actual Behavior

I get the following error message below...

image

Originally created by @0xJonasDev on GitHub (Apr 16, 2022). ### Windows Terminal version 1.12.10732.0 ### Windows build number 19043.1645 ### Other Software _No response_ ### Steps to reproduce Forgive me if this has been addressed already somewhere else, but I realized that when ```Use parent process directory``` is checked, ```Command line``` is able to run ```testrun.bat``` which is located in the parent process directory but ```Icon``` is unable to access ```test_icon.ico``` which is also located in the parent process directory. Is there a reference (such as ```%USERPROFILE%``` is to the home folder) to point to the parent process directory so that I can access the ```test_icon.ico``` file? Something along the lines of ```%CD%\test_icon.ico```(%CD% is a windows environment variable which outputs current directory path. See [source](https://pureinfotech.com/list-environment-variables-windows-10/) but terminal does not recognize %CD%. Any idea how to deal with this situation? The intent here is to have wt dynamically locate whatever ```test_icon.ico``` file that is present in the current parent process directory for the icon or background image settings. ![image](https://user-images.githubusercontent.com/72827311/163658623-9fb420d2-9988-455b-88cb-3e3e0c0c12f8.png) ### Expected Behavior ```test_icon.ico``` in the ```Icon``` field, Loads the .ico file as the icon. Same goes for the ```background image``` in the ```Appearance``` tab. ### Actual Behavior I get the following error message below... ![image](https://user-images.githubusercontent.com/72827311/163658758-7804005a-a519-4c36-a74a-9d7ca544b11e.png)
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:36:46 +00:00
claunia commented 2026-01-31 05:36:47 +00:00
Author
Owner
Copy Link

@0xJonasDev commented on GitHub (Apr 23, 2022):

Found a solution in this article

In the Icon and Background fields, you can reference your files relative to your current working directory:

%__CD__%\relative_path_to_icon_file. In my case it would be %__CD__%\graphics\app_bckgnd.jpg.

@0xJonasDev commented on GitHub (Apr 23, 2022): Found a solution in this [article][1] In the ```Icon``` and ```Background``` fields, you can reference your files relative to your current working directory: ```%__CD__%\relative_path_to_icon_file```. In my case it would be ```%__CD__%\graphics\app_bckgnd.jpg```. [1]: https://weblog.west-wind.com/posts/2019/Sep/03/Programmatically-Opening-Windows-Terminal-in-a-Specific-Folder
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17252
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?