Problem accessing cloud behind a proxy

Lubomir I. Ivanov neolit123 at gmail.com
Wed Nov 15 07:21:26 PST 2017


On 15 November 2017 at 17:20, Dirk Hohndel <dirk at hohndel.org> wrote:
> On Wed, Nov 15, 2017 at 05:08:49PM +0200, Lubomir I. Ivanov wrote:
>> On 15 November 2017 at 17:03, Dirk Hohndel <dirk at hohndel.org> wrote:
>> > On Wed, Nov 15, 2017 at 04:36:25PM +0200, Lubomir I. Ivanov wrote:
>> >> On 15 November 2017 at 16:27, Dirk Hohndel <dirk at hohndel.org> wrote:
>> >> >
>> >> > With Lubomir's changes there are two ways to get the console output:
>> >> >
>> >> > You can run from cmd.exe - then the output is shown on the screen, but not
>> >> > saved to the log files.
>> >> > Or you can run this by double clicking on the executable. Then the log
>> >> > output is saved to the two log files.
>> >> >
>> >>
>> >> something to note here, is that by default when the Subsurface.exe is
>> >> started from the desktop shortcut, the log files would remain mostly
>> >> empty because the executable does not receive any "-v" arguments.
>> >> so to see verbose output the user has to manually append the "-v"s in
>> >> the desktop shortcut <path-to-exe> field.
>> >
>> > Which makes me wonder... should we just use verbose=1 as default if
>> > started from the shortcut on Windows?
>> >
>>
>> i was implying the same question, in a way.
>> but then, what if the user needs to see something which requires more
>> verbose levels?
>> he/she has to append more "-v"s to the shortcut.
>>
>> would "1" suffice, by default?
>
> IIRC the higher levels give you detailed parsing info and similar
> extremely verbose information. I rarely see a reason to go there.
> So I think '1' is a reasonable default for this.
>

ok, sounds good.

lubomir
--


More information about the subsurface mailing list