Benavent

Since the very first moment I upgrade from Fedora 41 to Fedora 42 I notice a good and a bad thing.

The good one was an improvement in performance on the same hardware, maybe it’s just an illusion but that was the impression.

The bad one is Fedora 42 changes the default system editor to Nano. I look for a solution and I found quite a large number of fast and dirty solutions, such as include this line in your profile;
$ echo "export EDITOR=/usr/bin/vim" >> ~/.bashrc

I didn’t like those solutions because they all attack the “effect” but not the “cause” and they didn’t seems to me a canonical solution. I was pretty sure that if Fedora decides to change the default editor there must be a way to revert it… and it was.

The default editor was config via the file: /etc/profile.d/nano-default-editor.sh . So I check what package owns that file via: rpm -qf /etc/profile.d/nano-default-editor.sh and that file belongs to nano-default-editor.noarch.

Since the very first moment I upgrade from Fedora 41 to Fedora 42 I notice a good and a bad thing.

The good one was an improvement in performance on the same hardware, maybe it’s just an illusion but that was the impression.

The bad one is Fedora 42 changes the default system editor to Nano. I look for a solution and I found quite a large number of fast and dirty solutions, such as include this line in your profile;
$ echo “export EDITOR=/usr/bin/vim” >> ~/.bashrc

I didn’t like those solutions because they all attack the “effect” but not the “cause” and they seems to me a canonical solution. I was pretty sure that if Fedora decides to change the default editor there must be a way to revert it… and it was.

The default editor was config via the file: /etc/profile.d/nano-default-editor.sh . So I check what package owns that file via: rpm -qf /etc/profile.d/nano-default-editor.sh and that file belongs to nano-default-editor.noarch.

It was obvious to me that there would be available a package named vim-default-editor.noarch. I tried an simple installation and dnf asks you if you agree to remove the nano-default package, you just consented and since them Vi rules again on the system.

Existen distintas manera de listar el contenido de un paquete rpm instalado. Una que funciona siempre es ejecutar:

rpm -ql NombreDelPaquete

El comando anterior funciona solamente si el paquete está instalado. ¿Y si queremos conocer qué contiene un paquete sin haberlo instalado o antes de instalarlo? He encontrado una manera de hacerlo sin instalar el paquete y que consulta a la información de la base de datos rpm / dnf:

dnf repoquery -l NombreDelPaquete

Un ejemplo para el paquete cmatrix (un pequeño paquete que presenta un protector de pantalla en el terminal). Primero se desintala, con lo que el comando rpm -ql cmatrix no encontrará nada en la base de datos del sistema. Segundo se ejecuta el dnf repoquery -l cmatrix que consultará la información presente en el repositorio.

[root@host ~]# rpm -ql cmatrix
el paquet cmatrix no està instal·lat
[root@host ~]# dnf repoquery -l cmatrix
Fedora 37 - x86_64 - Updates 15 kB/s | 7.9 kB 00:00
Fedora Modular 37 - x86_64 - Updates 33 kB/s | 17 kB 00:00
Fedora 37 - x86_64 - VirtualBox 2.9 kB/s | 6.9 kB 00:02
/usr/bin/cmatrix
/usr/bin/cmatrix-tty
/usr/lib/.build-id
/usr/lib/.build-id/11
/usr/lib/.build-id/11/92b5cf8ad61f36e6322a0f1270a4a88eaf5d5a
/usr/lib/kbd/consolefonts/matrix.fnt
/usr/lib/kbd/consolefonts/matrix.psf.gz
/usr/share/doc/cmatrix
/usr/share/doc/cmatrix/AUTHORS
/usr/share/doc/cmatrix/CODE_OF_CONDUCT.md
/usr/share/doc/cmatrix/CONTRIBUTING.md
/usr/share/doc/cmatrix/ChangeLog
/usr/share/doc/cmatrix/ISSUE_TEMPLATE.md
/usr/share/doc/cmatrix/NEWS
/usr/share/doc/cmatrix/README
/usr/share/doc/cmatrix/README.md
/usr/share/licenses/cmatrix
/usr/share/licenses/cmatrix/COPYING
/usr/share/man/man1/cmatrix.1.gz