The kludgy syntax (superseded in v2.1.1.0) for the GLC command line options

[shriprem]

[ NOTE: The topic of this discussion was only relevant for the very much short-lived v2.1.0.0 Release. It has been rendered moot by the Consolidated GLC Command Line Options introduced in the v2.1.1.0 Release. ]

Reasons for the kludgy syntax (superseded in v2.1.1.0) for the -GLCx options

1. On the Notepad++ - Usage via the command prompt page, the multiple plural words in the description for the -z option lead you to think that a single -z is sufficient for the multiple plugin-specific options that follow it.
   
   The GotoLineCol plugin is able to scan and handle the -GLC options just fine without the -z option preceding each one of them. But the issue is with Notepad++; a bug probably. It considers any -GLC options lacking an immediately preceding -z as a filename and prompts whether to create a file with that name.
   

2. I did try merging the -z and -GLCx pairs into, say, the -zLCx format. The plugin was able to scan and handle the options just fine. But the issue was with Notepad++. It considered the -zLCx as a filename and prompted whether to create a file with that name.
   

3. I opted to precede each of GotoLineCol's command line options with the GLC prefix to avoid any conflicts with other plugins using single-lettered command line options. I am aware that there aren't that many NPP plugins that use command line options. But still.