Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating shortcut for Sublime Merge #2658

Closed
shakeel opened this issue Oct 10, 2018 · 4 comments
Closed

Creating shortcut for Sublime Merge #2658

shakeel opened this issue Oct 10, 2018 · 4 comments

Comments

@shakeel
Copy link

shakeel commented Oct 10, 2018

scoop update sublime-merge results in the following Move-Item error when creating a shortcut.

Updating` 'sublime-merge' (1065 -> 1070)
Uninstalling 'sublime-merge' (1065)
Removing shim for 'smerge'.
Unlinking ~\scoop\apps\sublime-merge\current
Installing 'sublime-merge' (1070) [64bit]
sublime_merge_build_1070_x64.zip (26.5 MB) [========================================================] 100%
Checking hash of sublime_merge_build_1070_x64.zip ... ok.
Extracting sublime_merge_build_1070_x64.zip ... done.
Linking ~\scoop\apps\sublime-merge\current => ~\scoop\apps\sublime-merge\1070
Creating shim for 'smerge'.
Creating shortcut for Sublime Merge (sublime_merge.exe)
Persisting Data
Move-Item : Cannot create a file when that file already exists.
At C:\Users\USSHMAH\scoop\apps\scoop\current\lib\install.ps1:1239 char:21
+                     Move-Item $source $target
+                     ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Users\USSHMA...ge\current\Data:DirectoryInfo) [Move-Item], IOE
   xception
    + FullyQualifiedErrorId : MoveDirectoryItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand

Cannot create a file when that file already exists.
'sublime-merge' (1070) was installed successfully!
@Ash258
Copy link
Contributor

Ash258 commented Oct 10, 2018

It's not when creating shortcuts, but when persisting data.

@shakeel
Copy link
Author

shakeel commented Oct 10, 2018

Oops I guess the title of the issue needs to be changed.

@Ash258
Copy link
Contributor

Ash258 commented Apr 18, 2019

This should be gone after #2897

@rasa
Copy link
Member

rasa commented Oct 20, 2020

Implemented

@rasa rasa closed this as completed Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants