Differences From Artifact [e8851d5c36]:
- File windows/window.c — part of check-in [e32793db99] at 2007-02-10 11:02:41 on branch trunk — Avoid launching a session from the Default Settings, even if they do represent a launchable session, unless the user can be construed to have really meant it. This means: - starting up PuTTY when the Default Settings are launchable still brings up the config box, and you have to hit Open to actually launch that session - double-clicking on Default Settings from the config box will load them but not launch them. On the other hand: - explicitly loading the Default Settings on the command line using `-load' _does_ still launch them. (user: simon size: 143193)
To Artifact [9d416f0baa]:
- File windows/window.c — part of check-in [dc0247bf7b] at 2007-02-16 12:44:07 on branch trunk — r7265 broke the legacy `putty @sessionname' construction, which I wouldn't care about except for the fact that it's still used to implement the Saved Sessions menu item in PuTTY and Pageant. (user: simon size: 143264)
| ︙ | ︙ | |||
393 394 395 396 397 398 399 400 401 402 403 404 405 406 |
while (i > 1 && isspace(p[i - 1]))
i--;
p[i] = '\0';
do_defaults(p + 1, &cfg);
if (!cfg_launchable(&cfg) && !do_config()) {
cleanup_exit(0);
}
} else if (*p == '&') {
/*
* An initial & means we've been given a command line
* containing the hex value of a HANDLE for a file
* mapping object, which we must then extract as a
* config.
*/
| > | 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 |
while (i > 1 && isspace(p[i - 1]))
i--;
p[i] = '\0';
do_defaults(p + 1, &cfg);
if (!cfg_launchable(&cfg) && !do_config()) {
cleanup_exit(0);
}
loaded_session = TRUE; /* allow it to be launched directly */
} else if (*p == '&') {
/*
* An initial & means we've been given a command line
* containing the hex value of a HANDLE for a file
* mapping object, which we must then extract as a
* config.
*/
|
| ︙ | ︙ |