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: Add some aliases for re-related functions Date: Mon, 4 May 2020 10:10:28 -0700 (PDT) Message-ID: References: <7976B8C1-AFC7-4662-B750-6492EB70C0D5@gmail.com> <29721725-0696-4dcf-b5de-36924a5de259@default> <3777996c-7b3f-4d44-9636-f18aaff76a65@default> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="1935"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , Stefan Monnier , Emacs developers To: Philippe Vaucher Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 04 19:13:23 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 1jVeef-0000Kt-AB for ged-emacs-devel@m.gmane-mx.org; Mon, 04 May 2020 19:13:21 +0200 Original-Received: from localhost ([::1]:39762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVeee-00041P-A9 for ged-emacs-devel@m.gmane-mx.org; Mon, 04 May 2020 13:13:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53402) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVedv-0003MC-IQ for emacs-devel@gnu.org; Mon, 04 May 2020 13:12:35 -0400 Original-Received: from aserp2120.oracle.com ([141.146.126.78]:55048) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVedu-0000xw-3o for emacs-devel@gnu.org; Mon, 04 May 2020 13:12:34 -0400 Original-Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 044H35c2067397; Mon, 4 May 2020 17:12:31 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=l2qoirBOmCOd1aAJTHfItHAWh3r1cMB9eJi7yLHV1RU=; b=C9RbYd176tF7K8sKd5CoudTdN1PPwfVSkxzMzlT2W6f/z2gsfuioqzxXtn8t7kRCkWa3 2RakXoIH4UrCWU1QVbdLwRcdJF22tWyA7vrCvd1V2wozbMRDN6ES/MjgZ4dq25uQSUY0 j8rLhOROmcSKhThI37GSYXn86hmGEBzpoCQbO9HH3mAn3nej675vcMrDlg8nYv1Ezwb8 zkJ8QyE/n9iLsLFcRgtM08kDDSHNwv8t0iXcergIIK0UL0FOLMccmSYD7KKXj60C2yEc nCDlSr1z606cSjYyPHmromGl5Ic/oVSUBcOBI9fJAdhW6JEnXbENToxPGh5hlyP8xIDa 9w== Original-Received: from userp3020.oracle.com (userp3020.oracle.com [156.151.31.79]) by aserp2120.oracle.com with ESMTP id 30s0tm873r-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 04 May 2020 17:12:31 +0000 Original-Received: from pps.filterd (userp3020.oracle.com [127.0.0.1]) by userp3020.oracle.com (8.16.0.42/8.16.0.42) with SMTP id 044H6eKJ162098; Mon, 4 May 2020 17:10:30 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userp3020.oracle.com with ESMTP id 30sjjwaj4y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 04 May 2020 17:10:30 +0000 Original-Received: from abhmp0001.oracle.com (abhmp0001.oracle.com [141.146.116.7]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 044HAT1u025842; Mon, 4 May 2020 17:10:29 GMT In-Reply-To: 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 suspectscore=0 mlxscore=0 phishscore=0 bulkscore=0 malwarescore=0 spamscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005040135 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9610 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 mlxscore=0 priorityscore=1501 lowpriorityscore=0 spamscore=0 suspectscore=0 phishscore=0 clxscore=1015 bulkscore=0 mlxlogscore=999 adultscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005040135 Received-SPF: pass client-ip=141.146.126.78; envelope-from=drew.adams@oracle.com; helo=aserp2120.oracle.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/04 12:52:00 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:248873 Archived-At: > > > You make it sound like because naming is hard > > > bad names are ok > > > > How did I make it sound like that to you? > > By systematically showing examples where it's > impossible and always rejecting proposals. > Also your tone while your say this kinda imply > this is a futile endeavor. Maybe it's just me > misintepretating tho. I'm not in any position to reject anything. Eli is the maintainer. I may have disagreed with this or that. Just one opinion. Agreement and disagreement, with accompanying arguments, are normal. > > If you look at the particular half-kidding examples > > I showed, you might see that they're not screwball. > > Nearly all of them are perfectly reasonable.=C2=A0 And > > that's the point of showing them. > > > > With a command such as `flush-lines', if we want to > > prefix the name, just what is a good prefix? > > > > Is the command mostly about lines (the type of data > > acted on), so perhaps use prefix `lines-'? > > > > Is it mostly about regexp-matching/searching, so > > perhaps use prefix `re-'? > > > > Is it mostly about deleting text, so perhaps use > > prefix `delete-' (as in one of its aliases)? > > First of all let's agree that nobody here proposed > to rename flush-lines. Fine. > Anyway, if we had to do it I think all your categories > are weak IMHO, sure it touches the concept of lines, > regexp and deleting I was trying to imagine renamings based on the things involved, which I thought was what is behind, say, renaming functions that are, as you said, "string-related APIs", to have prefix `string-' (and similarly for regexp-related APIs). > but fundamentally it's about modifying buffers. It's about modifying buffer content (only - nothing else about buffers). OK. > If I had to name it it'd be: > > keep-lines -> buffer-keep-lines > flush-lines -> buffer-flush-lines OK. So for you the most relevant thing involved is the buffer. Can you imagine that some might think something else is more relevant/helpful? That's the point (one of the points): which word to use as prefix - what's the main point/effect of the function? What term will users want to look for first or type first? (And other considerations.) > With more finesse I could argue for > `buffer-modif-select` and `buffer-modif-reject` > but I'd probably lose you ;-) Don't worry about losing me. I'm not important. Just try imagining that what's "obvious" to you might be open to different judgments. And naming is very much a judgment call - a balancing act.