On 07.12.2016 07:27, Bruno Jesus wrote:
I have used this in some situations to check how network enabled applications react to not having network access. IMO it is useful but if nobody cares I don't mind it being rejected.
I like it. Can you document it in a manpage?
Greets jre
On Wednesday, December 7, 2016, Jens Reyer jre.winesim@gmail.com wrote:
On 07.12.2016 07:27, Bruno Jesus wrote:
I have used this in some situations to check how network enabled
applications react to not having network access. IMO it is useful but if nobody cares I don't mind it being rejected.
I like it. Can you document it in a manpage?
Thanks for the reply, I can add it in the wiki as other environment variables. Not sure if others are in the manpage (replying from mobile).
In other words if the patch is accepted I would certainly document it anywhere necessary.
Best wishes, Bruno
On 07.12.2016 14:54, Bruno Jesus wrote:
On Wednesday, December 7, 2016, Jens Reyer jre.winesim@gmail.com wrote:
On 07.12.2016 07:27, Bruno Jesus wrote:
I have used this in some situations to check how network enabled
applications react to not having network access. IMO it is useful but if nobody cares I don't mind it being rejected.
I like it. Can you document it in a manpage?
Thanks for the reply, I can add it in the wiki as other environment variables. Not sure if others are in the manpage (replying from mobile).
In other words if the patch is accepted I would certainly document it anywhere necessary.
Great, wiki is nice. However I prefer putting documentation in the source and thus shipping it to the users. On Debian I'm used to first look in the manpages.
In a quick search I found these documented in the manpages:
wineserver: WINEPREFIX WINESERVER
wine: WINEPREFIX WINESERVER WINELOADER WINEDEBUG WINEDLLPATH WINEDLLOVERRIDES WINEARCH DISPLAY AUDIODEV MIXERDEV MIDIDEV
winedebug: WINE_GDB
Greets jre
-
Bruno Jesus -
Jens Reyer