From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Imports / inclusion of s.el into Emacs Date: Sat, 02 May 2020 12:56:03 -0400 Message-ID: References: <266155d4-f9c0-8ed3-8df5-32feea171076@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="123484"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Emacs developers , Dmitry Gutov To: =?windows-1252?B?Sm/jbyBU4XZvcmE=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 02 18:56:48 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 1jUvRX-000Vzu-Du for ged-emacs-devel@m.gmane-mx.org; Sat, 02 May 2020 18:56:47 +0200 Original-Received: from localhost ([::1]:39964 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jUvRW-0004aM-H4 for ged-emacs-devel@m.gmane-mx.org; Sat, 02 May 2020 12:56:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56154) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jUvQv-0003pu-6K for emacs-devel@gnu.org; Sat, 02 May 2020 12:56:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jUvQu-000495-5R for emacs-devel@gnu.org; Sat, 02 May 2020 12:56:08 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:46289) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jUvQt-00048r-LU for emacs-devel@gnu.org; Sat, 02 May 2020 12:56:07 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 42B4A450841; Sat, 2 May 2020 12:56:06 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 0838245083F; Sat, 2 May 2020 12:56:05 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1588438565; bh=GX3WG9RqvNZ/zXXcNwcWciYIMTPS7zB9YC4IT9emh68=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=lWg0nIMPe7chVpukU9t53KNeVkJb9MbQCh9vjdke7AdhkA3mGwONRY+mqulv3T1GT qlDBUZhid4ey8yGM8GSyCPrQYbDx5ou8mMMvPTNd087BFSz553xWUSnGEf0WffTCQG xQdO/FSRTlw8/p4ZHR/lM2tDqcYFZjlAMt2YKGcefDLWYwzbx7u9ZFRE8Jp/L3PZbS MpvYYhCv+XD38xgsVai/yu6plBKhtjYEbY0mcNDXys+mRJy+hzg7fa9110xOFsKJGx sD61fm+ZKaNYFnu408krzPNVgse9/zulvRSG/bXJ2l1NOePkrcnrK+teGslmChRobu 8srvEKdLLHFmg== Original-Received: from alfajor (unknown [216.154.3.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 97D3812058A; Sat, 2 May 2020 12:56:04 -0400 (EDT) In-Reply-To: (=?windows-1252?Q?=22Jo=E3o_T=E1vora=22's?= message of "Sat, 2 May 2020 14:08:13 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/02 12:48:41 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 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:248499 Archived-At: > Sure. In that case, if it's _not only_ for that reason, then I > would presume it to be mainly because it encapsulates useful > behaviour. It can also be "just because" (i.e. a question of habit). In any case, the point is that renaming the `s` library will go against the grain so the old `s` will likely stick around anyway. So I think we're better off either switching to `s` or coming up with our own `string.el` which we can design without having to worry about compatibility with `s`. > Logically, those developers wouldn't mind keeping that useful > behaviour and finding it under a different prefix/names. I wouldn't bet on it. It might have been true before `s` existed, tho. Stefan "who favors to `string-` prefix"