Hi ! I opened a few days ago a new thread about a supposed malfunction of op.exe under win7. I received the message "waiting for moderation".
And my thread still did not appear...
But since then, I saw other threads appeared...
So, how long is moderation waiting time ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
although everybody is allowed to post, in your case there has been some kind of malfunction; I got a moderation request and I approved it, but the message has been deleted by the system (at the moment I saw it in the forum, but it's not there any more).
Anyways, I was looking at the issue, and it's related to the parsing of command line options by getopt().
It's a really strange bug, as all other options are accepted; I'm trying to solve it.
In the meanwhile you can use option -save instead of -s
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It turns out that getopt_long_only() is sensible to the order of declaration of options in the option array.
In op.c find:
{"save", required_argument, 0, 's'},
{"s", required_argument, 0, 's'},
If you invert these two lines it works.
Really strange, I have no idea why it does so.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Look
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi ! I opened a few days ago a new thread about a supposed malfunction of op.exe under win7. I received the message "waiting for moderation".
And my thread still did not appear...
But since then, I saw other threads appeared...
So, how long is moderation waiting time ?
Hi,
although everybody is allowed to post, in your case there has been some kind of malfunction; I got a moderation request and I approved it, but the message has been deleted by the system (at the moment I saw it in the forum, but it's not there any more).
Anyways, I was looking at the issue, and it's related to the parsing of command line options by getopt().
It's a really strange bug, as all other options are accepted; I'm trying to solve it.
In the meanwhile you can use option -save instead of -s
It turns out that getopt_long_only() is sensible to the order of declaration of options in the option array.
In op.c find:
{"save", required_argument, 0, 's'},
{"s", required_argument, 0, 's'},
If you invert these two lines it works.
Really strange, I have no idea why it does so.