|
That sounds like an argument between Hefner and Yoda.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
Now more Yoda-like it is. 
|
|
|
|
|
Pardon!! Have you been at the poiteen again?
|
|
|
|
|
It looks like this language model has many random parameters ... 
Cheers,
|
|
|
|
|
VS Code[^]
Just found this a little bit ago have downloaded and kicking the wheels!
Anyone else using it? Any tips, tricks or complaints?
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
I didn't felt motivated to change IDE...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
It's not an IDE it's a light weight code editor with intellisense, highlighting and such.
So far looks pretty good, but just starting to use it.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
Mike Hankey wrote: It's not an IDE
Does it not call a compiler? Does it not execute the executable? And can it not attach a debugger to the executing process? It's an IDE; just not a full-featured one.
"and leaves more complex workflows to fuller featured IDEs." -- Visual Studio Code FAQ
My hope is that it's more like the Turbo Pascal (4 and 5) IDE. Over the last few years I have developed a simple IDE of my own with only the features I need. Debuggers, syntax-highlighting, and Intellisense (though convenient when available) are not things I generally need.
|
|
|
|
|
PIEBALDconsult wrote: It's an IDE; just not a full-featured one.
Agreed, although light weight it is indeed an IDE.
It's pretty cool but not sure if it will replace Notepad++? For me anyway.
Side Note: See it's getting a little warm out there!
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
I've never tried Notepad++ .
It's well into warm, but still too cold to go swimming.
|
|
|
|
|
Oh, so Notepad++ is an IDE now?! 
|
|
|
|
|
Notepad++ is only for Windows, so VSCode has the potential to be useful to many more programmers.
|
|
|
|
|
Same opinion here. I like Notepad++, but there is a need for something simimilar on linux and especially for the people from the win-dev-world.
Please I know about 'vi', but it's not my 1st choice only tool... please!
Something about which we often break our head:
"In the name of the Compiler, the Stack, and the Bug-Free Code. Amen."
(source unknown)
|
|
|
|
|
Sublime Text is still around for the Mac - shame it never got developed further than it did.
TextWrangler (free) is ok(ish) too if you're desperate, but VS Code does a decent enough job too. I tend to use WebStorm on the Mac though.
I came into this game for the action, the excitement. Go anywhere, travel light, get in, get out, wherever there's trouble, a man alone. Now they got the whole country sectioned off, you can't make a move without a form.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
I gave it a spin but decided I liked Sublime better. Maybe it was because I only found one plugin that let me FTP-sync with the actual code base running on an Ubuntu VM, and I didn't want to be bothered with configuring yet another editor.
But there was also something definitely klunky about it. It was sort of the whole gestalt of the tool. But again, by that time, I was probably used to Sublime's quirks and didn't want to learn new quirks, I mean, how to deal with new quirks, in the editor that is. 
Marc
|
|
|
|
|
VS Code definitely has some quirks and takes some time getting used to but I guess it's that way with any editor.
I use Nodepad++ for most of my none programming needs and I'm used to it and have pretty well discovered all the quirks and such. It's kind of like a pair of boots/shoes once you break them in they are comfortable and going to a new pair is a PITA because you have that break in period and you know it's going to hurt.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
I'm really interested in what you found klunky about VS Code. I'm on the VS Code team and we are working on removing adoption blockers. If you can spare the time to describe what put you off the product, we'd really appreciate it. Then we can work on it and improve the experience.
Thanks,
Steven
|
|
|
|
|
Steven_Clarke wrote: I'm on the VS Code team and we are working on removing adoption blockers.
Sure -- I'll fire it up again and let you know, if I get sidetracked (by work) ping me again either here or directly to remind me.
Marc
|
|
|
|
|
SlOT:
I have interacted with VS Code and since you (Steven Clarke) are on that team, the perfect opportunity to ask a question I can't seem to find an answer:
Where is the Run command in VS Code? I typed in an exercise in Python 3.51 to learn some more of the language and could not get the program to execute to the output window. What I'm missing? TIA
Free your mind and the rest will follow,
Don't be colorblind, don't be so shallow!
|
|
|
|
|
Hi,
Right out of the box, VS Code doesn't know how to run Python programs. There are two ways to tell it how to do so though.
First, you can install a Python extension. We have some documentation that describes how to do this: Python documentation
[^]
Alternatively, you can set up a task to run the currently opened file. We have documentation on tasks here: Tasks in visual Studio Code[^]
To set up a task, press Ctrl-Shift-B. If you don't have any tasks defined, VS Code will show a message box saying that no task runner has been configured. Click the button at the right hand side of the message box to configure a task runner.
You'll see a drop down offering a list of different task runners. Choose the 'Others' option at the bottom. This will generate a file in the .vscode folder that shows how to configure VS Code to run an external program (e.g., python.exe).
You can modify the example that is generated for you to look like this:
{
"version": "0.1.0",
"command": "python",
"isShellCommand": true,
"args": ["${file}"],
"showOutput": "always"
}
This tells VS Code to run the python command (make sure your environment is set up to find python.exe in your path, otherwise specify the full path to python.exe as the value for the command field). The args attribute specifies that the current open file should be passed as an argument to the python command.
Save any changes you make to this file, open the python file you want to run then press Ctrl-Shift-B. This will run the task you just specified on the currently open file.
If this all works properly you should see the output from your python program in the Output window.
In this example I've given above, the task assumes that the executable it launches won't seek any input from the user on the command line. There is a workaround for this posted here: Running python script in Visual Studio Code; how to get `input ()` to work? - Stack Overflow[^]
I hope this helps.
Thanks,
Steven
|
|
|
|
|
Thanks for the answer. Right now my head hurts with all of what's required for what should be a straightforward command. I will revisit VS Code, but for now, it's Notepad ++ and repl.it online.
Free your mind and the rest will follow,
Don't be colorblind, don't be so shallow!
|
|
|
|
|
Sorry, didn't mean to make your head hurt
Give the extension a try. It is simple to setup and not only does it allow you to run your Python code from inside VS Code it allows you to debug the code too. You can place breakpoints, step through the code, inspect variables etc.
VS Code is a rich code editor that aims to support all sorts of different languages and runtimes. So there is going to be a little bit of configuration required to get it to do exactly what you want with a specific language and runtime. We're always looking for ways to make this easier though.
|
|
|
|
|
Tried it, thought it sucked.
|
|
|
|
|
Yep, using it and loving it. It's great for a lot of things including editing markdown
Eagles may soar, but weasels don't get sucked into jet engines
|
|
|
|
|
I think it fits in quite well along side notepad++ and Full featured VS.
I tend to only use it for small/non-complex projects
Compared to Full VS it does all the basics and I find it quite a bit quicker, also it's less busy and makes it easier to focus. I still use Full VS for large projects since you have more context of the individual projects and more powerful plugins.
Notepad++ still has it's place for random edits of individual files, VS code seems over kill for that.
I've also used atom and quite a few online editors, they seem closer to the Notepad++ end of the spectrum, VS code seems to fit my needs better, being that it has tight DotNet integratiion.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
