rebuild, the buffer contains information that the Lisp state does not, and that unsaved text can be…
انتشار: 2026/08/11 10:07 UTCدریافت: 2026/08/13 05:00 UTCآخرین مشاهده: 2026/08/13 05:00 UTC
rebuild, the buffer contains information that the Lisp state does not, and that unsaved text can be lost.# 4. Display glyphs are not always text columnsGraphical checkbox glyphs and other display properties can occupy a different apparent width from their underlying string.That is usually harmless in a normal widget buffer, but it becomes visible ninside grids, padding and borders. For layout-heavy interfaces, text representations such as \[ \] and \[x\] are much easier to measure reliably.# 5. Recreating every widget is expensive; recreating changed regions can be acceptableThe useful question was not “Is widget.el slow?” but:>Which widgets are recreated, how often, and over what region?Preserving widgets in unchanged regions and adding optional fast paths produced a large improvement without replacing the control system.# 6. Benchmark byte-compiled codeThe source-loaded and byte-compiled results differed substantially, especially around closures and layout traversal.Source-loaded measurements are useful for relative profiling, but release-like performance should be measured with byte-compiled TextUI and widget definitions.# Where TextUI now standsTextUI still does not provide component-local state, a virtual DOM, CSS, a box model, or another widget catalogue.It currently provides:* responsive Flex and Grid layout* Knuth–Plass paragraph justification* native image regions* ordinary widget.el controls* buffer-level state* lifecycle effects and async protection* automatic block reconciliation* explicit region refresh as an optional fast path* optional measurement and attachment acceleration for package-owned widgetsThe project has moved from asking “Can Emacs display this kind of interface?” to a more useful question:>How much layout and refresh behavior can we add while keeping the native Emacs programming model understandable?For now, “automatic by default, explicit after measurement” feels like the right boundary.I would be interested to hear from package authors: which part of widget.el causes the most trouble in real interfaces—layout, editable fields, refresh cost, focus, or something else?\\[github.com/yibie/textui/blob/main/CHANGEL…(github.com/yibie/textui/blob/main/CHANGEL…)redd.it/1vlcqtu@r_emacs
تاریخچه بازدید مشاهدهشده
حدود 0 بازدید تازه در ساعت در این نمونهپستهای تلگرام — /r/emacs
Org-draw: Drawing inside org-mode using tl;drawyoutu.be/04zbf-tosNQhttps://redd.it/1vpon…
Magit Ricing?preview.redd.it/t1owu3yvkmjh1.png?width=9… really starting to like Magit from a functionality standpoint, but I hate to say it—it’s ugly. It’s probably the better choice for me practically, especially since I’m already using Emacs, but I really like the way Lazygit looks and feels.What I especially like about Lazygit is the panel-based layout. Files, branches, commits, diffs, etc. are visually separated into their own areas, which makes the interface feel much cleaner and easier to scan than having everything in one continuous buffer.Has anyone riced or customized Magit to get closer to that kind of look? I’m not necessarily trying to recreate Lazygit exactly, but I’d love stronger visual separation between sections and more of that clean, organized panel/dashboard feel.redd.it/1vphmxv@r_emacs
A Tour of Magit's Status InterfaceI just wrote a post about Magit's status screen, focusing on why it's powerful rather than just saying it is, I've always found the "why" gets asserted more than explained. It's written to be approachable for non-Emacs folks. Planning follow-ups on staging/committing and cherry-pick/rebase.For those who have been using Git CLI, what workflow did Magit make so painless you now take it for granted?heiwiper.com/posts/magit-status-tour/http…
Has anyone gotten org-display-remote-inline-images to work ?Found a post that says org-display-remote-inline-images only functional for TRAMP paths. Is this accurate ? I tried both 'cache and 'download options still getting "No images to display inline" Tried both with and without double brackets. (Local images work fine)emacs: 30.2 org mode : 9.7.11redd.it/1vpcccc@r_emacs
Gptel new interaction interface ?youtu.be/T9HSTSm7i5Mhttps://redd.it/1voxx…
Capture dotfiles using org-captureSince I discovered org mode, I always was balancing between using symlinks and org babel tangle to manage my configuration. Now I'm in point that work related items are org babel managed and system level config is symlinked, because, often tools write back to their files. Another reason why I did not go full on babel was that I don't like workflow:1. found file that requires backup2. copy file3. paste in to org mode4. fill all details5. tangle.But yesterday I was visited by GNU spirit and she gave mi this org-capture template that reduces adding new file to backup to C-c k (my capture prefix) b (backup) and then tangle that file to original place: * [[%(project-root (project-current))]] [[%(abbreviate-file-name (org-capture-get :original-file))][%(file-relative-name (org-capture-get :original-file) (project-root (project-current)))]] - repository :: [[%(project-root (project-current))]] - file :: [[%(abbreviate-file-name (org-capture-get :original-file))][%(file-relative-name (org-capture-get :original-file) (project-root (project-current)))]] #+header: :tangle %(abbreviate-file-name (org-capture-get :original-file)) #+begin_src %^{Language|shell|elixir|nix|python|elisp|fundamental|eshell|conf} %(with-temp-buffer (insert-file-contents (org-capture-get :original-file)) (buffer-string)) #+end_srcI cannot comprehend how simple it is and how I never realized I could do this. Two think I think would be nice in future: \- if only it can automatically group those captures by project, but thinking of creating project backup capture template and simply refile from capture buffer \- automatic detangle so I can get back changes written by tools to their files, but not all of them support comments and many of them don't patch but dump state to file, so probably unsolvable using build in tools, only by elisp scriptingI'm trying to avoid longer elisp scripting for now 😄 What do you think?redd.it/1vowo7f@r_emacs