Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Cannot see full filename

Aperta
#4,417 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@mpivchev ci sta già lavorando.

Dal 22/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement

I would like to strongly support this request. This is one of the most frustrating usability problems when working with Nextcloud on Android.

I regularly work with files that have long, similar names, where the most important difference is at the end or in the middle of the filename.

For example:

  • "Annual_Report_Project_2024.pdf"
  • "Annual_Report_Project_2025.pdf"
  • "Annual_Report_Project_2026.pdf"

When filenames are truncated, it becomes impossible to reliably identify the correct file.

I appreciate the work on PR #17426, but the fundamental problem remains: Users still need a reliable way to reveal the complete filename before opening or selecting a file.

I also tested an alternative Android file manager, Voyager, which connects to Nextcloud via WebDAV. Although its file list also truncates long names, it at least allows me to open the file details and see the complete filename.

This is still not ideal, but having that option is significantly better than not being able to identify the file at all.

I would suggest:

  1. Allow filenames to wrap onto two or more lines, ideally as a configurable option.
  2. Provide an easy way to reveal the complete filename, for example via tap, long press, or a file details dialog.
  3. Allow copying the complete filename.
  4. Make the full filename accessible in all relevant file browsing and selection workflows.
  5. Preserve the file extension and ensure that differences in the middle or at the end of filenames remain identifiable.
  6. Consider a configurable filename display mode instead of forcing a single truncation strategy.

The Android system file picker, when accessing Nextcloud through the Storage Access Framework, can also make identifying long filenames difficult. I understand that its UI is controlled by Android rather than the Nextcloud app, so this may require a separate upstream issue.

This is not merely a cosmetic issue. It affects basic file management and can lead to users opening, sharing, editing, or deleting the wrong document.

Please consider a complete solution rather than just changing where the ellipsis appears.

Thank you for your work on Nextcloud!

Originally posted by @funky123 in #17062

Lingua principale
Swift
Stelle
2.5k
Fork
1k
Merge medio
1g 6h
PR unite (30g)
41

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/ios

Tutte le issue di nextcloud/ios

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.