vcs

No need for description

-I does use it

Originally reported by Homer S

No need for description

Parsing of the “-U” option (optional argument) is incorrect, it always receives an argument (empty if none provided) which must be shifted manually. Currently it’s only shifted if provided explicitly.

“–fullname” is not affected since it doesn’t take any arguments.

No need for description

font_filename is ignored in 1.12

An alternative in the form of (boolean) nonlatin_filenames or similar should be added.

mplayer: FPS1

i.e.:
ID_VIDEO_CODEC=fffraps
ID_VIDEO_FORMAT=FPS1

ffmpeg: fraps

i.e.:
Stream #0.0: Video: fraps, yuvj420p, 1680x1050, 30 fps, 30 tbr, 30 tbn, 30 tbc

ffmpeg: hevc

i.e.:
Stream #0:0[0x12d]: Video: hevc (Main) (HEVC / 0×43564548), yuv420p(tv), 3840×2160, 150 tbr, 90k tbn, 90k tbc Stream #0:0: Video: hevc, yuv420p(tv), 3840×2160, 25 fps, 25 tbr, 1200k tbn, 25 tbc

Samples: http://www.elecard.com/en/download/videos.html

See http://p.outlyer.net/dox/vcs:extended_mode

No need for description

Configuration options that will trigger a change of all fonts, background and foreground settings respectively

No need for description

With the introduction of profiles vcs will need directories to place them.

Using vcs-nix might be safer since vcs is too short and too meaningful (Version Control System) to hijack it safely.

Candidates:

• Site-wide: /usr/share/vcs/profiles, /usr/local/share/vcs/profiles/
• User-local: ~/.vcs/profiles/

Implementation notes:

• Reserved namespace: :<WHATEVER>
• Built-in profiles won’t use reserved names
• System profiles will always take precedence over built-in profiles
• ~ profiles take precedence over site (/usr and /usr/local) profiles
• /usr/local takes precedence over /usr. Both are searched
• No such thing as a default profile (this would be redundant to configuration files)
• Profiles can’t depend/include/load other profiles
• Profile names are reflected in file names

Specific files will be loadable with --config

Markup

With the introduction of ~/.vcs/ (or ~/.vcs-nix/) it makes sense moving local configurations there. The older ~/.vcs.conf will still be accepted.

Load order:

1. /etc/vcs.conf
2. ~/.vcs.conf
3. ~/.vcs/vcs.conf
4. ./vcs.conf

Allow command-line overrides (changing internal variables from the command-line).

.

Reported by DanC

https://outlyer.net/2014-05-18:vcs-1_13_2-released/comment-page-1/#comment-20390:

A great utilty... I’ve been using this for a couple of years now (it runs every night as a cron job).

I’ve been looking at cleaning up the output that cron captures from each of its commands and stores as a system email.

I’ve enabled the -Wc option to prevent coloured output. Mostly this works except near the start of the script when it says:
Settings from /home/danc/.vcs/vcs.conf:
bg_heading
This is still shown in green. Bug?

Currently the colour only stops after the option is found.