home.social

#vscodium — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vscodium, aggregated by home.social.

  1. Si, comme moi, vous avez #GnomeSoftware qui prend 5 min à charger les données, où si l'extinction du pc met elle aussi 5 min, c'est sans doute à cause de dnf5daemon-server.

    discussion.fedoraproject.org/t

    En l'occurrence dans mon cas c'est la vérification gpg d'un des 2 repos tiers que j'ai déclaré : #vscodium ou #librewolf (très certainement ce dernier vu les alertes lors de la mise à jour)

    #dnf #Fedora #gnome

  2. Si, comme moi, vous avez #GnomeSoftware qui prend 5 min à charger les données, où si l'extinction du pc met elle aussi 5 min, c'est sans doute à cause de dnf5daemon-server.

    discussion.fedoraproject.org/t

    En l'occurrence dans mon cas c'est la vérification gpg d'un des 2 repos tiers que j'ai déclaré : #vscodium ou #librewolf (très certainement ce dernier vu les alertes lors de la mise à jour)

    #dnf #Fedora #gnome

  3. Si, comme moi, vous avez #GnomeSoftware qui prend 5 min à charger les données, où si l'extinction du pc met elle aussi 5 min, c'est sans doute à cause de dnf5daemon-server.

    discussion.fedoraproject.org/t

    En l'occurrence dans mon cas c'est la vérification gpg d'un des 2 repos tiers que j'ai déclaré : #vscodium ou #librewolf (très certainement ce dernier vu les alertes lors de la mise à jour)

    #dnf #Fedora #gnome

  4. #VSCodium peeps.

    I have just moved to a new LAMPs web development platform using LMDE7. VSCodium won't allow me to directly edit the canonical directory (ie /var/www/html/whatever) but sends me into the tmpfs (/run/user/$USER/doc/xxxxx). This FUBARs git. Is there a setting that will allow me to edit files directly?

    EDIT: Solved. It was an issue with flatpak. I installed the deb and it works fine now.

    #Linux #WebDev #LMDE

  5. Done.

    Install of VS Codium to replace VS Code went nicely (via 'snap' in Ubuntu's 'App Center').

    Needed only to reinstall a couple of extensions and reconnect to github (which is another service for which like to review alternatives).

    Also took the opportunity to install a 'linter' (Ruff) for superficial code review - it's a helpful tool; learned about the risk of 'bare excepts' which are ubiquitous in online code snippets/advice.

    #coding #it #ai #vscode #vscodium #codium #linux

  6. CW: VSCodium: Synthwave '84 on Linux issues, fix inside

    If anyone is

    1) on Linux
    2) using VSCodium
    3) struggling to activate Synthwave '84 (github.com/robb0wen/synthwave-)

    You have to run the following command:

    sudo chown -R (your local username):(your local username) /usr/share/codium/resources/app/out/vs/code/electron-browser/workbench

    There's a file that needs to be written on a folder that's under the root user/group

    #linux #synthwave84 #synthwave #codium #vscodium

  7. Naty @eclecticpassions ·

    I forked my Hugo theme and started applying all my overrides into the fork! Maybe one day, I'll share the theme publically... 🤔 Finally, I can work on cleaning up the worse mess: CSS. I can't wait to have a much cleaner style sheet!

    By the way, the branches are looking cool! Merged my first branch already. ;)

    PS: the theme I forked is called Anubis2 by Junyi-99.
    themes.gohugo.io/themes/hugo-t

  8. Naty @eclecticpassions ·

    I feel like I progressed up a level today in my Git skills by creating a new branch to manage my theme improvement!

    I downloaded Git Graph 2 (fork of the popular mhutchie VSC plugin) by hansu: github.com/hansu/vscode-git-gr

    It's so cool seeing the branch graph view 🤩 and I'm learning to write better commit messages/formatting.

    Useful resources:

    gist.github.com/joshbuchea/6f4

    wiki.openstack.org/wiki/GitCom

  9. RE: mastodon.social/@itsfoss/11601

    ⚠️ Si uses VS Code via Snap a Linux, vigila el teu disc! 🖥️💾

    S'ha detectat un error on els fitxers eliminats no van a la paperera del sistema, sinó a una de tancada dins del Snap que no es buida mai. S'han vist casos de fins a 200 GB de brossa acumulada! 😱

    📂 La trobaràs a: ~/snap/code/current/.local/share/Trash

    Es recomana passar a la versió .deb o Flatpak per evitar-ho. 🛠️

    Més info: itsfoss.com/news/vscode-snap-d

    #VSCode #Snap #Linux #Ubuntu #FOSS #OpenSource #DiskSpace #VSCodium

  10. Exit VSCode, enter #VSCodium, binary versions of the VSCode editor with all telemetry and tracking disabled by default.

    It's a drop-in replacement for VSCode and has been working perfectly for me, including its #xdebug integration.

    ➡️ vscodium.com

  11. Extremely happy with my decision to switch back to Sublime Text from VS Codium.

    It's **so much** faster and responsive, I'd forgotten how bloated and slow VS Code was! And no AI slop I need to disable every time it updates, since MS kept pushing them as new features. Totally worth registering, I bought a license for work, too.

    If I had a hard personal requirement to use open source I'd probably go with EMACS. Or Kate.

    #sublimetext #vscodium #vscode #emacs #kate

  12. Extremely happy with my decision to switch back to Sublime Text from VS Codium.

    It's **so much** faster and responsive, I'd forgotten how bloated and slow VS Code was! And no AI slop I need to disable every time it updates, since MS kept pushing them as new features. Totally worth registering, I bought a license for work, too.

    If I had a hard personal requirement to use open source I'd probably go with EMACS. Or Kate.

    #sublimetext #vscodium #vscode #emacs #kate

  13. Extremely happy with my decision to switch back to Sublime Text from VS Codium.

    It's **so much** faster and responsive, I'd forgotten how bloated and slow VS Code was! And no AI slop I need to disable every time it updates, since MS kept pushing them as new features. Totally worth registering, I bought a license for work, too.

    If I had a hard personal requirement to use open source I'd probably go with EMACS. Or Kate.

    #sublimetext #vscodium #vscode #emacs #kate

  14. Extremely happy with my decision to switch back to Sublime Text from VS Codium.

    It's **so much** faster and responsive, I'd forgotten how bloated and slow VS Code was! And no AI slop I need to disable every time it updates, since MS kept pushing them as new features. Totally worth registering, I bought a license for work, too.

    If I had a hard personal requirement to use open source I'd probably go with EMACS. Or Kate.

    #sublimetext #vscodium #vscode #emacs #kate

  15. Extremely happy with my decision to switch back to Sublime Text from VS Codium.

    It's **so much** faster and responsive, I'd forgotten how bloated and slow VS Code was! And no AI slop I need to disable every time it updates, since MS kept pushing them as new features. Totally worth registering, I bought a license for work, too.

    If I had a hard personal requirement to use open source I'd probably go with EMACS. Or Kate.

    #sublimetext #vscodium #vscode #emacs #kate

  16. • Accès à Distance :
    Gaming : #Sunshine (Hôte PC) + #Moonlight (Client) sur réseau local ou via #WireGuard (Serveur VPN hébergé sur mon mini-PC).
    Bureautique/Dépannage : TeamViewer → #RustDesk (serveur auto-hébergé).

    • Bureautique : MS Office/Adobe Reader → @ONLYOFFICE (PC & Mobile) + #Librera FD (Mobile) & #Okular (PC)

    • Plateforme de jeux : Steam → choisir @gog si possible (DRM-Free + Européen)

    • IDE : VSCode → #VSCodium

    7/13

  17. • Accès à Distance :
    Gaming : #Sunshine (Hôte PC) + #Moonlight (Client) sur réseau local ou via #WireGuard (Serveur VPN hébergé sur mon mini-PC).
    Bureautique/Dépannage : TeamViewer → #RustDesk (serveur auto-hébergé).

    • Bureautique : MS Office/Adobe Reader → @ONLYOFFICE (PC & Mobile) + #Librera FD (Mobile) & #Okular (PC)

    • Plateforme de jeux : Steam → choisir @gog si possible (DRM-Free + Européen)

    • IDE : VSCode → #VSCodium

    7/13

  18. • Accès à Distance :
    Gaming : #Sunshine (Hôte PC) + #Moonlight (Client) sur réseau local ou via #WireGuard (Serveur VPN hébergé sur mon mini-PC).
    Bureautique/Dépannage : TeamViewer → #RustDesk (serveur auto-hébergé).

    • Bureautique : MS Office/Adobe Reader → @ONLYOFFICE (PC & Mobile) + #Librera FD (Mobile) & #Okular (PC)

    • Plateforme de jeux : Steam → choisir @gog si possible (DRM-Free + Européen)

    • IDE : VSCode → #VSCodium

    7/13

  19. @oldperl #VsCodium mit #PlatformIO. Ist ein bisschen fummelig, weil PlatformIO leider die C++ Extension von Microsoft benötigt. Die kannst du nicht offiziell unter VsCodium installieren. Manuell mit Fummelei geht es aber. Ist aber gegen die Lizenzbestimmungen.
    Alternative: #VsCode mit PlatformIO. Da hast du auch die Anbindung an den offiziellen Store und kannst direkt PlatformIO installieren. Die C++ Extension wird automatisch mitgezogen. Aber es geht Telemetrie an Microsoft

  20. Depuis que #Gedit ne supporte plus les #plugin #python, je cherche un éditeur de texte de remplacement.

    Je me rabat pour le moment sur #VSCodium sur lequel je suis habitué à coder.

    J'aimerai tout de même qq chose de moins "austère" pour écrire.

    Tous les éditeurs de #markdown que j'ai testé (et il y a foule) souffrent des mêmes défauts :

    * Peu de fonctionnalités.
    * Peu/pas de configurations.

    (1/2)

  21. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  22. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  23. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  24. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  25. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  26. I've finally nailed down the #music studio setup, and can say for music I'm 95% migrated to #Linux (with some #Windows dependence still due to drivers required for programming one of my #synths).

    Using a #system76 tower with #Arch, running #FLStudio with #WineASIO (finally works! no latency from synths!), #lmms, and #Ardour.

    Next project is migrating #Tidalcycles from #VSCodium to #Vim (maybe?)

  27. I've finally nailed down the #music studio setup, and can say for music I'm 95% migrated to #Linux (with some #Windows dependence still due to drivers required for programming one of my #synths).

    Using a #system76 tower with #Arch, running #FLStudio with #WineASIO (finally works! no latency from synths!), #lmms, and #Ardour.

    Next project is migrating #Tidalcycles from #VSCodium to #Vim (maybe?)

  28. I've finally nailed down the #music studio setup, and can say for music I'm 95% migrated to #Linux (with some #Windows dependence still due to drivers required for programming one of my #synths).

    Using a #system76 tower with #Arch, running #FLStudio with #WineASIO (finally works! no latency from synths!), #lmms, and #Ardour.

    Next project is migrating #Tidalcycles from #VSCodium to #Vim (maybe?)

  29. I've finally nailed down the #music studio setup, and can say for music I'm 95% migrated to #Linux (with some #Windows dependence still due to drivers required for programming one of my #synths).

    Using a #system76 tower with #Arch, running #FLStudio with #WineASIO (finally works! no latency from synths!), #lmms, and #Ardour.

    Next project is migrating #Tidalcycles from #VSCodium to #Vim (maybe?)

  30. I've finally nailed down the #music studio setup, and can say for music I'm 95% migrated to #Linux (with some #Windows dependence still due to drivers required for programming one of my #synths).

    Using a #system76 tower with #Arch, running #FLStudio with #WineASIO (finally works! no latency from synths!), #lmms, and #Ardour.

    Next project is migrating #Tidalcycles from #VSCodium to #Vim (maybe?)

  31. What's your go-to, super-simple, publishing stack?

    What is #Gatsby ? You use it? #Gatsbyjs #netlify maybe? someone is building a new site w/ that. VS Codium maybe? i think. maybe? #Codium #VScodium @Liquidream

    I want simple. Something like this. Not so spartan as my .md notes,
    and
    not
    in
    #Python I suppose.

    thoughts?

    i mess w/ #WinterCMS but i'm thinking even more simple. wanna mess w/ opts to mod server-side content

    do people still do that?

  32. VSCodium: النسخة الحُرّة الآمنة من VS Code – بديل مفتوح المصدر بدون تتبع

    #VSCodium #vscode #microsoft #windows #linux #gnutux #programing #لينكس #free_software

    wp.me/p9aAZ6-eP

  33. Ever wondered how to edit your code with VSCodium on your LAN (remote SSH)?
    The alternative plugin does not work on a jail unfortunately or even on some installs....

    The solution is to install sshfs and mount the repositories remote. The user and group permissions need to be set correctly.
    But the manual helps doing that. Works very nicely!

    #VSCodium #SSHfs #repository

  34. I leave an info here that has taken me a while to find out about the use of python environments in #VSCode (Codium)

    In case you have a #python #venv already created in a certain path and you want to use it in VS just go to settings, search for venv and indicate the path of the folder.

    After doing this you will be able to select the python interpreter of the added venv.

    In the image you can see the example I solved with the path to the jupyterlab-desktop venv in #VSCodium

  35. 1/2

    An die anderen #PowerShell-Profis: Es gibt kommerzielle, in der Regel proprietäre #Editoren zu kaufen. Textbausteine, ausgebautes Debugging usw. Proprietär kommt für mich nicht in Frage, so widersinnig das klingt, für einen Windowsarbeiter. Das ist die Lohnarbeit, und die Freiräume, die ich habe, nutze ich für #FLOSS. Ich habe vor Jahren mit #VSCodium und verschiedenen PoSh-Extensions experimentiert, war instabil, #Eclipse ist mir zu groß, aktuell es das eingebaute ISE, auch, weil das auf jedem Kundensystem vorhanden ist.

    Meine Kriterien:
    *FLOSS, klar.
    *Linux- und damit PoSh-7-Unterstützung -- möglichst nicht plattformgebunden. Konfiguration portabel.
    *Ein flotter Festmatrixeditor fürs Terminal darf es gern sein.
    *Es darf auch gern VSCodium sein, mit reiferen Extensions. Obwohl mir Nicht-Microsoft lieber wäre.
    *Es soll einen messbaren Mehrwert gegenüber dem eingebauten ISE geben.