From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?utf-8?B?7KGw7ISx67mI?= Newsgroups: gmane.emacs.devel Subject: Re: Imports / inclusion of s.el into Emacs Date: Tue, 5 May 2020 22:18:21 +0900 Message-ID: <02922A76-29E2-46EA-9D99-83421BAC5E43@icloud.com> References: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="15639"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Philippe Vaucher , Drew Adams , Eli Zaretskii , Richard Stallman , Emacs developers , Stefan Monnier , Dmitry Gutov To: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 05 15:19:28 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 1jVxTq-0003vU-Ir for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 15:19:26 +0200 Original-Received: from localhost ([::1]:55020 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVxTp-0004bi-Hu for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 09:19:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVxSw-0003BI-D1 for emacs-devel@gnu.org; Tue, 05 May 2020 09:18:30 -0400 Original-Received: from pv50p00im-ztdg10011901.me.com ([17.58.6.50]:42543) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVxSv-0001lT-Ft for emacs-devel@gnu.org; Tue, 05 May 2020 09:18:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1588684708; bh=BX7sgHFI192zJoBB4mw1wjCSKg+/MvJhSWvN5Xfn6QA=; h=Content-Type:Subject:From:Date:Message-Id:To; b=mQSx/IMjCCRTUDwC04np3fFkO2uheek7ILsJbYNPcg5mvuiNRERH1uADtpN8OXjgg AxXVzfXkmhwiWNGbqhSLVqoBr+cv/MdCa4nKBp0mWqFmmSGB2TeEV7CFPvY28X8JZY DejAsMa73Hlhh47X6yUrDpgiMoLE9q/G2Z+Z+qDVm1r0TXY5uK5h1MmQN4Xdr0SK/s 1CigzRI8eQUugUETq8ANS03xDBkEHQZ8wmoMF8WOFKOVATfpbi18zfxqQZOZZV1i4s 11O5zl1Z2bwzipvKjt2rEjwkpyPacZtsKp6lOg3J0c89HbzgrzzNR0JiiE8VfC1p/a NBXExPQ21g6sg== Original-Received: from [192.168.0.2] (unknown [1.230.108.64]) by pv50p00im-ztdg10011901.me.com (Postfix) with ESMTPSA id 31208800555; Tue, 5 May 2020 13:18:24 +0000 (UTC) In-Reply-To: X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-05-05_08:2020-05-04, 2020-05-05 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=856 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2005050107 Received-SPF: pass client-ip=17.58.6.50; envelope-from=pcr910303@icloud.com; helo=pv50p00im-ztdg10011901.me.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/05 09:18:28 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, KHOP_DYNAMIC=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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:248980 Archived-At: João Távora 작성: > On Tue, May 5, 2020 at 12:58 PM Philippe Vaucher > wrote: > >> I think "all in string-" or "all in string- or multibyte-" would work >> for me. Sure, the first time you try to find "multibyte" in in >> "string-" you fail but you rapidly know that from now only multibyte >> starts with multibyte. For example your list I'd do: >> >> multibyte-string-p -> multibyte-string-p >> string-to-multibyte -> multibyte-from-string >> string-as-multibyte -> multibyte-from-string-unsafe >> set-buffer-multibyte -> buffer-set-multibyte >> multibyte-char-to-unibyte -> multibyte-char-to-unibyte > > [1] > > Do you know what this would make to fine completion list > I gave you? It would make it suck. So you, the "bit of an > extremist" who "is annoyed by a little noise", are prepared to > introduce an unimaginable amount of it into my and other's > workflows at the slightest difficulty and resistance to read > a fine manual. I like Emacs because it respects people's > established workflows, and allows for programmers > to build on it, so they can use whatever workflow they > prefer. Really? This whole mail thread’s 80% is about why just usual prefix-searching isn’t good and you should use ‘C-h ’ in order to search for a function. I can’t say that’s how it’s respecting a person’s ‘established’ workflow… I think it’s fair enough to say that Emacs is geared towards the workflow the majority of emacs-devel is used to. (Which is very different from usual Emacs users.) > Unfortunately, you're finding it a bit hard to support > your -- absolutely legitimate, mind you -- ruby-esque > ways. It’s not ruby-esque, mind you - it’s consistency, that almost every language aims to be. I can’t understand why you’re keep calling it as ‘ruby’ or something implying that it’s something new that doesn’t work with Emacs. > But you should be working to have proper > namespacing so you can work with a magnar-string.el > or ruby-regexp.el library the way you feel more > comfortable. That takes work, yes, but at least it's a > win-win, not a lose-lose. If proper namespacing takes a lot > of work, then work on a powerful completion tool. I can > help you with that. You're French, right? Imagine if > Google decided they'd to the complete works of Raymond > Roussell from French to modern, easy-to-search, French. > > João > > PS: BTW let a monkey bite me if for each of those > proposed renames you don't start a separate > 100-mail long bike-shedding war.