if you're constantly tripped up by #VSCode's File Tree having basically no indentation such that it's hard to determine levels visually, there's an easy fix that's labeled badly (and will affect all trees in the UI that aren't the code editor window):
settings -> search workbench tree indent -> set to like 24px instead of 8 px
I feel like the only complaint I have of #Kate, is that I use text editors like Kate/#VSCode a lot for searching certain keywords - this is a common use case I'm sure.
On VS Code this is easy, on Kate it can/should be too... except the arrows to go to the next or earlier iteration keeps moving when it reaches the very first iteration or very last iteration. It's such a little thing but genuinely frustrating - only bcos it is a very common use case when you're using a text editor like it.
Motherfuckers will spend hours of their life tweaking and fixing their vim config just to get the same functionality as a fresh VSCode install. Get a real job.
I'm trying to figure out GUI development workflows for #Fedora#Silverblue.
I went through a whole thing to connect the #VSCode#Flatpak to a #Toolbx, and while it worked, it was kind of underwhelming. Yeah, I can access the toolbox from the editor, but I can't compile/run from the VSCode menus.
If I'm not getting full integration in the IDE, why not just have a separate terminal with the Toolbox open?
I'm not sure why I can't just compile a C++ program from VS Code due to whatever Flatpak SDKs are already on the system.
I have trouble understanding how GNOME Builder "works" for non-GNOME/Flatpak development use cases. Just getting a binary out of there seems difficult.
For now I'm just falling back to the Geany Flatpak with Toolbox in a terminal. That's simple, and it works.
I'd like to be able to compile/run C++ and Ruby from an IDE, but I don't see it happening. What about Java and Python?
I get that everything is about containers, but I'm not finding a lot of documentation that "normal" people can follow, and it's very short on "Here's a GUI IDE workflow for atomic/immutable distros that is easy and works." Is this solved in #UniversalBlue?
I'm joining the party a wee bit late. Upgrading my little work machine (a NUC-like AMD powered little box from a company called #Beelink) to #Fedora 39 #Silverblue was super smooth once I was told the fedora-modularrepo was no more.
I'm actually running the #uBlue#UniversalBlue community image with a few applications layered on (#1Password, #VSCode, #Fish, #NeoVIM), but it all went swimmingly.
I really do love the immutable OS setup. Good stuff. #FOSS#Linux#GNOME
Do not confuse command pallete with search everywhere (typically Cmd+K) in #DataDog, #Slack, #Spotify, #Monday. It searches through your documents/files, but not through commands and options.
So Visual Studio Code now has a command center at the top and center of the editor window.
i am surprised not more people complained about this.
Yes, I understand the centering of the command center takes the arrows to its left side into account, but it doesn't negate the visual noise it causes when you use the command palette which seems misaligned to it.
And this is why usability is such a field on its own.
Was pleasantly surprised to see #GithubCopilot autocomplete a form letter I was writing (using the #VSCode + #LaTeXworkshop setup I have recently switched to). Given just the opening paragraph and a further sentence, it suggested the remainder of the paragraph that was quite close to what I had actually intended to write, and I was able to complete the form letter in less than half the time I had expected by performing minor edits to the Copilot suggestions.
The letter contains some personal information regarding the subject of the letter, so I cannot share it here; but I can share a typical screenshot of how the autocomplete would work in the paper I recently finished. In attempting to autocomplete an outline of the proof, Copilot does manage to quote relevant results from elsewhere in the paper, but then wanders off into stochastic analytic number theory nonsense. Outside of some very short autocompletions or when writing some repetitive patterns of text, I have found it more amusing than useful while writing math papers thus far, but it may well surprise me in the future. (My previous paper was largely written using my previous editor, so I have not yet fully tested out the new setup on a longer math writing project.)
Every five to ten years, I make the effort to switch my #TeXLaTeX editor to a more modern one. This process has now iterated several times back from when I was a graduate student in the mid-1990s using vi from a UNIX shell to write in plain TeX. On the suggestion of a reader here, I installed #VSCode + #TeXLive + #LaTeXworkshop + #GithubCopilot as an upgrade from my current setup of #TeXnicCenter + #MiKTeX
which I had been using for almost a decade, and am recording my first impressions here (which will most likely be quite naive for existing VSCode users).
The installation had no problems (other than the four hours needed to download TeX live on a slow internet connection). I began experimenting with various features. So far I have mostly played with the user-defined code snippets feature, which can allow me for instance to create an entire corollary environment by typing in a trigger word (I chose "cor") and pressing tab (see enclosed screenshots). Strangely enough I had a version of this functionality 20 years ago during a brief period when I experimented with using Microsoft Word as a LaTeX editor purely for the ability to use Visual Basic macros (though I abandoned this shortly after due to the lack of other LaTeX-friendly features). I could certainly see myself using this feature frequently as a time-saver.
So far the AI-powered Copilot suggestions have been mainly useful for filling out the snippet functionality: after giving a few examples of the snippets I wanted, it was able to suggest more that I could accept, again with the single click of the tab key.
(Incidentally, the screenshots are displaying a paper which I will be putting on the arXiv shortly. Stay tuned...)
Una versione senza telemetria/tracking/sorpresine varie di Microsoft 😅
Dal sito:
"This is not a fork. This is a repository of scripts to automatically build Microsoft's vscode repository into freely-licensed binaries with a community-driven default configuration."
Despite it's widespread popularity, I've been skeptical about VS Code in my own workflows. However, after seeing in action, I've been trying it out myself and it's pretty great.
I'll continue using BBEdit for a couple more decades, but VS Code will be a nice addition to projects.