/timestamp bug? - mIRC Discussion Forums

I'm not sure if this is a bug or what but when using /timestamp it doesn't update the mirc.ini.

1,1,1,0,0,0,9999,0,0,0,1,1,1024,1,1,99,60,0,0,0,2,1,1,2,0,5000,1,5,0,0,3,0,1,1,0,0,0

Apparently 1 meaning it's turned on, 0 being turned off.

Excuse the mess:

Code:

alias tstamp {
  .timestamp off
  saveini mirc.ini
  .timestamp on
  echo -a 4Not saved: $readini(mirc.ini, options, n4), 12, 44)
  saveini mirc.ini
  echo -a 4Saved: $readini(mirc.ini, options, n4), 12, 44)
  .timestamp off
}

Here's an example of the behavior.

Basically I'm saving it before I turn it on, when it's turned on I get:

Not saved: 1,1,1,0,0,0,9999,0,0,0,1,0,1024,1,1,99,60,0,0,0,2,1,1,2,0,5000,1,5,0,0,3,0,1,1,0,0,0 12, 44)

Then when it is saved I get:

Saved: 1,1,1,0,0,0,9999,0,0,0,1,1,1024,1,1,99,60,0,0,0,2,1,1,2,0,5000,1,5,0,0,3,0,1,1,0,0,0 12, 44)

Any idea what's going on?

See here.

So basically I'd need to re-alias the commands and saveini after it? Otherwise it'd be quite bothersome to issue saveini every time I use a command.