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:55:33 +0900 Message-ID: References: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> <02922A76-29E2-46EA-9D99-83421BAC5E43@icloud.com> 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="98257"; 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 16:05:24 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 1jVyCK-000PS0-8B for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 16:05:24 +0200 Original-Received: from localhost ([::1]:47532 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVyCJ-0005Wv-8h for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 10:05:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52898) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVy2z-0004Ga-5n for emacs-devel@gnu.org; Tue, 05 May 2020 09:55:45 -0400 Original-Received: from pv50p00im-ztdg10021901.me.com ([17.58.6.55]:49667) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVy2x-0001mA-EN for emacs-devel@gnu.org; Tue, 05 May 2020 09:55:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1588686941; bh=KrsKS/Koi4YpnIWh1MjcjASGedqkksHreXT9MK9lXx8=; h=Content-Type:Subject:From:Date:Message-Id:To; b=XbK5NYcJeGFvn03X7THVmsu5rpfmgkfBc++8gZ3Ds5QtefNwONsviNMkD7d/gMhn2 dgEvIrAuZTSMgDHwFRrl4i23teqldR5wCHeQbHpRW18OXRF44I0xGTK1CreS7wzBzV nw+ovPxK1W9PIotuQJa3i0w8bcvztWW7hi//0FGAByw+3HF/B6xQyx4xrvnzbIWmQu 18i2kL4+mjyn2Ifn6oUyom9oqAfZ1y51O4Dsyzq1Oy8Wvag1QThiRGNLT09PlARvJN fYuwJ3ivT5NdcOWhz4cmNXXJmdW6uls25bmzH2MVagvx2LxjzBoVEgRrKPTRHCg/dh b6Y1D/OIs49VQ== Original-Received: from [192.168.0.2] (unknown [1.230.108.64]) by pv50p00im-ztdg10021901.me.com (Postfix) with ESMTPSA id 9A7F8880308; Tue, 5 May 2020 13:55:37 +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=763 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2005050113 Received-SPF: pass client-ip=17.58.6.55; envelope-from=pcr910303@icloud.com; helo=pv50p00im-ztdg10021901.me.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/05 09:55:41 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:248987 Archived-At: João Távora 작성: > On Tue, May 5, 2020 at 2:18 PM 조성빈 wrote: > >>> 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. > > You're confused and should read the thread. I was not > talking about prefix-searching. My workflow doesn't use > prefix searching (anymore) I use "flex". But I haven't impinged > my workflow on other people. Well I lie. I do so on occasion, > because I think it's cool. But I'm not going to _force_ it on > other people. I’m not saying only about completion - I was thinking about things like how C-h f isn’t really useful for function finding and we should use C-h a and C-h d. And arguably emacs lisp function names are forcing us to use them. How should an Emacs user fix one’s init.el in Vim because his init.el is broken to make Emacs not work? (And let’s not say emacs -Q is the answer, because it’s just one example. Just think that he/she doesn’t want to use emacs -Q because it litters *~ files in the file system.) >> 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. > > I was answering Philippe, and he mentioned earlier that he's > a big fan of "Convention over Configuration" a philosophy > popularized in the 2000's by the RoR community. I can’t see why CoC applies here - function names aren’t ‘configuration’, right? - AFAIK CoC is something like sensible defaults which, while Emacs have a long way to get some more sensible defaults IMO, is for another thread. (BTW, while the term CoC was coined by RoR, there are various similar concepts that existed before that - it’s not something RoR has invented.) > He's also > mentioned he has done Ruby. As have I, and I have nothing > against it, quite the contrary. Pretty nice language. And I > also love the API lists and the naming consistency there. > >> Something implying that it’s something new that doesn’t >> work with Emacs. > > Quite the contrary. I'm trying to convince you that it can > work with closer to that if you work towards it without > futzing up other people's, equally legitimate, ways of > thinking about symbol names. Actually, IMO that ways of thinking symbol names should be codified and be recommended - could you help in making some emacs lisp API guidelines with that knowledge? > Hey, if Emacs had Common > Lisp, you could probably program the reader and put most > of Ruby itself in Elisp if you wanted to. Proper namespaces, > manual-extracted API lists, existing completion styles, new > completion styles. All these things would go a long way before > you take the thickest brush to a 40-year old painstakingly > crafted painting. A living painting, yes and never finished, > just like a real one, but still. > > João Távora