Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

feature: configurable icon for local file links

Offen
  • Stimmt etwas nicht?
#712 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 6 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
57/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
lua, neovim
Bereich
developer-experience

Rechercherichtung

Start by reading the plugin’s link rendering and link.custom configuration code to see how it classifies link targets and applies icon overrides. Trace how relative, absolute, and file:// paths are distinguished from fragment-only links and other URI schemes. Done means local file links can use an optional configured icon, custom overrides retain precedence, and existing behavior remains when no file icon is set.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Is your feature request related to a problem? Please describe.

Links to local files currently use the same default icon as web links. When reading Markdown notes with many links to other notes, a distinct file icon would make it easier to tell whether a link opens another local document or a website.

For example:

[Related note](../notes/topic.md)
[Local document](./document.pdf)
[Website](https://example.com)

I'd like the first two links to use a Nerd Font file icon such as 󰈙 , while the website keeps the existing hyperlink icon.

Describe the solution you'd like

Would you consider supporting a separate icon for local file links, perhaps through an optional link.file setting?

Ideally, this would cover relative paths, absolute paths, and file:// URLs, including paths without a file extension. Fragment-only links such as #heading and links with other URI schemes should retain their existing behavior. Existing link.custom overrides should still take precedence.

Keeping the current appearance unless a file icon is explicitly configured would be fine. This request is about being able to distinguish the link targets, rather than requiring a particular default glyph.

Describe alternatives you've considered

link.custom can match known path prefixes or file extensions. However, covering local paths in general seems less straightforward: paths may have no extension, and web URLs may also end in .md or .pdf.

If there is already a clean way to express this using link.custom, a documented configuration example would also solve my use case.

Additional information

I'm interested in contributing a PR if this fits the plugin's scope. I'd appreciate your preference on whether this belongs in a dedicated setting or the existing custom-link configuration.

Vorherrschende Sprache
Lua
Sterne
5.2k
Forks
150
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus MeanderingProgrammer/render-markdown.nvim

Alle Issues in MeanderingProgrammer/render-markdown.nvim

Ähnliche Issues

Weitere Issues zu Lua

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.