Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Move to new window hangs xed for up to 10 minutes when underlying file has changed

Abierto
  • ¿Algo no está bien?
#765 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
desktop

Línea de trabajo

Start by tracing how Xed handles external file changes and moves a tab between windows; the issue does not name a source file or test. Reproduce the sequence with a file modified externally before moving its tab, then check that the move does not hang and that Xed reports the changed contents so they can be reloaded without overwriting them.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

xed - Version 3.8.9 on x86-64 Linux Mint 22.3 Zena

The problem replicates consistently on my system:

  1. Open a file with xed (e.g. a file on a NAS server)
  2. Modify the file (e.g. externally via another NAS client)
  3. Move the tab to another window before the message appears to reload the file

result: Xed hangs for up to 10 minutes.
Fortunately, if you are patient and click many times on "wait" instead of "terminate", xed ultimately recovers with the desired outcome: the tab has moved to a new window and no work has been lost. In my case, the file captures the output of failed background kernel compilations, part of git workflows, so very unpredicatable.

EDIT: forgot to mention that the new window contains the original, non-modified version of the file and won't display a message that the file has changed anymore. There seems no way to reload the modified contents (no refresh/reload button). The only indication you get is a message warning you to overwrite the file when using the "save" function. Never a message to reload the file, even when the file is modified a second time. Hitting "save" a second time, gives no more message and destroys the file.

It is quite annoying because one has generally no idea that the file been has modified and unless you understand what is happening and have the patience, the expected reaction is to terminate the editor and start all over which can cause both "lots and loss" of work.

Happy to look into the code and file a PR, but need some help to figure out where to start cause I have never looked at Xed source code.

Lenguaje dominante
C
Estrellas
558
Forks
117
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de linuxmint/xed

Todos los issues de linuxmint/xed

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.