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

No copy path for (non-workspace) file #192266

Closed
jrieken opened this issue Sep 6, 2023 · 6 comments · Fixed by #193781
Closed

No copy path for (non-workspace) file #192266

jrieken opened this issue Sep 6, 2023 · 6 comments · Fixed by #193781
Assignees
Labels
insiders-released Patch has been released in VS Code Insiders output Output channel system issues

Comments

@jrieken
Copy link
Member

jrieken commented Sep 6, 2023

  • opened a log file
  • missing reveal in finder
  • missing copy path
Screenshot 2023-09-06 at 09 19 10
@bpasero bpasero assigned sandy081 and unassigned bpasero Sep 6, 2023
@bpasero bpasero added the output Output channel system issues label Sep 6, 2023
@bpasero
Copy link
Member

bpasero commented Sep 6, 2023

Sandy can you check, I think this came in from #40575. I wonder why we don't just open the file on disk and why this needs a custom log viewer. We can mark the editor as readonly.

@jrieken
Copy link
Member Author

jrieken commented Sep 6, 2023

also related to #192271 - the lack of these actions make it really hard to attach the sync-log to an issue

@sandy081
Copy link
Member

sandy081 commented Sep 6, 2023

Yeah, this is opened as log viewer to make it readonly. If we can mark readonly for normal files, then we do not need this spl log viewer.

@sandy081 sandy081 added this to the September 2023 milestone Sep 6, 2023
@bpasero
Copy link
Member

bpasero commented Sep 6, 2023

@sandy081 I think there are 2 options here:

  • make the setting files.readonlyInclude dynamic by adding the logs folder by default
  • ad-hoc configure the logs folder or logs file to open as readonly via the new IFilesConfigurationService.updateReadonly method

I think I would go with the second choice because that is quite straightforward.

@sandy081
Copy link
Member

Adopted to ad-hoc readonly state change, but it is allowing user to write into the file

image

Is it possible to prevent that? I know user can open the file directly from the folder and can edit, but I would like to prevent this action when opened using the action in output

sandy081 added a commit that referenced this issue Sep 22, 2023
sandy081 added a commit that referenced this issue Sep 22, 2023
@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label Sep 22, 2023
@bpasero
Copy link
Member

bpasero commented Sep 22, 2023

currently not, but I don't think its a big deal

@VSCodeTriageBot VSCodeTriageBot added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Sep 25, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
insiders-released Patch has been released in VS Code Insiders output Output channel system issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants