On Thursday, May 17, 2018 08:51:34 Kagamin via Digitalmars-d wrote:
> On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
>
> wrote:
> > This way one can unzip over a previous install without losing
> > the original sc.ini file.
>
> Also that's not a correct way to update, you should
On Friday, 18 May 2018 at 00:05:49 UTC, IntegratedDimensions
wrote:
This may be a suitable solution. While it has some overhead and
pollutes the environment, it at least offers a working
alternative unlike other (non)"solutions".
It would be better if HOME wasn't so general since other
On Thursday, 17 May 2018 at 08:53:06 UTC, Vladimir Panteleev
wrote:
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
Any custom modification swill overwrite the original sc.ini
file. The compiler should copy(rename) or create the file on
demand when it is ran and does not
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
This way one can unzip over a previous install without losing
the original sc.ini file.
Also that's not a correct way to update, you should unzip into an
empty folder or stray files can be left from the previous
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
Any custom modification swill overwrite the original sc.ini
file. The compiler should copy(rename) or create the file on
demand when it is ran and does not exist in the same path as
the compiler.
Not detracting from your
On Thursday, 17 May 2018 at 07:38:50 UTC, IntegratedDimensions
wrote:
This way one can unzip over a previous install without losing
the original sc.ini file. It is a pain to have to remember to
back it up every time(given if one updates slowly).
You only need to back it up once.
That or
Any custom modification swill overwrite the original sc.ini file.
The compiler should copy(rename) or create the file on demand
when it is ran and does not exist in the same path as the
compiler.
This way one can unzip over a previous install without losing the
original sc.ini file. It is a
