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

repl ignores inputrc

Abierto
#720 5 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
30/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Área
cli

Línea de trabajo

Start at the spago repl entry point and inspect how terminal input and inputrc/readline configuration are handled; the issue does not name a file or test. Done means the listed history-search bindings work in spago repl without breaking normal history navigation, with coverage for the reported behavior if the project has relevant tests.

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

Descripción

document me

I have the following lines in my ~/.inputrc:

"\e[A": history-search-backward
"\e[B": history-search-forward

For most apps that use the readline library, this means that I can search my history by typing the first few characters of a previous command and pressing the up arrow. However, spago repl seems to ignore this, and just goes to the previous history entry, regardless of what I type.

This feature would be particularly useful for purescript, since there seems to be no way to reload a package without also losing all the bindings that that were entered previously. It would be a lot easier to re-enter commands if I was able to search the history for them.

(By the way, I don't yet understand the purescript ecosystem well enough to know if this is an issue with spago or some other package - if I should file this issue somewhere else please let me know.)

Lenguaje dominante
PureScript
Estrellas
831
Forks
138
Merge medio
6 h 21 min
PR fusionados (30 d)
4

Preparar el entorno

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 purescript/spago

Todos los issues de purescript/spago

Issues similares

Más issues de CLI

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.