Hello Wilfred,

On Tuesday January 26 2016 15:40, you wrote to me:

 MvdV>> binkd -nP binkd.cfg

 MvdV>> While it is good that binkd can be started with an alternate
 MvdV>> configuration, it would save me a lot of typing if binkd.cfg in
 MvdV>> the current directory would be the default.

 WV> Maybe it could use the same configuration file as the already active
 WV> binkd instance by default.

I had to read that several times to see what you meant. The concept is new to
me.

 WV> That would work better with current practice on other OS's.

It assumes that there is an "already active binkd" to start with. In my example
that would be the case, but that is just an example. Also, I do not know if
there is a practical way to find out if there is an „lready active binkd" and
if so what config file it uses.

 WV> On linux it would be unlikely that the configfile would be in the
 WV> current directory for instance.

In DOS and Windows this was/is more or less a standard. Although some
applications assume the default config file to reside in the same direrctory as
the .exe.

 WV> And you could of course create a batch file on your system for this
 WV> function! ;)

I know, but I do not like to contaminate my system with many small batch files
that I can't remember what they all exactly do anyway. For me that works only
for batch files that I use VERY often. And I am not asking it for just /this/
function.

When I started using binkd one of the first things that did strike me as odd
(and akward), is that it has no default for the config file. Binkd was the
first application (and so far the only) on my system that requires the config
file to always be specified explicitly in the command line.

Every other application I have ever used and that can use more than one config
file has a default. Except binkd...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111