|
Post by Mark Dunham on Feb 19, 2020 14:06:17 GMT -5
Anytime! Feel free to reach out if you have trouble getting them to work. Sublime can be a bit of a bear sometimes. :@) Will do
|
|
|
Post by Mark Dunham on Feb 19, 2020 14:55:01 GMT -5
Anytime! Feel free to reach out if you have trouble getting them to work. Sublime can be a bit of a bear sometimes. :@) "Houston" I need some guidance lol Do import it as a package or do I need to look at it as separate modules?
|
|
|
Post by sarossell on Feb 19, 2020 15:35:06 GMT -5
If you're using Windows, the files just need to be copied to the Sublime User Packages folder. For me, that's
C:\Users\SAR\AppData\Roaming\Sublime Text 3\Packages\User
For Mac, it's
/Users/Scott/Library/Application Support/Sublime Text 3/Packages
After copying the files, restart Sublime and then select the Syntax for Liberty BASIC from the Preferences menu.
:@)
P.S.: It literally took me hours to figure this stuff out, so if you have any trouble, it's kind of expected. But it works flawlessly once you get it right.
|
|
|
Post by Mark Dunham on Feb 19, 2020 15:41:36 GMT -5
If you're using Windows, the files just need to be copied to the Sublime User Packages folder. For me, that's C:\Users\SAR\AppData\Roaming\Sublime Text 3\Packages\User For Mac, it's /Users/Scott/Library/Application Support/Sublime Text 3/Packages After copying the files, restart Sublime and then select the Syntax for Liberty BASIC from the Preferences menu. :@) P.S.: It literally took me hours to figure this stuff out, so if you have any trouble, it's kind of expected. But it works flawlessly once you get it right. Awesome, I was figuring it was going to be an odd path I never did check roaming. Thanks again.
|
|
|
Post by sarossell on Feb 19, 2020 15:53:12 GMT -5
Any time!
|
|
|
Post by Mark Dunham on Feb 19, 2020 15:57:53 GMT -5
If you're using Windows, the files just need to be copied to the Sublime User Packages folder. For me, that's C:\Users\SAR\AppData\Roaming\Sublime Text 3\Packages\User For Mac, it's /Users/Scott/Library/Application Support/Sublime Text 3/Packages After copying the files, restart Sublime and then select the Syntax for Liberty BASIC from the Preferences menu. :@) P.S.: It literally took me hours to figure this stuff out, so if you have any trouble, it's kind of expected. But it works flawlessly once you get it right. I keep getting an error on the shell commands I will have to read up more on it later to see if I can figure it out. Liberty Basic is installed in the default locations with default names? I like how it looks so far very promising.
|
|
|
Post by sarossell on Feb 19, 2020 16:30:47 GMT -5
It might be a permissions issue. I run as Admin by default, so I rarely run into problems.
You might try running the shell commands in the Windows CMD.EXE window directly to see what errors you might get.
You might also try removing the "tskill /a liberty & " part.
:@)
|
|
|
Post by Chris Iverson on Feb 19, 2020 17:02:51 GMT -5
It's most likely a path issue. The configuration uses short paths, which are optional and aren't generated by default on modern Windows systems. (Also, the same path can be shortened to two different short paths on two different systems, depending on the other names that are there.) If you try to use them, the system will attempt to generate them on the fly, unless short name generation has been turned off. If it is, short names won't work at all. (That's not a default setting, though, that's something that has to be deliberately done.)
In particular, try changing both instances "Progra~1" in the Liberty BASIC.sublime-build file to "Progra~2". On 64-bit systems, LB gets installed to C:\Program Files (x86)\ by default, and on those systems, if short name generation is turned on, "PROGRA~1" is usually given to "C:\Program Files", whereas "C:\Program Files (x86)" is given "PROGRA~2".
Also, if you have multiple copies of LB installed, or LB AND LB Pro, you may need to change the Libert~1 to get the one you want.
Also, if you have LB Pro installed instead of LB, the EXE name needs to be changed to lbpro.exe. (And the tskill command needs to kill lbpro).
Sadly, the START command to run LB minimized doesn't seem to work well with paths that have spaces in them. Quoting the path to the start command doesn't work either; it causes the START command to set that as the title of a new cmd window.
And cutting out the start command means the LB IDE won't run hidden, because LB's built-in switch for starting the window minimized is broken.
You can at least add the -a switch to have the LB IDE close automatically once the program finishes running, but that's it.
Here's a version of the file I set up to launch LB Pro from the full path. The START command has been cut out of it.
{ "selector": "source.bas", "cmd": ["date"],
"variants": [
{ "shell_cmd": "tskill /a lbpro & \"C:/Program Files (x86)/Liberty BASIC Pro v4.5.1/lbpro.exe\" -a -d $file", "name": "Debug", },
{ "shell_cmd": "tskill /a lbpro & \"C:/Program Files (x86)/Liberty BASIC Pro v4.5.1/lbpro.exe\" -a -r $file", "name": "Run" }, ] }
|
|
|
Post by sarossell on Feb 19, 2020 17:09:27 GMT -5
All good stuff, Chris. In fact, everything you mentioned is what caused me to have to spend so many hours by trial and error to get it to work for me. You might also consider creating a batch file and calling that from Sublime instead. That way, all of the imposed syntax by Sublime might be avoided.
It's a real booger, for sure. But once it works, it's awesome.
:@)
|
|
|
Post by Mark Dunham on Feb 19, 2020 21:51:32 GMT -5
It's most likely a path issue. The configuration uses short paths, which are optional and aren't generated by default on modern Windows systems. (Also, the same path can be shortened to two different short paths on two different systems, depending on the other names that are there.) If you try to use them, the system will attempt to generate them on the fly, unless short name generation has been turned off. If it is, short names won't work at all. (That's not a default setting, though, that's something that has to be deliberately done.) In particular, try changing both instances "Progra~1" in the Liberty BASIC.sublime-build file to "Progra~2". On 64-bit systems, LB gets installed to C:\Program Files (x86)\ by default, and on those systems, if short name generation is turned on, "PROGRA~1" is usually given to "C:\Program Files", whereas "C:\Program Files (x86)" is given "PROGRA~2". Also, if you have multiple copies of LB installed, or LB AND LB Pro, you may need to change the Libert~1 to get the one you want. Also, if you have LB Pro installed instead of LB, the EXE name needs to be changed to lbpro.exe. (And the tskill command needs to kill lbpro). Sadly, the START command to run LB minimized doesn't seem to work well with paths that have spaces in them. Quoting the path to the start command doesn't work either; it causes the START command to set that as the title of a new cmd window. And cutting out the start command means the LB IDE won't run hidden, because LB's built-in switch for starting the window minimized is broken. You can at least add the -a switch to have the LB IDE close automatically once the program finishes running, but that's it. Here's a version of the file I set up to launch LB Pro from the full path. The START command has been cut out of it. { "selector": "source.bas", "cmd": ["date"],
"variants": [
{ "shell_cmd": "tskill /a lbpro & \"C:/Program Files (x86)/Liberty BASIC Pro v4.5.1/lbpro.exe\" -a -d $file", "name": "Debug", },
{ "shell_cmd": "tskill /a lbpro & \"C:/Program Files (x86)/Liberty BASIC Pro v4.5.1/lbpro.exe\" -a -r $file", "name": "Run" }, ] } This is the error I get 'tskill' is not recognized as an internal or external command,
|
|
|
Post by sarossell on Feb 19, 2020 22:11:58 GMT -5
That's should be easy enough to fix by simply removing the "tskill /a lbpro &" part. Perhaps the missing tskill command is a Windows version issue. I use Windows 10. This command isn't necessary anyway. It's just my OCD showing through. It just closes any currently running instances before starting another one. Sounds like you're getting close. :@)
[UPDATE]: You might be able to replace the tskill with the taskkill command:
|
|
|
Post by Mark Dunham on Feb 19, 2020 22:22:07 GMT -5
That's should be easy enough to fix by simply removing the "tskill /a lbpro &" part. Perhaps the missing tskill command is a Windows version issue. I use Windows 10. This command isn't necessary anyway. It's just my OCD showing through. It just closes any currently running instances before starting another one. Sounds like you're getting close. :@)
[UPDATE]: You might be able to replace the tskill with the taskkill command:
I am using windows 10
|
|
|
Post by sarossell on Feb 19, 2020 22:55:11 GMT -5
Huh. Well, shoot. You might be able to download the latest version of tskill.exe from here (https://www.exefiles.com/en/exe/tskill-exe/). The download links are near the bottom of the page with links for each version of Windows.
:@)
|
|
|
Post by Mark Dunham on Feb 20, 2020 8:08:49 GMT -5
Huh. Well, shoot. You might be able to download the latest version of tskill.exe from here (https://www.exefiles.com/en/exe/tskill-exe/). The download links are near the bottom of the page with links for each version of Windows. :@) Using the sample Chris provided and removing the tskill portion I am able to run it with no errors. I will look at downloading tskill and adding the command back but it runs and now I am coding in dark mode. Once again this community rocks.
|
|
|
Post by sarossell on Feb 20, 2020 11:46:26 GMT -5
Outstanding! What a team we have here, huh?! Glad to hear you got it working. Happy coding!
:@)
|
|