From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#3465: 23.0.94; feature request: be able to log minibuffer messages Date: Sat, 22 Aug 2020 12:17:16 -0700 (PDT) Message-ID: <12b66207-14ef-46aa-98d5-533362f0a3ea@default> References: <<>> <<<87a8keeufp.fsf@gnus.org>>> <<<87r3dq248n.fsf@gnu.org>>> <<<87ziseu7bh.fsf@gnus.org>>> <<<87zh6pkv4b.fsf@gnus.org>>> <<<83364hceou.fsf@gnu.org>>> <<<87k0xtktxc.fsf@gnus.org>>> <<<83wo1taywj.fsf@gnu.org>>> <<<871rk1ksob.fsf@gnus.org>>> <<<83sgchaydm.fsf@gnu.org>>> <<<87sgchjd9r.fsf@gnus.org>>> <<<83tuwv9mm2.fsf@gnu.org>>> <<<87ft8en62j.fsf@gnus.org>>> <<>> <<<834kouaa0y.fsf@gnu.org>>> <<028c363a-e801-4c9a-8ebd-d55180961cf7@default>> <<83zh6m8r4e.fsf@gnu.org>> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39521"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 3465@debbugs.gnu.org, larsi@gnus.org, 4477@debbugs.gnu.org, bojohan@gnu.org To: Eli Zaretskii , Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Aug 22 21:18:14 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1k9Z1n-000A7T-Hj for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 22 Aug 2020 21:18:11 +0200 Original-Received: from localhost ([::1]:35154 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k9Z1m-0001wt-5O for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 22 Aug 2020 15:18:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57434) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k9Z1e-0001wN-Ly for bug-gnu-emacs@gnu.org; Sat, 22 Aug 2020 15:18:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39957) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1k9Z1e-0006VU-Cv for bug-gnu-emacs@gnu.org; Sat, 22 Aug 2020 15:18:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1k9Z1e-0003hN-91 for bug-gnu-emacs@gnu.org; Sat, 22 Aug 2020 15:18:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 22 Aug 2020 19:18:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 3465 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 3465-submit@debbugs.gnu.org id=B3465.159812385113310 (code B ref 3465); Sat, 22 Aug 2020 19:18:02 +0000 Original-Received: (at 3465) by debbugs.gnu.org; 22 Aug 2020 19:17:31 +0000 Original-Received: from localhost ([127.0.0.1]:51499 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k9Z18-0003SG-JR for submit@debbugs.gnu.org; Sat, 22 Aug 2020 15:17:31 -0400 Original-Received: from userp2130.oracle.com ([156.151.31.86]:41640) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1k9Z15-0003ML-R9; Sat, 22 Aug 2020 15:17:29 -0400 Original-Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 07MJD7MT128375; Sat, 22 Aug 2020 19:17:22 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2020-01-29; bh=XOH2giuc6NW3P6OnNdNBw+pZAE/4FEhBt2ZPdoGCHvY=; b=sy99EcIJboU1NPpBcBIUUL2fTTYF9IUjBuBMTMBZEQQ+Uk4xzBDA3L1K5INHFp1UuPXN bK9khwW+3w4VNBfGkCdsVzwcTwj4bjlcW+OUJO1fFJSLvMVbPG+GImwe5/8rrB/JsQg2 6HeJ01zwOlhXWIxtqIEqmOvCqWVxavz4Dv9EouSzn8JwRN7DWB8oXs3XQH6xVJjfGxmp wOUMA8+9GRZ/BDhDi0pm+b4htp0RMniABpXSZkf+xWajZk9DDUKqPhLvg+AYEPJolGkI pLI+9pNzdM4oBspnA8iC7gufIv5lnkleB8x4jyBbcQLYS2F/HJokKpCZi5ANGJvk7AtU Zw== Original-Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by userp2130.oracle.com with ESMTP id 332tsqhfen-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 22 Aug 2020 19:17:21 +0000 Original-Received: from pps.filterd (aserp3030.oracle.com [127.0.0.1]) by aserp3030.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 07MJCc1Y031299; Sat, 22 Aug 2020 19:17:21 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by aserp3030.oracle.com with ESMTP id 332sd8qnbm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Sat, 22 Aug 2020 19:17:21 +0000 Original-Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by userv0122.oracle.com (8.14.4/8.14.4) with ESMTP id 07MJHHWc006274; Sat, 22 Aug 2020 19:17:18 GMT In-Reply-To: <<83zh6m8r4e.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.5044.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9721 signatures=668679 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 adultscore=0 phishscore=0 malwarescore=0 mlxscore=0 bulkscore=0 mlxlogscore=999 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2008220212 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9721 signatures=668679 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 malwarescore=0 suspectscore=0 phishscore=0 clxscore=1015 mlxscore=0 lowpriorityscore=0 bulkscore=0 adultscore=0 priorityscore=1501 impostorscore=0 mlxlogscore=999 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2006250000 definitions=main-2008220212 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:185992 Archived-At: > > The request is to be able to have `minibuffer-message' > > output logged, WITHOUT calling `message'. >=20 > Why "without"? Treat `minibuffer-message' as first-class, the same way `message' is treated. `message' shouldn't affect `minibuffer-message', and vice versa. `message' has an easy way to do what's requested; `minibuffer-message' does not have one. > > It's about simply controlling logging for > > `minibuffer-message', totally, completely, independent > > of any use of `message'. >=20 > You want every single call to minibuffer-message to be logged in > *Messages*? I'm guessing not, because this would make no sense. Not at all. What makes you think that? I think I made it clear that the request is to be able to have, for `minibuffer-message', control over logging similar to what we have for `message'. They are separate. They should remain separate. All that's being requested is logging control for `minibuffer-message' that's on a par with the logging control for `message'. > If you want to log only _some_ calls to minibuffer-message, then you > will have to have special code to request that in those places where > you want the minibuffer messages to be logged. I'm saying that you > can easily call 'message' in those places, and be done with that. What I want is to be able to do with and for `minibuffer-message' what I can do with and for `message'. Without any use of `message' - no connection between the two, no dependence of either on the other. > > IOW, please forget about `message'. The request is > > for a simple way to (optionally) log output of > > `minibuffer-message', just as we do, for example for > > `message' output. And without recourse to any call > > to `message' - no workaround, just a simple way to > > log `minibuffer-message'. We have such a way for > > `message' output. The request is for such a way for > > `minibuffer-message' output - totally independent > > from `message'. >=20 > You cannot request a feature and then also dictate > how it is implemented. I in no way dictated anything about implementation. I have said absolutely nothing about implementation. The entire request is expressed in terms of behavior: user-visible, user-controllable behavior. Nothing about implementation. It's about what users can do. > The solution I proposed should do what you want without > requiring any changes to the core. See above. It doesn't do what was requested. > > > You are already able to do that, AFAICT. > > > > Not simply. >=20 > It's simple enough, from where I stand. Certainly > so for a minor feature such as this one.