Startup error with v18

[prcek]

I installed v18 (the 64-bit version) and after importing my v17 settings it blows up in beautifier.ex offset 3693; the stack trace is attached below. When I dismiss the error box the VS window is blank (no menu, no nothing) and thus it's completely unusable. Any suggestions, anyone?

Thanks
PeterK

Invalid number argument
 Slick-C STACK TRACE ******************************
 Created on 7/22/2013 at 16:59:38 (617 ms)
 SlickEdit Version 18.0.0.13 Copyright 1988-2013 SlickEdit Inc.
 Edit module and type "st -f <offset>" to get the
 run-time error position

beautifier.ex 3693 beautifier:_common_language_def_sync(
   1:   ._typename()=VS-LANGUAGE-SETUP-OPTIONS
   1:   .mode-name=C/C++
   1:   .tabs=5 9
   1:   .margins=1 74 1
   1:   .keytab-name=c-keys
   1:   .word-wrap-style=1
   1:   .indent-with-tabs=0
   1:   .show-tabs=0
   1:   .indent-style=1
   1:   .word-chars=A-Za-z0-9_$
   1:   .lexer-name=cpp
   1:   .color-flags=1
   1:   .line-numbers-len=6
   1:   .TruncateLength=0
   1:   .bounds=0 0
   1:   .caps=0
   1:   .SoftWrap=0
   1:   .SoftWrapOnWord=0
   1:   .hex-mode=0
   1:   .line-numbers-flags=0
   2:   c
   p_window_id: 5
   p_object: OI_FORM
   p_name:
beautifier.ex 3760 _c_language_definition_sync(
   1:   ._typename()=VS-LANGUAGE-SETUP-OPTIONS
   1:   .mode-name=C/C++
   1:   .tabs=5 9
   1:   .margins=1 74 1
   1:   .keytab-name=c-keys
   1:   .word-wrap-style=1
   1:   .indent-with-tabs=0
   1:   .show-tabs=0
   1:   .indent-style=1
   1:   .word-chars=A-Za-z0-9_$
   1:   .lexer-name=cpp
   1:   .color-flags=1
   1:   .line-numbers-len=6
   1:   .TruncateLength=0
   1:   .bounds=0 0
   1:   .caps=0
   1:   .SoftWrap=0
   1:   .SoftWrapOnWord=0
   1:   .hex-mode=0
   1:   .line-numbers-flags=0
   p_window_id: 5
   p_object: OI_FORM
   p_name:
LanguageSettings.ex 2844 se.lang.api.LanguageSettings.getLanguageDefinitionOptions(c,
   2:   ._typename()=VS-LANGUAGE-SETUP-OPTIONS
   2:   .mode-name=C/C++
   2:   .tabs=5 9
   2:   .margins=1 74 1
   2:   .keytab-name=c-keys
   2:   .word-wrap-style=1
   2:   .indent-with-tabs=0
   2:   .show-tabs=0
   2:   .indent-style=1
   2:   .word-chars=A-Za-z0-9_$
   2:   .lexer-name=cpp
   2:   .color-flags=1
   2:   .line-numbers-len=6
   2:   .TruncateLength=0
   2:   .bounds=0 0
   2:   .caps=0
   2:   .SoftWrap=0
   2:   .SoftWrapOnWord=0
   2:   .hex-mode=0
   2:   .line-numbers-flags=0
   p_window_id: 5
   p_object: OI_FORM
   p_name:
stdcmds.ex 49381 _GetLanguageSetupOptions(c,
   2:   ._typename()=VS-LANGUAGE-SETUP-OPTIONS
   2:   .mode-name=C/C++
   2:   .tabs=5 9
   2:   .margins=1 74 1
   2:   .keytab-name=c-keys
   2:   .word-wrap-style=1
   2:   .indent-with-tabs=0
   2:   .show-tabs=0
   2:   .indent-style=1
   2:   .word-chars=A-Za-z0-9_$
   2:   .lexer-name=cpp
   2:   .color-flags=1
   2:   .line-numbers-len=6
   2:   .TruncateLength=0
   2:   .bounds=0 0
   2:   .caps=0
   2:   .SoftWrap=0
   2:   .SoftWrapOnWord=0
   2:   .hex-mode=0
   2:   .line-numbers-flags=0
   p_window_id: 5
   p_object: OI_FORM
   p_name:
setupext.ex 7986 _SetLanguageOption(c,SW,0)   p_window_id: 5   p_object: OI_FORM   p_name:
stdcmds.ex 49587 _SoftWrapSetAll(0,1)   p_window_id: 5   p_object: OI_FORM   p_name:
stdcmds.ex 49421 _SoftWrapUpdateAll(0,1)   p_window_id: 5   p_object: OI_FORM   p_name:
briefdef.ex 48 defmain()   p_window_id: 5   p_object: OI_FORM   p_name:
emulate.ex 1332 emulate:change_config(BRIEF,,briefdef.ex,brief-keys)   p_window_id: 5   p_object: OI_FORM   p_name:
emulate.ex 723 emulate:brief()   p_window_id: 5   p_object: OI_FORM   p_name:
emulate.ex 256 defmain(brief)   p_window_id: 5   p_object: OI_FORM   p_name:
main.ex 5178 _firstinit()   p_window_id: 5   p_object: OI_FORM   p_name:

[prcek]

BTW, when I try to close the (totally blank) VS window, it blows up with a different error (see stack trace below). So v18 is not just unusable, it also refuses to die . In all seriousness, I can obviously kill the process through the task manager (and I have no problem using v17 for now either), so no biggie, but if anyone has a workaround I'd love to try it. Maybe what I could do is delete the config directory, also uninstall / delete v17 (so there's nothing to import), re-install v18, apply the most recent hotfix (if that might help) and then try to re-import my settings - would that work? Kind of a pain, but I can try it.

Thanks
PeterK

Invalid argument
 Slick-C STACK TRACE ******************************
 Created on 7/22/2013 at 17:12:17 (498 ms)
 SlickEdit Version 18.0.0.13 Copyright 1988-2013 SlickEdit Inc.
 Edit module and type "st -f <offset>" to get the
 run-time error position

autosave.ex 261 _DeleteAutosaveFiles()   p_window_id: 5   p_object: OI_FORM   p_name:
autosave.ex 304 _exit_delete_autosave_files(1)   p_window_id: 5   p_object: OI_FORM   p_name:
files.ex 10264 call_list(-exit-,1)   p_window_id: 5   p_object: OI_FORM   p_name:
window.ex 3955 exit_list(1)   p_window_id: 5   p_object: OI_FORM   p_name:
window.ex 4476 safe_exit(1,1)   p_window_id: 5   p_object: OI_FORM   p_name:
window.ex 8354 _on_exit(1)   p_window_id: 7   p_object: OI_EDITOR   p_name:

[patrick]

Looking at it.  The tab settings coming out of v17 look a little odd, in that it's not a format I would have expected v17 to write out, but it's a format we're supposed to be able to handle, so there's a bug here somewhere. 

If you want to get it running for now, two options:

1) Remove the 18.0.0 directory from your config directory.  (ie: ~/.slickedit/18.0.0 under *nix, My Documents\My Slickedit Config\18.0.0 for windows, HOME/Library/Application Support/Slickedit/18.0.0 on Mac).  Fire up v17.  Change the C++ tab settings to something like +4.  Exit v17.  If it's set up to prompt you to save the configuration, be sure to tell it to save.  Start up v18 again.  If the tab setting was the problem, then it should come up with your settings imported.

2) Start it with a clean config.  Start v18 with the command line options "+new -sc SOME_DIRECTORY" where SOME_DIRECTORY will be the location of the new configuration directory.  Should start up.  At this point, you can start up v17, export your configuration via the options dialog, and then import that into v18.  I suspect this will work even though the initial import didn't, but I can't be sure yet.

[patrick]

Derp, hit send too soon.  Could you also post or PM me with the vusrdefs.e or vunxdefs.e file that's in your v17 config directory? 

[prcek]

Thanks for the suggestion - the "tabs" thing worked! My tab setting was "5 9", not sure why (I've been a SlickEdit / Brief user since the 80's and in my old age it's easy to get the command syntax confused . BTW, when I opened a C++ file in v17 it blew up the same way; I discovered several v16 config directories on this particular PC, so it's hard to say how it ended up like this. If you'd still like me to send you that *.ex file just let me know, BTW - I archived all of the pre-existing configs so it's easy to grab any of the old / "bad" files.

Thanks again!

PeterK

[patrick]

Great.  I don't need the files, what you told me confirms what I thought the problem was, so I can go ahead and fix it for v18.0.1.   Thanks for the report.