Settings editor erases the symbolic link rather than following it #14679

Closed
opened 2026-01-31 04:16:41 +00:00 by claunia · 3 comments
Owner

Originally created by @roflolilolmao on GitHub (Jul 25, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal Preview 1.10.1933.0

Other Software

Symbolic link created from my configuration repository with this command:

New-Item `
 -ItemType SymbolicLink `
 -Force `
 -Path "$env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json" `
 -Target ./terminal/settings.json

Steps to reproduce

  1. Create a symlink to the settings file;
  2. open the settings in the terminal and hit the save button.

State after 1.:

image

State after 2.:

image

Expected Behavior

The settings editor follows the symbolic link and saves the file in my configuration repository.

Actual Behavior

The settings editor erases the symbolic link.

Originally created by @roflolilolmao on GitHub (Jul 25, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal Preview 1.10.1933.0 ### Other Software Symbolic link created from my configuration repository with this command: ```powershell New-Item ` -ItemType SymbolicLink ` -Force ` -Path "$env:LOCALAPPDATA\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json" ` -Target ./terminal/settings.json ``` ### Steps to reproduce 1. Create a symlink to the settings file; 2. open the settings in the terminal and hit the save button. State after 1.: ![image](https://user-images.githubusercontent.com/9419517/126890858-95c9f7ed-3cfc-472e-9ead-15bbda7f94f2.png) State after 2.: ![image](https://user-images.githubusercontent.com/9419517/126890825-0bba6e1d-2f07-49a3-917b-c9e54f2f4b83.png) ### Expected Behavior The settings editor follows the symbolic link and saves the file in my configuration repository. ### Actual Behavior The settings editor erases the symbolic link.
Author
Owner

@Diablo-D3 commented on GitHub (Aug 1, 2021):

This breaks any use case that involves a typical dotfiles repo setup; ergo, I've been bitten by this at least once.

@Diablo-D3 commented on GitHub (Aug 1, 2021): This breaks any use case that involves a typical dotfiles repo setup; ergo, I've been bitten by this at least once.
Author
Owner

@ghost commented on GitHub (Aug 31, 2021):

:tada:This issue was addressed in #10908, which has now been successfully released as Windows Terminal Preview v1.10.2383.0.🎉

Handy links:

@ghost commented on GitHub (Aug 31, 2021): :tada:This issue was addressed in #10908, which has now been successfully released as `Windows Terminal Preview v1.10.2383.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.10.2383.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Author
Owner

@ghost commented on GitHub (Aug 31, 2021):

:tada:This issue was addressed in #10908, which has now been successfully released as Windows Terminal Preview v1.11.2421.0.🎉

Handy links:

@ghost commented on GitHub (Aug 31, 2021): :tada:This issue was addressed in #10908, which has now been successfully released as `Windows Terminal Preview v1.11.2421.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.11.2421.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14679