From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Imports / inclusion of s.el into Emacs Date: Mon, 4 May 2020 10:36:52 -0700 (PDT) Message-ID: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> References: <> <> <> <<831ro2tqqx.fsf@gnu.org>> <<4a1fd3f4-df92-c756-9874-4d07b54148ac@yandex.ru>> <> <<3bd09dca-dcdc-7569-e5fb-f6b53397af9d@yandex.ru>> <> <> <<83bln6s5on.fsf@gnu.org>> <<6d43996b-65ab-0bc6-9124-156520396910@yandex.ru>> <<2152FEE0-987F-4816-9FB5-717EED2B47BE@icloud.com>> <<83h7wyqiku.fsf@gnu.org>> <> <<83imhbojx6.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="ciao.gmane.io:159.69.161.202"; logging-data="123959"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pcr910303@icloud.com, emacs-devel@gnu.org, joaotavora@gmail.com, monnier@iro.umontreal.ca, dgutov@yandex.ru To: Eli Zaretskii , rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 04 19:40:01 2020 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 1jVf4S-000W5i-CE for ged-emacs-devel@m.gmane-mx.org; Mon, 04 May 2020 19:40:00 +0200 Original-Received: from localhost ([::1]:57274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVf4R-00042J-Dc for ged-emacs-devel@m.gmane-mx.org; Mon, 04 May 2020 13:39:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58536) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVf3a-0003G6-Pg for emacs-devel@gnu.org; Mon, 04 May 2020 13:39:07 -0400 Original-Received: from userp2130.oracle.com ([156.151.31.86]:37220) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVf3Z-0004JL-JK; Mon, 04 May 2020 13:39:06 -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 044HbYf2018598; Mon, 4 May 2020 17:39:02 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=dZbKK7wjQQZa3GkhLmV7wt8GzNNTm+yBiyXbi+U/cE4=; b=rNT7M75iLzyQf9TxiZtiqtwOlI4/7TyD/dyxSHgeSWRYeER6kvA+jXvCaxibGPipxAmL A1ilwNGdJcG2o08gilsQ9FwoRHm0pqCSnzd45Tl4zFk1DIWSkQ0Y8Z738C0oy14vFl/E EXwMRTfzEfPtainvbfoM9+BbWordvW3Ibr1qJjSQpM2oAeXgmosrXYI8tPPoC+d1l1Qc Y1F/EKPPOJYQ24VXhbIu1xnNkSVY5QzmFsSlQoppDh1dZPctRi2zeT6f6ac0lvlVIgoQ PkMlh6VPPL8URMPDbCtTERYXQd6pTfu93dyJ/NC0s27oJKDRC1gpdhmvVfFRwNuBg2nR OQ== Original-Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by userp2130.oracle.com with ESMTP id 30s09r0dm4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 04 May 2020 17:39:02 +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 044HaqhA050457; Mon, 4 May 2020 17:37:01 GMT Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserp3030.oracle.com with ESMTP id 30sjdr0ecc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 04 May 2020 17:37:01 +0000 Original-Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 044Haskn011207; Mon, 4 May 2020 17:36:54 GMT In-Reply-To: <<83imhbojx6.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4993.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9610 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=18 mlxscore=0 bulkscore=0 adultscore=0 phishscore=0 mlxlogscore=999 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005040140 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9610 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 mlxscore=0 lowpriorityscore=0 spamscore=0 adultscore=0 clxscore=1011 suspectscore=18 priorityscore=1501 malwarescore=0 mlxlogscore=999 phishscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005040140 Received-SPF: pass client-ip=156.151.31.86; envelope-from=drew.adams@oracle.com; helo=userp2130.oracle.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/04 12:45:49 X-ACL-Warn: Detected OS = Linux 3.x [generic] [fuzzy] X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN 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:248883 Archived-At: > > > > So, if I would rename concat, it would be concat-to-string. > > > > > But then people who need to concatenate strings will not find it, > > > because they will type string- TAB. > > > > My solution, extending apropos and its variants so it "finds" > > 'string-' in the name 'concat', would deal with that. >=20 > The main motivation for "renaming" was to have completion find those > names. People who advance that proposal don't want to use apropos > instead of completion. So we will need to extend the completion to do > the same trick you had in mind for apropos. Don't forget that completion can now use substring and other kinds of matching. So depending on what you mean, perhaps there's no need to extend completion - there's just a need to let users get the kind of completion they want in any context. The question, for any given _use_ of completion, is what kind of completion someone wants. For code-completion maybe prefix completion is great. For `C-h f' maybe substring completion is better.