Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

feature: configurable icon for local file links

Ouverte
  • Quelque chose ne va pas ?
#712 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 6 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
57/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
lua, neovim
Domaine
developer-experience

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Lua
Étoiles
5.2k
Forks
150
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de MeanderingProgrammer/render-markdown.nvim

Toutes les issues de MeanderingProgrammer/render-markdown.nvim

Issues similaires

Plus d'issues Lua

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.