From: No Wayman <iarchivedmywholelife@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64452@debbugs.gnu.org, Andrea Corallo <acorallo@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#64452: [Wishlist/PATCH] Use special-mode for *Native-compile-log*, *Async-native-compile-log*
Date: Tue, 04 Jul 2023 18:21:00 -0400 [thread overview]
Message-ID: <87bkgr48qy.fsf@gmail.com> (raw)
In-Reply-To: <83zg4ckki0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
> Thanks, but why not elisp-compile-mode, like we do in
> *Compile-log*
> buffers for byte compilation?
Works for me. Revision attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-comp.el-use-emacs-lisp-compilation-mode-for-log-buff.patch --]
[-- Type: text/x-patch, Size: 2193 bytes --]
From 9912e598354f877cb4ccf20ac68d7267d8c599c8 Mon Sep 17 00:00:00 2001
From: Nicholas Vollmer <iarchivedmywholelife@gmail.com>
Date: Mon, 3 Jul 2023 20:23:00 -0400
Subject: [PATCH] * comp.el: use emacs-lisp-compilation-mode for log buffers
(comp-log-to-buffer): ensure comp-log-buffer in emacs-lisp-compilation-mode
(comp-run-async-workers): ensure comp-async-buffer in emacs-lisp-compilation-mode
---
lisp/emacs-lisp/comp.el | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/lisp/emacs-lisp/comp.el b/lisp/emacs-lisp/comp.el
index 22fb08e4688..5f42d10407f 100644
--- a/lisp/emacs-lisp/comp.el
+++ b/lisp/emacs-lisp/comp.el
@@ -1133,7 +1133,8 @@ comp-log-to-buffer
(log-buffer
(or (get-buffer comp-log-buffer-name)
(with-current-buffer (get-buffer-create comp-log-buffer-name)
- (setf buffer-read-only t)
+ (unless (derived-mode-p 'emacs-lisp-compilation-mode)
+ (emacs-lisp-compilation-mode))
(current-buffer))))
(log-window (get-buffer-window log-buffer))
(inhibit-read-only t)
@@ -4085,7 +4086,8 @@ comp-run-async-workers
:buffer (with-current-buffer
(get-buffer-create
comp-async-buffer-name)
- (setf buffer-read-only t)
+ (unless (derived-mode-p 'emacs-lisp-compilation-mode)
+ (emacs-lisp-compilation-mode))
(current-buffer))
:command (list
(expand-file-name invocation-name
@@ -4119,6 +4121,8 @@ comp-run-async-workers
(run-hooks 'native-comp-async-all-done-hook)
(with-current-buffer (get-buffer-create comp-async-buffer-name)
(save-excursion
+ (unless (derived-mode-p 'emacs-lisp-compilation-mode)
+ (emacs-lisp-compilation-mode))
(let ((inhibit-read-only t))
(goto-char (point-max))
(insert "Compilation finished.\n"))))
--
2.41.0
next prev parent reply other threads:[~2023-07-04 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 0:13 bug#64452: [Wishlist/PATCH] Use special-mode for *Native-compile-log*, *Async-native-compile-log* No Wayman
2023-07-04 11:02 ` Eli Zaretskii
2023-07-04 22:21 ` No Wayman [this message]
2023-07-05 11:25 ` Eli Zaretskii
2023-07-05 12:52 ` iarchivedmywholelife
2023-07-05 14:47 ` Andrea Corallo
2023-07-06 8:52 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkgr48qy.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=64452@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).