Nemo Dragon, meets VS Code
Nemo Dragon, meets VS Code
I am not a fan of MicroSoft, I think most people would be aware of that. I have recently been required to use VSCode for some of my work and I admit it is not entirely unpleasant. I still prefer vim and no vim mode is not good enough 😉 though it does make it vastly more usable.
After an arm wrestling match, that I finally won, I have VS Code configured for my work environment. I use Fedora 43 Workstation for my daily driver and getting VS Code to co-operate with my default configuration for the terminal was a bit of a nuisance. There must be more than a million settings in this beast! 😉
Unus Nemo
plan-A (ﾟヮﾟ) likes this.
plan-A (ﾟヮﾟ)
in reply to Unus Nemo • — (8 - Bit) •@Unus Nemo Well I made my own, was tired of Telemetry and I know you love Vim as many do, dunno why but the nano thing still keeps as a KISS way for me.
Made my own kind , only have to add bash and many more funcs in the GTK app.py with all dependencies etc at hand in 1 Pod my toolbox dev-env box
Was bored and initial idea was to keep a tracker of own made codes , I made it a week ago I think or 2 but amply used it lol, it is not the same but it can be enhanced! 😃
I think the pimp my OS up is done now and just make the existent better.
I have the idea that people may regard an Atomic version just good to keep files in it and have another daily drive while this just elevates your daily drive in my opinion> with some minor restrictions that are solvable.
Unus Nemo likes this.
Unus Nemo
in reply to plan-A (ﾟヮﾟ) • •@plan-A (ﾟヮﾟ)
I am doing a technical review on a video course on the Go programming language. The creator uses MS/VSCode in the course so it was necessary for me to use that for the review. So far I am not upset with the editor but it is unnatural for me so I had to adapt.
One of the things that bothered me was that when using the shell via VSCode's integrated terminal was that I lost all of my normal shell env that I have taken a lot of time historically setting up. This was not acceptable. So I did a deep dive and found that VSCode runs one instance of the shell for itself and then creates a subshell for it's integrated terminals. I have shields in my configuration that prevent it from being sourced multiple times which can lead to bloat and an environment with a path that has the same directories in it multiple times. So VSCode's approach stopped the integrated terminals from being able to source
... Show more...@plan-A (ﾟヮﾟ)
I am doing a technical review on a video course on the Go programming language. The creator uses MS/VSCode in the course so it was necessary for me to use that for the review. So far I am not upset with the editor but it is unnatural for me so I had to adapt.
One of the things that bothered me was that when using the shell via VSCode's integrated terminal was that I lost all of my normal shell env that I have taken a lot of time historically setting up. This was not acceptable. So I did a deep dive and found that VSCode runs one instance of the shell for itself and then creates a subshell for it's integrated terminals. I have shields in my configuration that prevent it from being sourced multiple times which can lead to bloat and an environment with a path that has the same directories in it multiple times. So VSCode's approach stopped the integrated terminals from being able to source my configuration so my desired env was not available in VSCode's integrated terminal. I found a toggle that allowed me to turn that feature off so that my env was sourced in the integrated terminals.
Now this may be a small detail to some. Though I do 90% of my work in the terminal and not having access to my normal env was not pleasant at all. It basically made using the integrated terminals painful and unproductive. I was pretty excited to see Nemo Dragon rear his head in the integrated terminal as it showed my env was indeed being sourced! 😉
The only negative part of using MS/VSCode is the feeling that MS is watching, lol, of course I have a copy of VSCode built from sources so I know that is not possible in my case. As I would have seen the code on inspection and I would see evidence of the telemetry on my network.
Would you install a stock version of VSCode and see if you get any telemetry? I would appreciate it if you could do that test for me. Do not use a copy distributed by a third party such as they have in the Fedora repo, get the version distributed directly from MS. I know you will do a very thorough investigation 😀. I have faith in your paranoia 😛
Unus Nemo
in reply to plan-A (ﾟヮﾟ) • •@plan-A (ﾟヮﾟ)
I do not think I will ever be done pimping up my OS after 30+ years I am still working on it 😛. I do not think we outgrow that. When we leave the confines of MS/Windows (In my case MS/DOS) or MacOS behind and we are given the freedom to make our computer truly our own. It is hard to not take advantage of that opportunity.
Unus Nemo
in reply to plan-A (ﾟヮﾟ) • •@plan-A (ﾟヮﾟ)
What do you mean by keep a tracker of own made code?