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.devel Subject: RE: Recentish C-s M-y change Date: Fri, 1 Jan 2021 11:12:50 -0800 (PST) Message-ID: <435f0392-e8e5-4208-a27c-40aaa1700427@default> References: <87r1na4tyu.fsf@gnus.org> <87tus6tj7s.fsf@mail.linkov.net> <87a6txigm1.fsf@gnus.org> <874kk5lzew.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5418"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org, Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 01 20:14:19 2021 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 1kvPsR-0001Kb-4m for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jan 2021 20:14:19 +0100 Original-Received: from localhost ([::1]:43164 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kvPsQ-0008EW-5k for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Jan 2021 14:14:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37748) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kvPrA-0007Pc-UD for emacs-devel@gnu.org; Fri, 01 Jan 2021 14:13:00 -0500 Original-Received: from userp2130.oracle.com ([156.151.31.86]:44270) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kvPr8-0001fH-Nq; Fri, 01 Jan 2021 14:13:00 -0500 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 101J6hns112805; Fri, 1 Jan 2021 19:12:55 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=9ev1GTXcrez9t4oyn2mODvxZ2zHKJ62vO+M1cqJcAq4=; b=qAqUpiWbt4umApyCuJQODkXXv7fV7C5f/yvJp/gTjL3aCWJ4YP30hKzxNe0pWLj6MYsV FClVXmM1XodHIjXaAsMUknsG4rVng0zYWjbcgcdlem8uI704njHmUhdEyoEl1w6QYzAF iaF1ykaOCUCPOpH1Bjzy7/oVmUM+HuJQyXKeX2KRwWTkLFwjtLhXppEg/ucqbg+dfuzv ShludjvdHYvtPGVv+meSLPwAaFR96LFxmZn6T1Ig/g+WrndMj9lIoMC6/Ugb9Bn0re8K tXfXhGKANt9O1so+JRDUdk87FuxwpDC6Adf1oeRhl0/+uevHeQmaPF7tQvpglFaMYu/B 1g== Original-Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by userp2130.oracle.com with ESMTP id 35nvkqw5xh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 01 Jan 2021 19:12:54 +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 101JABEl119959; Fri, 1 Jan 2021 19:12:53 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserp3030.oracle.com with ESMTP id 35perq7n7g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 01 Jan 2021 19:12:53 +0000 Original-Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 101JCpQj027951; Fri, 1 Jan 2021 19:12:52 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.5095.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9851 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 adultscore=0 mlxlogscore=999 mlxscore=0 malwarescore=0 bulkscore=0 phishscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101010121 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9851 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 bulkscore=0 adultscore=0 priorityscore=1501 malwarescore=0 impostorscore=0 suspectscore=0 mlxlogscore=999 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2101010120 Received-SPF: pass client-ip=156.151.31.86; envelope-from=drew.adams@oracle.com; helo=userp2130.oracle.com X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, GAPPY_SUBJECT=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:262262 Archived-At: > I almost always exit a search with a command that > will execute after exiting. Some thoughts (maybe relevant, maybe not): 1. There is (longstanding) option `search-exit-option'. But I guess that doesn't override explicit bindings in `isearch-mode-map'. Its doc string doesn't say that, however. At least the doc string of `isearch-forward' does suggest it: "Other control and meta characters terminate the ^^^^^ search and are then executed normally (depending on `search-exit-option'). That "other" comes after descriptions of keys that are bound in `isearch-mode-map', so it suggests that IF a control or meta char isn't bound in the Isearch map THEN `search-exit-option' applies. 2. In Emacs 27, `search-exit-option' has more possible values. Perhaps it could have a value that lets control and meta bindings override `isearch-mode-map' bindings. (I'm not _proposing_ that.) 3. FWIW, in `isearch+.el' I have a white-list option, `isearchp-initiate-edit-commands', whose commands / keys don't exit Isearch but instead initiate `isearch-edit'. E.g., if `backward-char' is in the list then `C-b' during Isearch won't exit search but will instead invoke `isearch-edit-string'. A similar white-list option could be added to Emacs to let users specify commands/keys that _should_ exit and perform their own actions, e.g. movements. IOW, this would override their bindings, if any, in `isearch-mode-map'. This would provide more specific control than would an overriding `search-exit-option' (#2). (Of course, users can explicitly bind whatever control or meta keys they want to `isearch-exit', but that doesn't, by itself, let the command perform its normal action.)