weidu.cfg - continued from SHS

[the bigg]

Original posts: http://www.shsforums.net/index.php?s=&showtopic=43523&view=findpost&p=469923

summary:
weidu --save-component-names reprints weidu.log with the mod names
weidu --safe-exit will update weidu.log before beginning each component installation to ensure that termination of the WeiDU process doesn't leave the game in an inconistent state.

{game}/weidu.cfg will contain default command-line parameters and other similar settings. Example:

Code:

COMMAND_LINE "--skip-at-view" "--quick-log" "--language" "0"

This also needs switches like --force-at-view, --no-quick-log to restore default behavior if it was altered by weidu.cfg.

Reply to Miloch's latest post:

WeiDU.cfg is per-directory (users of noble operating systems can also use ~/.WeiDUrc). Regarding languages, would the following make sense?

Code:

PARAMETER "Language" ".*english.*"
PARAMETER "LanguageMode" "RegexpCaseInsensitive"

[devSin]

Assuming you never auto-generate {Game}/WeiDU.cfg (or only touch it), why not just --no-conf to shut it up instead of having to negate everything that might be in the config? I could see something like this being useful, but how annoying for those times when I actually have to use WeiDU "for real" (i.e., something other than yet another endless test run of crap I'll never, ever finish).

I don't think local config really addresses Miloch's concern (I want one COMMAND_LINE to be used when installing, but I want it ignored or a different COMMAND_LINE when uninstalling). "Local" (per-user) .cfg actually seems kind of useless (I mean, really, come on); what you really want is per-mod, if you could figure out a way to derive a unique name to give to whatever command is being run (likely, "MyMod.TP2").

For that matter, what occurs if I'm using WeiDU this one time to output some Ds (*.DLG --out ~/Desktop) or to compile a BAF (MyMod.BAF --out override)? Does the .cfg chime in and try to add all its useless arguments to every single invocation of WeiDU if I happen to be sitting in the game directory (which you almost always would)?

Am I missing something, or basically, this feature is only useful if the only thing I do is install TP2s all day every day?

[the bigg]

Am I missing something, or basically, this feature is only useful if the only thing I do is install TP2s all day every day?

The latter. Though it must be noted that --skip-at-view and the like will (hopefully) have no effect when using the other 30000 command line features, and that only Miloch would use this anyway 

--no-cfg should be easy enough to add; I can also make it so that weidu.cfg is only read when argv[0] is ^setup-.* and/or argv[] contains a .*\.tp2$ argument.

[devSin]

--no-cfg should be easy enough to add; I can also make it so that weidu.cfg is only read when argv[0] is ^setup-.* and/or argv[] contains a .*\.tp2$ argument.

I would stick with just the latter if argv[0] is the command (if you're smart enough to have WeiDU.cfg, you're smart enough to have some other non-Setup-* executable name).

Or you could have a special attribute (COMMAND_LINE_TP2 or whatever) in the args file to have it apply to only .*\.tp2\b (and COMMAND_LINE a generic "always add").

But really, call me dubious on the use of this over some simple (shell, batch, blah) script...

[the bigg]

But really, call me dubious on the use of this over some simple (shell, batch, blah) script...

Hurr Durr doubleclick

[the bigg]

Feature dropped - the requester doesn't respond for additional comments, and the argv[] parsing library can't handle this type of feature without significant a significant rewrite (it can be called exactly once per program, can only work with the original argv[]).

[Miloch]

Feature dropped - the requester doesn't respond for additional comments

If you're talking about me, I didn't see the need for additional comments. Unless you're talking about the language feature, in which case what you suggested should work. My original suggestion was basically just "is it possible to skip README/LANGUAGE queries if a component is already installed?" (but to display them if a component of the mod is not already installed).

[the bigg]

Oh, right, doing specifically that should be easy 

Do you want to block AT_* ~VIEW~ as well or just the README query?

[Miloch]

Do you want to block AT_* ~VIEW~ as well or just the README query?

I only use the latter, but both would probably be best if it's just as easy to do so.

[the bigg]

Actually blocking AT_* VIEW causes problems with Refinements (which opens a different readme file per component), so you'll have to --skip-at-view if you really need it.

README/LANGUAGE blocking gitted BTW.

[Miloch]

README/LANGUAGE blocking gitted BTW.

Cheers.

[Miloch]

This seems to be a bit glitchy in v213. To replicate, pick a mod with several components. Install it for the first time. As expected, you get prompted for the readme. Now uninstall everything, then reinstall. When I did this (even after exiting the prompt) I did not get prompted for the readme, even though there were no components installed. However, when I installed everything again then uninstalled again, I got prompted for the readme during the *uninstall*. When installing a third time with no components present, I still didn't get the readme. Shouldn't it just be able to read uncommented entries in the WeiDU.log to see if anything's installed?

[the bigg]

Will take a look at it.

[the bigg]

Code:

if any_component_installed()
  show_readme_prompt()

It was written as clearly as that, and it took me two hours (in multiple tries) to notice the missing NOT.