From fbbe9a67675b9dd503f4f570d589042cb7a5af46 Mon Sep 17 00:00:00 2001 From: Eshel Yaron Date: Wed, 27 Sep 2023 19:14:27 +0200 Subject: [PATCH] Fix a typo in a blog post --- ...08-making-shell-scripts-executable-just-in-time.org | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org b/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org index 0ff2501..f6878ab 100644 --- a/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org +++ b/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org @@ -103,11 +103,11 @@ C-x v h~ reveals the following commit: #+end_src As we see in the above patch, back in 2000 this function would simply -look at the start of your buffer, and if begins with a /shebang/ it'd -ensure that the file has executable permissions. Other than the name -of the function becoming yet a little longer (the ~executable-~ prefix -was added, so to follow Elisp namespacing conventions), not much has -changed in terms of its implementation since then. +look at the start of your buffer, and if it finds there a /shebang/ +it'd ensure that the file has executable permissions. Other than the +name of the function becoming yet a little longer (the ~executable-~ +prefix was added, so to follow Elisp namespacing conventions), not +much has changed in terms of its implementation since then. Although, as I described earlier, putting ~executable-make-buffer-file-executable-if-script-p~ into one's -- 2.39.2