From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Selecting *Compile-log* buffer automatically Date: Mon, 11 Dec 2023 19:04:39 +0200 Organization: LINKOV.NET Message-ID: <86wmtlrqpc.fsf@mail.linkov.net> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23608"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel@gnu.org To: Kiso Katsuyuki Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 11 18:22:28 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rCjzA-00062d-Kt for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Dec 2023 18:22:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rCjyM-0005EK-MQ; Mon, 11 Dec 2023 12:21:38 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rCjyK-0005E7-7s for emacs-devel@gnu.org; Mon, 11 Dec 2023 12:21:36 -0500 Original-Received: from relay8-d.mail.gandi.net ([2001:4b98:dc4:8::228]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rCjyH-0002fb-CB for emacs-devel@gnu.org; Mon, 11 Dec 2023 12:21:35 -0500 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id 3B7CA1BF20B; Mon, 11 Dec 2023 17:21:26 +0000 (UTC) In-Reply-To: (Kiso Katsuyuki's message of "Sun, 10 Dec 2023 12:38:22 -0600") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=2001:4b98:dc4:8::228; envelope-from=juri@linkov.net; helo=relay8-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313705 Archived-At: > I recently found that I had been moving focus to the *Compile-log* buffer > and burying it after byte-compiling an elisp file. > Selecting *Compile-log* buffer automatically reduces commands to do this. > After my investigation on bytecomp.el and warning.el, there seems to be no > option to select the *Compile-log* buffer automatically > when it shows up in the active frame. > > Does it make sense to do > - On byte-compiling an elisp file, select the byte-compile-log-buffer > window automatically if the buffer is visible, and > - Add a variable to switch the function enable/disable. > ? I believe this should be customizable with something like (setopt display-buffer-alist '(("\\*Compile-log\\*" nil (select-window . t))))