|
|
|
|
|
|
by codethief
327 days ago
|
|
|
> It seems backwards to me to use a fancy IDE, but then run all your code in the terminal. Having literally spent days at a time just to get a working run configuration at various employers and clients over the past decade, I find it backwards to use anything besides the terminal and version-controlled scripts & task runners / CLIs to fire up anything. (: People rarely document their JetBrains setup fully and even if they do, JetBrains IDEs are not exactly known for their reproducible behavior or for not occasionally messing up your configuration (in case you do decide to check in your IDE config & share with your team). Besides, you will need those terminal scripts for your CI pipeline, anyway. That being said, > I love IDE features like clicking on the test I'm editing to run it, and setting breakpoints in the IDE. I agree, that is very useful. However, to me it's the cherry on top of proper self-contained run scripts for the terminal. |
|
|
It looks like this should be possible with tasks https://zed.dev/docs/tasks#variables but I haven't put enough time into figuring it out yet.
Maybe my use case is too specific, but I'll spell it out just in case: I try and open a Django project in Zed. I go to a test file. There's a > arrow next to the test to run or debug, but it will only run it with PyTest (I use unittest, but PyTest is backwards compatible, so w/e). When I try to run it, it fails because some environment variables I need are not set. I don't see how to configure them so I'm dead in the water.
I'd also love to run the Django server with a debugger attached. It's not clear to me how to do that. I haven't found the rights docs. Dead in the water again.
Maybe I need to spend more time exploring and reading the docs :)