[Gtkwave-users] GTKwave bug with user tcl scripts passed by -S or --script

[Racer N. <dki...@gm...>]

Hello,

I am a new user to Source Forge, so I don't yet know how to use it. I made
an account to report this bug for GTKWave. I am using VUnit with
GHDL/GTKWave and am adding the following functionality for VUnit (
https://github.com/VUnit/vunit/issues/458). Anyways, what that feature
request on VUnit boils downto is that GTKWave doesn't allow spaces in path
names for the -S flag for running user .tcl scripts. Whether I use absolute
or relative paths for adding scripts to GTKWave to run, it is never safe
for me or many users to assume the path will not have spaces, thus why I
want to open a bug on this issue. When I try to use the -S flag with a file
whose path name has a space in it, I see this TCL error:

GTKWave Analyzer v3.3.98 (w)1999-2019 BSI

[0] start time.
[104500000] end time.
GTKWAVE | Executing Tcl script 'C:\Users\Glen
Nicholls\Desktop\vunit\examples\vhdl\axi_dma\gtkSource.tcl'
GTKWAVE | wrong # args: should be "source ?-encoding name? fileName"

I tried every combination of using quotes along with space delimiters in
path names, but nothing is allowing however GTKWave passes user TCL scripts
to TCL to run. I understand the issue with spaces in directory/path names,
but where I'm using GTKWave, I don't have a choice unless I want to spend
days fixing an issue that doesn't affect any other part of our workflow.