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: Tue, 5 May 2020 08:03:56 -0700 (PDT) Message-ID: References: <83368ivmym.fsf@gnu.org> <5f91c6e5-b4af-4478-b221-4ca37f0fb74c@default> <2afdde98-4d71-4847-8ee4-b0eee677baef@default> <8d649ffd-c60e-4cb5-ae21-413cc39ae409@default> <3df43231-ea25-4ceb-82f3-45a493091849@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="125869"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Stefan Monnier , Richard Stallman , Emacs developers To: Philippe Vaucher Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 05 17:05:25 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 1jVz8O-000WX0-FR for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 17:05:24 +0200 Original-Received: from localhost ([::1]:39186 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVz8N-00047x-Gm for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 11:05:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40304) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVz78-0003RC-Gz for emacs-devel@gnu.org; Tue, 05 May 2020 11:04:06 -0400 Original-Received: from aserp2120.oracle.com ([141.146.126.78]:43698) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVz77-0000be-6B; Tue, 05 May 2020 11:04:05 -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 045EnKdV030385; Tue, 5 May 2020 15:04:01 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=/cGBddwPwg9krSI86kW7fGVBZcIofIW6tKRPRBaJGQQ=; b=0DW8HvrVeTSBojNMsKdaC0KV19TzKBU/mubNNzvdKy8go3tkt4OYV+gxFGc7WKRDH+59 Zixz+ZgRh+4iKkwi6tKZdckge73Km860AqZdx/uvhBj2Z4ThTnqpfERiurG18nU8IJgY /mzXyLWm/1f6B74WJyUH0Ca9W8S2wpnVKaD0bo3iFR504ufyROop/WueuN809SxLxK0T 4lrwa5dgRpDqv6icrx+79q+sIZfKslvylZDnnKnvrvHgXAJ95cq5EDdjzQrQWGE7O/vh XlZwx6Upf8dLDJAwt8n8FzOWtHIJrE93GPHH89gdJsjcY3QHvaxhhRyMaBCAjyGziYol 1A== Original-Received: from aserp3030.oracle.com (aserp3030.oracle.com [141.146.126.71]) by aserp2120.oracle.com with ESMTP id 30s0tmd9j2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 05 May 2020 15:04:01 +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 045Ekjr1117721; Tue, 5 May 2020 15:04:01 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserp3030.oracle.com with ESMTP id 30sjdt6vwm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 05 May 2020 15:03:59 +0000 Original-Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id 045F3v4e018604; Tue, 5 May 2020 15:03:57 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=9612 signatures=668687 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 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-2005050121 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9612 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-2005050121 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/05 11:04:03 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:248998 Archived-At: > > I suggested that any proposed name changes > > (including aliases) be submitted (and tracked) > > as bug/enhancement requests. > > > > And I'm not aware that anything has been rejected. > > If you submit them as a bug report (or bug reports, > > if they're not very related) then it will be clear > > if the bug gets fixed, stalls, or is closed as > > won't fix. >=20 > Well I thought I did a concrete proposal on `string-` and I'm thinking > that if I made the same proposal throught the bug tracker I'd get the > same answers. >=20 > Anyway, I'll try if you tell me that's how I'd do it. I'm a bit > reluctant because I hoped that we'd do this all together here and > reach some form of consensus with rough guidelines like "yes I think > for A, B, & C it makes sense, for D & E not so much" and thus the real > concrete proposal would already be pretty accurate. >=20 > I'll make a bug report anyway and we'll see how it goes. Should it be > already patches or just a message with "new aliases / new api" > sections like I did a few emails above in that thread? I can't speak for anyone but myself. Others will perhaps offer other suggestions. I'd suggest filing an enhancement request (M-x report-emacs-bug) for some specific renamings or aliases, providing brief reasons. If you think it will help, you can reference, or quote from, specific messages in this list (at=20 https://lists.gnu.org/archive/html/emacs-devel/). But maybe wait a bit, to see first if you get other suggestions, including any that might disagree. Eli, in particular, may have a preference about handling this.