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?Sm/Do28gVMOhdm9yYQ==?= Newsgroups: gmane.emacs.devel Subject: Re: Imports / inclusion of s.el into Emacs Date: Tue, 5 May 2020 21:42:03 +0100 Message-ID: References: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000ce219a05a4ecae77" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="88812"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Richard Stallman , Emacs developers , Stefan Monnier , =?UTF-8?B?7KGw7ISx67mI?= , Dmitry Gutov , Eli Zaretskii , Drew Adams To: Philippe Vaucher Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 05 22:42:52 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 1jW4Ox-000N0d-Rk for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 22:42:51 +0200 Original-Received: from localhost ([::1]:49568 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jW4Ow-00016O-Pg for ged-emacs-devel@m.gmane-mx.org; Tue, 05 May 2020 16:42:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48072) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jW4OQ-0000bg-FL for emacs-devel@gnu.org; Tue, 05 May 2020 16:42:18 -0400 Original-Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]:37821) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jW4OP-0008Vt-H1; Tue, 05 May 2020 16:42:18 -0400 Original-Received: by mail-il1-x135.google.com with SMTP id n11so120331ilj.4; Tue, 05 May 2020 13:42:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NQyvnXbOcPRf0SazePcKs8Ql6viRgLNxsVybXXCFDfk=; b=n/1CDejs3WIQlmouPiQXNgc+TolCIZH84feYBRGKhJGV8fjoIf4PTm5lUWzzVph6vJ XqfS7TZ7FbyvXgp3iHafIWzOu8MWh5rF9wsWK9ukNCB+Zc63zLQlEKD4SoWm12MT1N3u 8+8n29nvFSge1lpL2dmCjZ1N8wdNL45zkmrq/xDRrJX0v4o8/cqUYj7d+oey+U2EFJji oHRV6xNmjAR8HN4rjeBm4QUZJfSFRam6BOQz0Sm8/5UxbMswpKeKY/H1WKh6+OU32ChN xARo+ZOEacXgGXnYhm34DUhHOLccIWCMQKMLzH4tVaCOHQQaPflqAjkdiB1A03LC37Ac bhtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NQyvnXbOcPRf0SazePcKs8Ql6viRgLNxsVybXXCFDfk=; b=CgJPoxC/G7Tv0bsF6njg6Z8TR+gEkZ+cx8fJYqt3CtrXmFgqG6hgGNn0a3OUeqOaec x7YGfvaNLWaoomLAh7vRdxmTwz7zLWNsXu7ddhDGco6oOuK11h55bXjy00LLzL5iuXlT TtsEuh7j3wAfENA1a/VG1pIJTd1hrnnQSd2bOS4Dh0xAOC+/lwS+NEkMuofAzjmGZ7US 0OYRuvaV2wWS0vHdnjoQLO9++t6rGACFfS16J9YvLcI1eCTOhqFJgXZtbNQCLUW5qr/f BFSqjXJ6ndDngfGNKi8YosodTCli3EpXY/7vwJ66IxfebZTaWJNk9oC+Z2YqQujvllR5 A1dA== X-Gm-Message-State: AGi0Pua2AIaK0O0vx7Qy46xjYCkOEGVtLtIWTLrWLMlCHP02PlR5nrVq 102dzpCpV65Xd6D0s/nT0HlwcKWALLYd+1umqhg= X-Google-Smtp-Source: APiQypJP0Hc3nshizamAmaVz8cIjx1Bcu49Ws5vxkE0zFcDVKE5oeEoN1+QJQSi1nGMlXrpgM1xpyvY0zEg6Y6yjloM= X-Received: by 2002:a92:858b:: with SMTP id f133mr5072952ilh.97.1588711335533; Tue, 05 May 2020 13:42:15 -0700 (PDT) In-Reply-To: Received-SPF: pass client-ip=2607:f8b0:4864:20::135; envelope-from=joaotavora@gmail.com; helo=mail-il1-x135.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 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_FROM=0.001, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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:249039 Archived-At: --000000000000ce219a05a4ecae77 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, May 5, 2020 at 8:59 PM Philippe Vaucher wrote: > > Sure that's worth it? Wouldn't you rather work on namespaces? The two > > issues intersect! > > Out of curiosity, say "real" namespaces land in Emacs, do you reckon > we'd be able to agree on reasonably well-defined topics? > Sure, I think so. If they were here today, you could have the s.el library under the "modern-string" namespace or "magnar-string" namespace or something like that. I don't see it'd be contentious. In your library, you could then somehow indicate you'd like to use the "magnar-string" namespace and have access to what is now "magnar-string-empty-p" under just "empty-p". Or maybe you'd prefer to indicate you want to use the "magnar-string" namespace under the "s-" local nickname. Then you can type "s-empty-p" as you're used to. Same thing with dash.el that so many people like. Some parts of what is not yet in a namespace can be moved to a proper namespace with no breakage. So someone working a lot with a properly named lib today, say, "package.el" could -- locally -- access all those functions without the "package-" suffix. You could request completion for symbols in a space or maybe only "external" symbols in a space. The problem is rather agree on the form that this namespace system should take. There are many ways, all have advantages and disadvantages. From a purely cosmetic one to full-featured CL packages. See the other thread. --=20 Jo=C3=A3o T=C3=A1vora --000000000000ce219a05a4ecae77 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, May 5, 2020 at 8:59 PM Philippe Vaucher <philippe.vaucher@gmail.com> = wrote:
> Sure that's worth it? Wouldn't you rather work on = namespaces? The two
> issues intersect!

Out of curiosity, say "real" namespaces land in Emacs, do you rec= kon
we'd be able to agree on reasonably well-defined topics?

Sure, I think so.=C2=A0 If they were here today, you = could have
the s.el library under=C2=A0 the "modern-string&q= uot; namespace
or "magnar-string" namespace or somethin= g like that. I don't
see it'd be contentious. In your lib= rary, you could then somehow
indicate you'd like to use the &= quot;magnar-string" namespace
and have access to what i= s now "magnar-string-empty-p"
under just "empty-p&= quot;. Or maybe you'd prefer to indicate
you want to use the = "magnar-string" namespace under
the "s-" loca= l nickname.=C2=A0 Then you can type "s-empty-p"
as= you're used to. Same thing with dash.el that so many
people = like.

Some parts of what is not yet in a names= pace can be
moved to a proper namespace with no breakage.=C2=A0 S= o
someone working a lot with a properly named lib
=
today, say, "package.el" could -- locally -- access all
=
those functions without the "package-" suffix.=C2=A0 <= br>

You could request completion for symbols in a = space
or maybe only "external" symbols in a space.

The problem is rather agree on the form that this
namespace system should take.=C2=A0 There are many ways,
al= l have advantages and disadvantages. From a purely
cosmetic one t= o full-featured CL packages. See the other
thread.

=
--
Jo=C3=A3o T= =C3=A1vora
--000000000000ce219a05a4ecae77--