Skip to content

Update TigerVNC documentation #463

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update TigerVNC documentation #463

wants to merge 1 commit into from

Conversation

fox8091
Copy link

@fox8091 fox8091 commented Mar 20, 2025

TigerVNC uses XDG Base Directory Specification paths as of PRs #1737 and #1760, update documentation to match.

Copy link
Contributor

@kamack38 kamack38 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be specified from what version the XDG Base Dir spec is supported.

"movable": false,
"help": "Currently unsupported.\n\n_Relevant issue:_ https://github.com/TigerVNC/tigervnc/issues/1195\n"
"movable": true,
"help": "Supported by default.\n\nNewer versions of tigervnc automatically create directories at correct locations, consult `man vncviewer` to see where to move files.\n**WARNING: Failure to move files to the correct location can result in locking out VNC access**"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"help": "Supported by default.\n\nNewer versions of tigervnc automatically create directories at correct locations, consult `man vncviewer` to see where to move files.\n**WARNING: Failure to move files to the correct location can result in locking out VNC access**"
"help": "Supported by default.\n\nAll versions above 1.14.0 will automatically create directories at correct locations, consult `man vncviewer` to see where to move files.\n**WARNING: Failure to move files to the correct location can result in locking out VNC access**"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know whether it should not be changed to 1.13.1, since the change was introduced in 1.14.0.

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

Successfully merging this pull request may close these issues.

2 participants