Screenshot
Hey guys, I am new to Sublime Text3, and last week somehow I changed the way ST3 lint my code and show the error information. It looks actually a little annoying and I would like to get rid of these instant error display while I am coding. Can someone tell me how to do that?
In addition, how to setup ST3 so that when you type a function from a package, it could show its meaning and format? I can do it in my Windows PC but failed in MAC.
Really appreciate any help!
Open your package control, for Ubuntu its Ctrl+Shift+P, It may be Cmd+Shift+P, type disable in the package, it would show you Package Control:: Disable Package, press an enter key, now disable the packages that are causing it.
Related
I go to :
and install :
with these settings :
and have no idea why hex is not my SBT3 still not display as its color form. 😥
I've also tried : CSS
Reboot the IDE & even reboot the Mac OS X ... still not working.
Did I forgot to turn on some settings?
Can someone please help me ?
Edit
ColorHelper works on the first try, right after install. Huge thanks to : #MattDMo
... but I am still curious if someone really knows what I did wrong.
Over the past few years I began having more and more problems with the different color highlighting packages available for Sublime, including Color Highlighter, which hasn't been updated in at least 3 years, and Color Highlight at 2½ years. Someone recommended ColorHelper, and I've been happy with it ever since. Make sure you completely uninstall Color Highlighter and/or Color Highlight first, as I think I had issues with it before I did that. ColorHelper is in regular development with the release of the new v3, which apparently is a complete rewrite, and is easy to set up and use out of the box. There are a ton of customization options if you want to get into the weeds, and the author has been very responsive with some config issues I had recently. I would highly recommend it.
Recently, I switched my OS to Ubuntu. I just started with collage and I have to learn pascal for my finals. But a problem occurred.
I installed Visual Studio Code and Pascal extension for it, but I am unable to run even a simple Hello World code. I wrote code, it saved automatically as .pas, but when I enter debug & run option in VSC it displays a message that says 'Open a file which can be debugged or run.', followed by 'debug' and 'run' buttons that I am unable to click and another message that says 'To further configure Debug and Run create a launch.json file.'
I am not even sure am I supposed to post questions such as this one on stackoverflow, but I sincerelly hope that someone could give me a hint on what to do. Solve this within Visual Studio Code or switch to another IDE (and which one would you recommend for Linux user) and pretend that nothing happened?
Thanks in advance.
I know this isn't an answer to "how to debug with pascal with vscode" but, perhaps you would find it easier to just use FPC / Lazarus (IDE) to do your work. While it doesn't have a dark theme, contrary to popular belief, that's not necessary to program.
The IDE is feature packed and allows for full code completion, debugging, etc... (everything you really need to do the work for school).
Additionally, you can use this open source tool to install everything you need for your platform in just a few button clicks (also allows for installing common library packages)
https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases
download release for your OS
under "FPC Version" & "Lazarus Version" select trunkgit (or stable for an older version)
click the "Install/Update FPC + Lazarus" button
Have you Installed Pascal extension which is available for code to smoothly run pascal code.
If you haven't then try installing this extension using,
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
ext install alefragnani.pascal
You can always check,
https://marketplace.visualstudio.com/items?itemName=alefragnani.pascal
to install and configure pascal in vscode.
I will direct you to the debugging page from the Visual Studio Code documentation that details how to use the debugger and configure a launch.json file. VSCode is a generic IDE so you need to give it some information about your project before it knows how to run the debugger. This is what launch.json is for.
If I could make a suggestion. When you're learning how to program, it's best to start with the basics. Write a small program in a text editor (VSCode is fine, or Vim, or Nano, or Notepad, or whatever). Save the file. Compile and run the program on the command line.
Once you put an IDE in the mix, you have to learn how to use that as well. If you're stuck on both parts, it can be hard to make progress. That said, it's good to learn how to use the IDE, and you should spend some time reading the documentation and working through some of the examples. It takes some time, but it will pay you back a thousand times when you can work more quickly.
I have been dealing with a bug in Sublime Text in js files for a while where anytime I write a comma or semi-colon, Sublime Text creates an autocomplete box with a specific number 62118. So anytime I hit enter it will autofill this useless number and I have to delete it.
More keystrokes = More anger, so I was wondering if
anyone has run into this
or if anyone might have an idea whats causing it
OR if anyone has a good general technique for finding bugs in Sublime Text
It seems to only happen in .js files but I could be wrong so help me out here please I'd love to keep the configuration I have.
There may be information in the Sublime console. To open the console go to View > Show Console (ctrl + `).
Otherwise, uninstall your plugins one by one. While it probably isn't necessary, it would be a good idea to restart Sublime each time you uninstall, to make sure any caches the plugins create are cleared.
Finally, you can simply disable autocomplete by adding the following to your User Settings.
"auto_complete": false
Does anyone know how automatic build systems work in 3083 right now? Because I am struggling to get it to do the right thing. (p.s. I am not an expert st3 customizer so I am probably just doing it wrong.)
My TypeScript.sublime-build file lives in ../Packages/User and contains:
{
"cmd": ["/usr/local/bin/tsc"],
"file_regex": "^(.+?) \\((\\d+),(\\d+)\\): (.+)$",
"selector": "source.TypeScript"
}
When I edit a .ts file the syntax highlighting is for TypeScript and that is also what is displayed in the bottom right corner. So from that I deduce that ST3 is correctly identifying the desired syntax for the file (although I am not sure where that happens.)
When I choose the TypeScript build system by hand and click CMD-B it runs the build and displays the output in the console, as I expected.
When I have "automatic" build system and I open a .ts file or change to a .ts file that was already open, ST3 again correctly identifies the syntax (bottom right in the window.) However when I click CMD-B it runs the last build method that I happened to have used.
I thought that the idea with automatic is that it would choose the build system based on the syntax identified via the file extension.
Does anyone understand this problem or correct my assumptions?
Never figured out the problem. But I fully uninstalled ST3 and reinstalled it, with the package control and typescript packages and nothing more, and now it seems to work. Oh well. I guess not all the bugs are out yet.
I don't know of any other way to access Package Control, but i find it weird that it doesn't work anymore, could the installation of other packages have caused it to just stop working? I don't even know how to debug something like this or find a solution for it, it appears this doesn't happen to many people, but it surely is happening to me.
When i press cmd+shift+p i don't get the Package control window. My ST3 has been very buggy and no updates have ever been available.
Is there just a quick way to wipe it all clean and start over?
Thanks.
If you want to completely start from scratch, first exit Sublime, then delete /Applications/Sublime Text.app. Finally, delete ~/Library/Application Support/Sublime Text 3.
You can now re-download ST3 and reinstall Package Control. Restart Sublime as instructed, and you should now be able to hit ⌘ShiftP and open the Command Palette. Type in packcon to get the Package Control options. You'll need to reinstall all your plugins, and reset any custom preferences, keybindings, snippets, etc. you've made.
Good luck!