TigerVNC/tigervnc

Configuration file detection is not evident

Open

#956 opened on Feb 6, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (1,176 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (7,396 stars)
PR merge metrics
 (Avg merge 95d 10h) (4 merged PRs in 30d)

Description

When I start vncviewer from command line I can use a x.tigervnc file to specify the connection parameters. This file can be created from vncviewer directly ('Save As' button). The problem is that if I give just myfile.tigervnc as command-line option - it is considered as server name (and failed to resolve). Digging in the code I found the way to use a configuration file as command-line option - it should be ./myfile.tigervnc I think it is not evident and can be confusing ;)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Research direction
Look at the command line argument parsing in the VNC viewer code to understand how configuration file paths are distinguished from server names.
Tech stack
cpp
Domain
desktopcli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65