TGViewer
/r/emacs /r/emacs @r_emacs · 81 subscribers
Post #28691 7
need to repeatedly resolve a complete neighboring face here, or could it reuse information the display iterator already knows?

The small cache is a proof of concept, not necessarily the right upstream design. It may be better to reuse existing iterator state or provide a narrower way to answer the box-boundary question.

I would especially welcome feedback on:

* Whether there is existing interval information that makes this cache unnecessary.
* Which face-resolution or invalidation cases this approach might miss.
* Whether a box-specific query would be preferable.
* How best to test glyph and border equivalence before proposing a patch.

**Tested environment:** macOS/ARM64, NS backend, Emacs source revision `fc9cf69afa90990776526a7cf9e693893739fc45`, Org 9.8.7, org-modern 1.15. All core modifications were made in a separate experimental build.

https://redd.it/1x0ou3b
@r_emacs
Reddit From the emacs community on Reddit Explore this post and more from the emacs community
More from @r_emacs
  1. Oct 8, 2026Emacs on Windows 11 Arm64 I got myself an Asus Zenbook A16 and it has been a really great…
  2. Oct 8, 2026Hyperbole HyRolo: Search, Retrieve and Insert Records, Not Lines https://www.chiply.dev/po…
  3. Oct 8, 2026NEW emacs32 master branch support scaling for underline, overline... face Related email di…
  4. Oct 8, 2026Fixing the tree-sitter syntax highlighting bug in Emacs 31+ indirect buffers (The Emacs ma…
  5. Oct 8, 2026makes a measurable difference The experimental change is deliberately narrow. It remembers…
  6. Oct 8, 2026A small change in xdisp.c reduced allocations by ~42% in a boxed-text workload **I think t…
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →