File view: no multi-select, so batch drag / delete is not possible
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
Línea de trabajo
Start with CONTRIBUTING.md, which asks that larger changes be discussed first, and with the File Preview keybindings in the docs. The issue places the work in the file view model, which tracks a single current-file cursor, and in its drag and delete handlers. Related issues #965 and #2044 overlap in scope. Done means maintainers agree on a first step, such as Cmd/Ctrl+click and Shift+click, and the agreed behavior is in place.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
File view: no multi-select, so batch drag / delete is not possible
Summary
The file view component only supports a single "current" file at a time. There is no way to
select more than one file, so any batch operation — dragging a group of files into another
directory, deleting a set of files, opening several files at once — has to be repeated one
file at a time. This is the single biggest friction point for me in an otherwise excellent
file workflow.
This sits in the same area as #965 (file management generally — rename / delete / cut /
copy / paste) and overlaps partly with #2044 (multi-select during upload). It is narrower
than both: this is only about multi-selection inside the file view, which is the
prerequisite that makes any of those actions usable in bulk rather than one file at a time.
Concretely, #2044 is about picking several files to send somewhere; this is about being able to
select several files and then act on them (move, delete, rename, open).
Wave Version
0.14.5
OS
macOS 26.2 (arm64)
Steps to reproduce
- Open a directory that contains more than a couple of files in the file view.
- Try to build a multi-file selection using any of the usual gestures:
- Cmd-click a second file
- Shift-click a range of files
- Rubber-band / marquee drag across several rows
- Shift+Up / Shift+Down from the current file
- In every case the selection collapses back down to a single file. There is no visible
indication that a multi-select is even possible.
Expected behavior
Standard file-manager selection semantics:
- Cmd/Ctrl+click — add or remove a file from the selection
- Shift+click — select a contiguous range
- Shift+Up / Shift+Down — extend the selection with the keyboard
- Rubber-band / marquee selection
- Ctrl/Alt+Up / Alt+Down (or Shift+Arrow equivalents) — grow / shrink the selection
And with a multi-selection in place, batch actions on the whole set:
- Drag the selection to move or copy all selected files at once
- Delete (move to trash) all selected files in a single action
- Open all selected files, e.g. across tabs or split views
Actual behavior
Only one file can be current at a time. Per the File Preview keybindings in the docs, Up/Down
merely "change file selection up/down", and no modifier-based multi-select is documented or
implemented. As far as I can tell there is also no file-side delete shortcut at all, which
makes bulk cleanup especially tedious.
Current workarounds
- Move / rename / delete files from a terminal block with
mv,cp,trash,rm, etc.,
then refresh the view withAlt+Shift+R.
These work fine, but they mean the file view itself can't be used for what a file view is
normally for, so every time I come back from the shell the multi-select is still missing.
Anything else?
Happy to discuss scope — my instinct is that this is a contained change: keep a selected-set
next to the existing current-file cursor in the file view model, then add click handling,
keyboard range extension, and route the existing drag / delete handlers to the set instead of
the single item. Let me know if you'd prefer a smaller first step (for example Cmd/Ctrl+click
plus Shift+click only, no marquee drag).
Per CONTRIBUTING.md I understand larger changes should be discussed in Discord first — happy
to move this there if that's the better venue.
- Lenguaje dominante
- Go
- Estrellas
- 22.7k
- Forks
- 1.2k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de wavetermdev/waveterm
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
wavetermdev/waveterm#3587 ·
Los mantenedores suelen responder en 1 día
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
wavetermdev/waveterm#3568 ·
Los mantenedores suelen responder en 1 día
-
pwsh: encodeEnvVarsForPowerShell rejects Windows-standard env var names like ProgramFiles(x86), breaking wsh token on every pwsh blockPosiblemente ocupada @vortsghost2025 la tomó hace 63 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
wavetermdev/waveterm#3481 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
wavetermdev/waveterm#3435 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
wavetermdev/waveterm#3432 ·
Los mantenedores suelen responder en 1 día
Todos los issues de wavetermdev/waveterm
Issues similares
-
area/installation kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
vllm-project/aibrix#3456 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
go good first issue help wanted up-for-grabs
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
andrewsiah/agentswarm-data-tasks#236 ·
Los mantenedores suelen responder en 1 día
-
kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
cadence-workflow/cadence#8745 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
charmbracelet/crush#4271 ·
Los mantenedores suelen responder en 1 día
-
Flake: TestTheTimerBeginsTheNextGame leaves restore-point writes running into TempDir cleanupAbiertobug in-progress needs-triage P1 tier:2-standard
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
krakenhavoc/cmd_and_ctrl#5693 ·
Los mantenedores suelen responder en 1 día