From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Should `get-file-buffer' be implemented in Elisp? Date: Sun, 16 Jul 2023 22:10:03 +0300 Message-ID: <83cz0r8ygk.fsf@gnu.org> References: <87pm4r1z03.fsf@localhost> <83fs5n8zaz.fsf@gnu.org> <87mszv1xur.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6255"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 16 21:10:37 2023 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 1qL78f-0001Tu-7u for ged-emacs-devel@m.gmane-mx.org; Sun, 16 Jul 2023 21:10:37 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qL78A-0003l8-JB; Sun, 16 Jul 2023 15:10:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qL787-0003kw-Hq for emacs-devel@gnu.org; Sun, 16 Jul 2023 15:10:04 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qL785-0003hT-7E; Sun, 16 Jul 2023 15:10:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=D4+LjxlJ3o9VfVTaEDPGlLsdOD/mEU+HEJSWPmO09hc=; b=NLDhiZYHjlEl FTBBRI8pweJCVgcJsQjsLYhqGIUiNBtIDThsoju6DiAdXjW7odo/hz7E8RNwpofRwyQtxIWr2kK2Q Bd6mkcBax5PdGzA1mR8Ll5dHCu537adLvYprWKH178K6a37NyvSNd2AF0oQnWuSGS9UCYeGytvo3e iPC5V7FWsD6ooBUn0VY6pHbmfice3zV8txrm1u9KN3cNci3S4bLN+yEbs2g8CMPt/LN80on1Hi6k7 CCUmTmc4k6Zmn6T0bfMLGlhgsxOUDiruaHfaI19gEJbtpZGrFvB8iN42OQWY0NcYhMsx6vxV3rLna fu33UVMbf6ZlRu4DAVrQDg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qL77l-00048R-SK; Sun, 16 Jul 2023 15:09:52 -0400 In-Reply-To: <87mszv1xur.fsf@localhost> (message from Ihor Radchenko on Sun, 16 Jul 2023 19:05:00 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:307901 Archived-At: > From: Ihor Radchenko > Cc: emacs-devel@gnu.org > Date: Sun, 16 Jul 2023 19:05:00 +0000 > > Eli Zaretskii writes: > > >> AFAIU, we generally aim to move C functions to Elisp. > > > > Only when there's a good reason to do so. > > Interesting. > Then, my memory is failing me. I recall being told on emacs-devel that > the general direction is to have as many things as possible in Elisp and > reduce the C core. > > I stay corrected. No need to stand corrected: the key is the interpretation of "as many as possible" -- it is not as simplistic as perhaps it could be. Basically, we have enough good reasons to rock the boat and make changes which could as side effects introduce bugs and subtle behavior change; let's not risk that when we don't have such a good reason.