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: Wed, 6 May 2020 01:47:04 +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="89893"; 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 18:48:39 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 1jW0kJ-000NGH-3t for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 18:48:39 +0200 Original-Received: from localhost ([::1]:38774 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jW0kI-0006Zr-37 for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 12:48:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34032) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jW0j1-00066X-Tv for emacs-devel@gnu.org; Tue, 05 May 2020 12:47:20 -0400 Original-Received: from pv50p00im-zteg10011501.me.com ([17.58.6.42]:37373) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jW0iz-0007y6-26 for emacs-devel@gnu.org; Tue, 05 May 2020 12:47:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1588697231; bh=2BfEGngdEAwcApbYhZ7S7gzIslGYG0Klara8Tr7yBJE=; h=Content-Type:Subject:From:Date:Message-Id:To; b=VWoVdfj1qFunZ3DZDli6p3+KfgrDi2MnfWOy4dYBYD4YKy6jjIgqp48ODCB7pG83+ lIT94TanbYWO3Y4JWCz98zWsjmsKSUwxgACW+qt42jDPF4+p82F+9vkyjFIMx3mwfl fHKMFeFBkIMPR/FBAdJbFYSxL8mOWFZ4Vp6Fc1FCyVuHY8ZeZi/DDdJeVPWGgAzcVv 6hO5N2SHyxyer09h2LmKv3SjTcAWLI3fms4DiYvjIpf4t2/uxpX4m2eoy8mMz8ifkb asgebwsmPkOgGb6IjMLoAcftevvx+AWVEOhB3LkEFYZXFR849AnS4hpq2AP8TrZl6j JmY743XsCmibg== Original-Received: from [192.168.0.2] (unknown [1.230.108.64]) by pv50p00im-zteg10011501.me.com (Postfix) with ESMTPSA id 01940B00641; Tue, 5 May 2020 16:47:08 +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_09: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=770 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2005050130 Received-SPF: pass client-ip=17.58.6.42; envelope-from=pcr910303@icloud.com; helo=pv50p00im-zteg10011501.me.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/05 12:47:12 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:249013 Archived-At: João Távora 작성: > On Tue, May 5, 2020 at 2:55 PM 조성빈 wrote: > >> 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. > > But I'm saying it _is_ useful. It IS useful to me. With flex. Yes, that’s true, but flex, while is super useful (and I’m grateful to you developing it), is still a hack that exists because the function names don’t have good rules. (Why should everybody use flex, just to find functions?) > And > your proposal will make it much less useful, and that's bad. >>> 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? > > No, but using `(setq completion-styles 'flex)` is. A pretty useful > bit of it too. Maybe you try it for a while? It works with Company, > completion-at-point and, theoretically, with a new version of Helm. In fact, I already use it - I use flex for both Company & Helm, it’s wonderful. (As I have said already) Thanks for flex-completion, it’s super useful to me. However, IMO the fact that you can now search functions in C-h f a bit easily doesn't mean that the functions can be less consistent. > You can also try M-x fido-mode. > > Anyway, CoC is what Phillipe brought up, not me. It's a RoR thing, > and I was answering him. Oh, I might have missed that. Sorry. > And Convention is pretty good, sure, > when you're starting from scratch. So in your next new language, > by all means, use the Best Convention (TM). > >>> 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? > > For new domains, surely? ------------------------------------------------------------------------------ Well, Elisp will gain some more core APIs in the future, so I was thinking about that, but except from package prefixes, wouldn’t it be similar? > Like washing-machines.el or > little-green-men.el? Sure, I can do that. I have my own > conventions on how to name things (and they've changed > over the years, a lot, and they will probably change until > I'm dead. I wouldn't recommend putting a lot of weight in > them, though. You can check my latest packages, like > eglot.el or jsonrpc.el to see how I name things. How do you think about this: > I think some preliminary conventions that Elisp already follows is that the > - scheme is for actions on the object like rename-file or > clear-string, and - scheme is for getting properties of > the > object like string-width and file-name-extension. (I’m not considering > polymorphic ones.) > > But then there are exceptions, like string-trim (which should then be > trim-string) or string-join (which should then be join-string). > João