Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

feature: configurable icon for local file links

Aberta
  • Algo errado?
#712 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 6 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
57/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
lua, neovim
Domínio
developer-experience

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Lua
Estrelas
5.2k
Forks
150
Nenhum PR com merge em 30d

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de MeanderingProgrammer/render-markdown.nvim

Todas as issues de MeanderingProgrammer/render-markdown.nvim

Issues semelhantes

Mais issues de Lua

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.