From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Sheng Yang" Newsgroups: gmane.emacs.bugs Subject: bug#47150: 28.0.50; Incorrect major-mode in minibuffer Date: Mon, 15 Mar 2021 16:58:04 -0500 Message-ID: <05c43a83-6e3c-4f10-a36f-0567bcceb3f6@www.fastmail.com> References: <877dm9nsii.fsf@gmail.com> <40f3c845-ba30-4112-bb3c-9c06c1f106d3@www.fastmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=7b00dfe34f644f6e8a660dca0fab2ec1 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9052"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Cyrus-JMAP/3.5.0-alpha0-206-g078a48fda5-fm-20210226.001-g078a48fd Cc: 47150@debbugs.gnu.org To: "Alan Mackenzie" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 15 22:59:10 2021 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 1lLvEz-0002DF-16 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 15 Mar 2021 22:59:09 +0100 Original-Received: from localhost ([::1]:53320 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lLvEy-0002Qm-38 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 15 Mar 2021 17:59:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41956) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lLvEs-0002Qb-By for bug-gnu-emacs@gnu.org; Mon, 15 Mar 2021 17:59:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54132) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lLvEs-0003MY-4e for bug-gnu-emacs@gnu.org; Mon, 15 Mar 2021 17:59:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lLvEs-0002PU-4F for bug-gnu-emacs@gnu.org; Mon, 15 Mar 2021 17:59:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "Sheng Yang" Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 15 Mar 2021 21:59:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 47150 X-GNU-PR-Package: emacs Original-Received: via spool by 47150-submit@debbugs.gnu.org id=B47150.16158455149228 (code B ref 47150); Mon, 15 Mar 2021 21:59:02 +0000 Original-Received: (at 47150) by debbugs.gnu.org; 15 Mar 2021 21:58:34 +0000 Original-Received: from localhost ([127.0.0.1]:37445 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lLvEQ-0002Ol-0L for submit@debbugs.gnu.org; Mon, 15 Mar 2021 17:58:34 -0400 Original-Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:44259) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lLvEO-0002OX-7y for 47150@debbugs.gnu.org; Mon, 15 Mar 2021 17:58:33 -0400 Original-Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 4330027EE; Mon, 15 Mar 2021 17:58:26 -0400 (EDT) Original-Received: from imap2 ([10.202.2.52]) by compute6.internal (MEProxy); Mon, 15 Mar 2021 17:58:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm2; bh=3+e0mahPm1Lp9SK8rxnINJgfySysifQ bfFFvuwxdr6w=; b=W2K4u18eJmy244YKkSXZGgYZ730JpxkInXVzQ0/IHW/smrd 3CbHXnr+XX8AApy7pOlwyRMvITaYXP0hOeKQYZRk+X/tLolaPYqj6U18S7C8eiHp 26P/LWZ0uAizN3DTpabJYYuJAwrm2psV7oL0AS7WMPaNb2CfX43ntSfTwbFFC0Di rSJSHOfdrksXxMZeEhxg29uBbV+pS3VeDIqMOcRmt869YMFhMhqZvNvOUtEToLvs 8G+mk3WcqXFgdvqFW9P5lpf81qeehjTG33ojcxoOCr5BgkhQDhk4VkKkfSXanHFI 5M8etm14b4Pkvc1KhZKdKYX5Nf+wYllBdxVH8ow== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=3+e0ma hPm1Lp9SK8rxnINJgfySysifQbfFFvuwxdr6w=; b=QC4xeuEpxd8NOPm1ZTsUYs RhyAm6wYSZE5zQvE8Bjbs7QTFEtuEmkTeDWEjie/dbLTUwUJUyjC5NPSRcU4VJOg KGmIv5J1D8GiOgcdQfnSdWwlXubUnqibXs4XtVFClqlujfiPew191z1Z08Hkt1nI mYUDlCPHLu3bBYYWDtMkj+mXa6WFZDh0a7OySY5f2t2zUe9eXBhhkAoOpRMNAbjW HykX7EVJzz1aV4Nkcl7zY0U1UIvc/65ic0ThkgXJUinZpk6L6zRgWQh6OzCtuXsI o5OggsjnuaJkasGbGO6oIlujpFfSxxnc4yalmX3PqVmn7mGjUnf9J2V52DIclajA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudeftddgtdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfufhhvghnghcujggrnhhgfdcuoehsthihrghnghesfhgr shhtmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpeehleeutdduffffgeffieelte etvdduieehhfevgfdviedvtddtieefieeggeevjeenucevlhhushhtvghrufhiiigvpedt necurfgrrhgrmhepmhgrihhlfhhrohhmpehsthihrghnghesfhgrshhtmhgrihhlrdgtoh hm X-ME-Proxy: Original-Received: by mailuser.nyi.internal (Postfix, from userid 501) id 32CEDA00073; Mon, 15 Mar 2021 17:58:25 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface In-Reply-To: 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:202436 Archived-At: --7b00dfe34f644f6e8a660dca0fab2ec1 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Alan, Thanks for the detailed explanation, everything makes sense now. I still= would like to clarify the following > As you say, there is (minibufferp). What is wrong with that? >=20 > That does indeed suggest we really want a minibuffer-mode, rather than= > just fundamental-mode. But surely, the parenthesis pairing will be > dependant on the sort of text you're typing into the minibuffer, so it= > can't really be connected with, say, minibuffer-mode. >=20 > Sorry, I don't understand what you mean, here. How will the use of > (minibufferp) prevent anything else? I am not suggesting anything wrong with (minibufferp). What I have in mi= nd is that it would be better if there is a mode for the minibuffer, so = that existing packages can still use *-modes, *-global-modes, *-inhibit-= modes, etc. to decide whether to enable or disable some functionalities.= I checked the several packages I mentioned, they either compare major-m= ode with minibuffer-inactive-mode directly, or use some *-modes variable= that checks the major-mode. Their maintainers' life will be easier comp= aring to the case where only (minibufferp) is available and they are for= ced to make a corner case for the minibuffer. > I hope my description in this post is satisfactory. Yes, crystal clear! > So, a quick summary: (i) the change in the minibuffer's major mode to > fundamental-mode was intended; (ii) there may be some problems in some= > packages because of this; (iii) we aren't yet in agreement on how to > proceed with this bug report. (i)(ii) agreed. (iii), I am mostly in support of removing minibuffer-inactive-mode and m= inibuffer-inactive-mode-map, and give the minibuffer a proper mode. This= way, the maintainers' life will be easier. Another option is still remo= ve minibuffer-inactive-mode and minibuffer-inactive-mode-map, but keep m= inibuffer in fundamental mode. What do you think? Sheng Yang(=E6=9D=A8=E5=9C=A3), PhD Computer Science Department University of Maryland, College Park E-mail: styang@fastmail.com E-mail (old but still used): yangsheng6810@gmail.com --7b00dfe34f644f6e8a660dca0fab2ec1 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Alan,

Thanks for the detailed explanation, everything m= akes sense now. I still would like to clarify the following

As you s= ay, there is (minibufferp).  What is wrong with that?

That does indeed suggest we really want a minibuffer-mod= e, rather than
just fundamental-mode.  But surely, th= e parenthesis pairing will be
dependant on the sort of tex= t you're typing into the minibuffer, so it
can't really be= connected with, say, minibuffer-mode.

Sorr= y, I don't understand what you mean, here.  How will the use of
=
(minibufferp) prevent anything else?

I am not suggesting anything wrong with (minibufferp).= What I have in mind is that it would be better if there is a mode for t= he minibuffer, so that existing packages can still use *-modes, *-global= -modes, *-inhibit-modes, etc. to decide whether to enable or disable som= e functionalities. I checked the several packages I mentioned, they eith= er compare major-mode with minibuffer-inactive-mode directly, or use som= e *-modes variable that checks the major-mode. Their maintainers' life w= ill be easier comparing to the case where only (minibufferp) is availabl= e and they are forced to make a corner case for the minibuffer.

I ho= pe my description in this post is satisfactory.
Yes, crystal clear!

So, a quick summary: (i) the change in the mi= nibuffer's major mode to
fundamental-mode was intended; (i= i) there may be some problems in some
packages because of = this; (iii) we aren't yet in agreement on how to
proceed w= ith this bug report.

(i)(ii) a= greed.
(iii), I am mostly in support of removing minibuffe= r-inactive-mode and minibuffer-inactive-mode-map, and give the minibuffe= r a proper mode. This way, the maintainers' life will be easier. Another= option is still remove minibuffer-inactive-mode and minibuffer-inactive= -mode-map, but keep minibuffer in fundamental mode. What do you think?


Sheng Yang(=E6=9D=A8=E5=9C=A3), PhD
Computer Science Department
University of Maryland, College Park
E-mail: styang@fastmail.com<= br>
E-mail (old but still used): yangsheng6810@gmail.com


--7b00dfe34f644f6e8a660dca0fab2ec1--