For years now, my go-to "open -a Xcode ." failed with "Xcode not found". I thought something with "xcodes” was off but never investigated.
Using Codex, I found out that the "Xcode.app" symlink is still pointing to 15.4! Not actually the problem but still interesting.
But it pointed me to #xed, so TIL that there is already a CLI that I can call with fewer keystrokes to open #Xcode for the current path 🥳
$ xed .
Most used applications on my #LinuxMint #LMDE laptop:
#LibreWolf
#Xed
#RetroArch
#ScummVM
#Redream
#chiaki-ng (for #PS5)
#VLC
#StrawberryMusicPlayer
#NicotinePlus
#qBittorrent
#Geeqie
#GIMP
#GnomeContacts
#GnomeCalendar
#GnomeTerminal
#Stellarium
#Foliate
#Blanket
#Plank
"Xed-Editor was updated to 3.1.0, and Git integration was moved to a standalone extension. The developer also warns users to only download the app from the official sources: F-Droid, IzzyOnDroid and the project Github, as somebody has put the app on Play without their approval. The same person/company has done the same for WhatSave unfortunately."
Source: https://f-droid.org/2025/05/22/twif.html
#xed #fdroid #android #playstore #fakeapp #psa #foss #opensource
It's years that I use #markdown for any #notetaking and it feels great, independently from the software.
#Notepad++ #Kate or #Xed do the trick as well, but #Obsidian has a cleaner UX (à la Apple) and an interesting graph feature and a great companion browser extension.
However I prefer the control and customisation capabilities that #QOwnNotes provides. That's my nerdy choice.
I'm writing a document in #Markdown and was somewhat disappointed to realise that #Xed (the default text editor in #LinuxMint) doesn't have a Markdown preview ability...
I didn't really want to install an app just for writing/previewing Markdown files, so searched online instead and found https://stackedit.io/app
It seems to work quite nicely, and it's #FOSS! Win-win.
Title: Projected changes in the Iberian Peninsula drought characteristics.
High spatial resolution drought projections for the Iberian Peninsula (IP)
have been examined in terms of duration, frequency, and severity of drought
events. For this end, a set of regional climate simulations wa [...]
Authors: M. García-Valdecasas Ojeda, S.R. Gámiz-Fortis, J.J. Rosa-Cánovas, E. Romero-Jiménez, P. Yeste, Y. Castro-Díez, M.J. Esteban-Parra
High spatial resolution drought projections for the Iberian Peninsula (IP) have been examined in terms of duration, frequency, and severity of drought events. For this end, a set of regional climate simulations was completed using the Weather Research and Forecasting (WRF) model driven by two global climate models (GCMs), the CCSM4 and the MPI-ESM-LR, for a near (2021-2050) and a far (2071-2100) future, and under two representative concentration pathway (RCP) scenarios (RCP4.5 and RCP8.5). Projected changes for these simulations were analyzed using two drought indices, the Standardized Precipitation Evapotranspiration Index (SPEI) and the Standardized Precipitation Index (SPI), considering different timescales (3- and 12-months). The results showed that the IP is very likely to undergo longer and more severe drought events. Substantial changes in drought parameters (i.e., frequency, duration, and severity) were projected by both indices and at both time scales in most of the IP. These changes are particularly strong by the end of the century under RCP8.5. Meanwhile, the intensification of drought conditions is expected to be more moderate for the near future. However, the results also indicated key differences between indices. Projected drought conditions by using the SPEI showed more severe increases in drought events than those from SPI by the end of the century and, especially, for the high-emission scenario. The most extreme conditions were projected in terms of the duration of the events. Specifically, results from the 12-month SPEI analysis suggested a significant risk of megadrought events (drought events longer than 15 years) in many areas of IP by the end of the century under RCP8.5.
la #pazzia del giorno che vedo in giro e che non è opera mia: questo bel programmino che è #EmulatorJS si regge su un file #JavaScript che da solo è lungo 4900 linee (https://github.com/EmulatorJS/EmulatorJS/blob/1b3a17f6f12a184fc84781c17c692cd7dade1ed5/data/emulator.js)… già solo volerlo modificare è difficile, mi è crashato 1 volta #xed, mentre lo scrolling su #GitHub lagga male 🥴️
magari farò una seconda pull-request per dividergli la roba in più file, se mi va, ma prima farei bene a chiedere.
Xed is AWESOME!!!
Can your VScode do this?
Sören Gade
Emma Liv 🇨🇦
Richard
sfm
TiTiNoNero 
Norm
S.R. Weaver
AOSbot
minioctt
Gers