From 326ba730395b655372d6a89f6b8ecc863c8cd2a1 Mon Sep 17 00:00:00 2001 From: Eshel Yaron Date: Tue, 15 Apr 2025 08:30:13 +0200 Subject: [PATCH] Fix typo --- esy-publish.el | 4 ++-- source/posts/2023-11-17-completion-preview-in-emacs.org | 2 +- ...-27-emacs-aritrary-code-execution-and-how-to-avoid-it.org | 5 +++-- 3 files changed, 6 insertions(+), 5 deletions(-) diff --git a/esy-publish.el b/esy-publish.el index 7359654..694306e 100644 --- a/esy-publish.el +++ b/esy-publish.el @@ -586,12 +586,12 @@ (list "assets" :base-directory esy-publish-source-directory :publishing-directory esy-publish-local-directory - :base-extension "svg\\|ico\\|css\\|png" + :base-extension "svg\\|ico\\|css\\|png\\|gif" :publishing-function #'org-publish-attachment) (list "sassets" :base-directory esy-publish-assets-source-directory :publishing-directory esy-publish-local-assets-directory - :base-extension "svg\\|ico\\|css\\|png" + :base-extension "svg\\|ico\\|css\\|png\\|gif" :publishing-function #'org-publish-attachment) (list "org" :completion-function #'esy-publish--finalize diff --git a/source/posts/2023-11-17-completion-preview-in-emacs.org b/source/posts/2023-11-17-completion-preview-in-emacs.org index 92bafbe..207215d 100644 --- a/source/posts/2023-11-17-completion-preview-in-emacs.org +++ b/source/posts/2023-11-17-completion-preview-in-emacs.org @@ -69,7 +69,7 @@ The second important question is "when exactly is the preview shown?" The answer is that it /may/ be shown after each command. My initial implementation included a user-extensible hook that Completion Preview mode consulted with after each command to determine whether or not to -show the preview, but that was [[https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66948#68][dimmed]] "over-engineered" during the +show the preview, but that was [[https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66948#68][deemed]] "over-engineered" during the patch review, so currently we have two simple conditions that must hold for Completion Preview to show the preview: diff --git a/source/posts/2024-11-27-emacs-aritrary-code-execution-and-how-to-avoid-it.org b/source/posts/2024-11-27-emacs-aritrary-code-execution-and-how-to-avoid-it.org index 0462e5c..112ef5c 100644 --- a/source/posts/2024-11-27-emacs-aritrary-code-execution-and-how-to-avoid-it.org +++ b/source/posts/2024-11-27-emacs-aritrary-code-execution-and-how-to-avoid-it.org @@ -28,7 +28,7 @@ working on countermeasures that will hopefully make their way into future Emacs versions. This advisory is intended to help users of existing Emacs versions protect themselves. -UPDATE: Mitigations are implemented in Emacs 30 (to be released soon). +UPDATE: Mitigations are implemented in Emacs 30. * Update 2024-12-20 @@ -58,7 +58,8 @@ The Emacs maintainers have implemented a safety mechanism which disables Flymake and code completion induced macro-expansion in untrusted files. This is already included in the latest Emacs 30 "pretest" release, version 30.0.93. See commits b5158bd1914, -8b6c6cffd1f, b9dc337ea74 and 8a0c9c234f1 in emacs.git for details. +8b6c6cffd1f, b9dc337ea74, 8a0c9c234f1 and 5485ea6aef9 in emacs.git for +details. * Background -- 2.39.5