#1940·eza

bug: four `FILENAME_ICONS` entries are unreachable because the names are normally directories

Author: MQDuckCreated Sep 12, 2026Updated Sep 12, 2026
Labelstype: bug

.atom, .idea, .rvm and .zsh_sessions are in FILENAME_ICONS, but icon_for_file() returns early for directories, and all four names are directories in the tools that create them — JetBrains project metadata, Atom's home directory, RVM's install root, and the directory macOS Terminal creates with mkdir ~/.zsh_sessions. (RVM's file-level markers are .rvmrc and .ruby-version; .rvmrc already has its own entry.) So INTELLIJ, LANG_RUBY, SHELL and U+E764 never get drawn for them.

The same four names as directories and as files:

bash
$ mkdir .atom .idea .rvm .zsh_sessions
$ touch .idea/{.atom,.idea,.rvm,.zsh_sessions}
$ eza --all --tree --icons=always
 .
├──  .atom
├──  .idea
│   ├──  .atom
│   ├──  .idea
│   ├──  .rvm
│   └──  .zsh_sessions
├──  .rvm
└──  .zsh_sessions
$
Image

The regular files get their mapped icons; the directories (which is what these names will be in the real world) get a generic folder glyph (U+F115 or U+E5FF). Unfortunately, the special glyphs probably don't make great folder icons.

  • eza v0.23.5
  • bash 5.3.15
  • Arch Linux, x86_64