From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?Sebasti=C3=A1n_?= =?UTF-8?Q?Mon=C3=ADa?= Newsgroups: gmane.emacs.bugs Subject: bug#34842: 26.1; Alist documentation: let-alist Date: Thu, 14 Mar 2019 04:47:05 +0000 Message-ID: References: > <3c296021-c231-4c62-b8e3-0e870cb224cc@default> , <1fa49979-2e67-44bd-86cd-080bb9f7e1de@default> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_BN8PR04MB5555A6BF2B41241F94807CAA8B4B0BN8PR04MB5555namp_" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="186390"; mail-complaints-to="usenet@blaine.gmane.org" To: "34842@debbugs.gnu.org" <34842@debbugs.gnu.org> Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Mar 14 05:48:14 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h4IHt-000mOJ-OU for geb-bug-gnu-emacs@m.gmane.org; Thu, 14 Mar 2019 05:48:13 +0100 Original-Received: from localhost ([127.0.0.1]:56773 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4IHs-0003d2-FY for geb-bug-gnu-emacs@m.gmane.org; Thu, 14 Mar 2019 00:48:12 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:54967) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h4IHm-0003cu-4U for bug-gnu-emacs@gnu.org; Thu, 14 Mar 2019 00:48:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h4IHl-0003nN-4H for bug-gnu-emacs@gnu.org; Thu, 14 Mar 2019 00:48:06 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57414) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h4IHk-0003n1-CM for bug-gnu-emacs@gnu.org; Thu, 14 Mar 2019 00:48:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h4IHi-0005xT-H8 for bug-gnu-emacs@gnu.org; Thu, 14 Mar 2019 00:48:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Sebasti=C3=A1n_?= =?UTF-8?Q?Mon=C3=ADa?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 14 Mar 2019 04:48:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 34842 X-GNU-PR-Package: emacs Original-Received: via spool by 34842-submit@debbugs.gnu.org id=B34842.155253883522848 (code B ref 34842); Thu, 14 Mar 2019 04:48:02 +0000 Original-Received: (at 34842) by debbugs.gnu.org; 14 Mar 2019 04:47:15 +0000 Original-Received: from localhost ([127.0.0.1]:42725 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h4IGw-0005wR-GL for submit@debbugs.gnu.org; Thu, 14 Mar 2019 00:47:14 -0400 Original-Received: from mail-oln040092005032.outbound.protection.outlook.com ([40.92.5.32]:59798 helo=NAM02-SN1-obe.outbound.protection.outlook.com) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1h4IGu-0005wB-PI for 34842@debbugs.gnu.org; Thu, 14 Mar 2019 00:47:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rwr1SSUAJs1QOcj8x9MhZLR9bh9tNPbuK9GI0naMkg8=; b=FrahAQ5yr8QpwjnJvJTrwo/GHs0RPbzPewmNLSrRgzJIULL/4yXAaXeuXwXyJXM4qHCYhwobY7zf+/Gg+yMaiTPddV8+ZxkU23UZ3yif8rEPNcLbmSjjVRGbZ3hZ7vtqfu+LlDepk5/a7WXq3XSmcwxcZTB7LuCyiOdRfmgCGURo7Js9qPn5KQ5c2bAQGaoIAsJGuN8gnj37FbWS5ZaCkafT/djDb4Gfvyrml73KkD86pF5A1P0FkeX6duGCL+/hrmzfzszGdDRv4Z4Wj+9hOGs6l6Pg5bek3NsTEeA9HD9M8249M+EqbI2Heh5I5gKQ7i06dBoXzOvlJuZUCemhXA== Original-Received: from BL2NAM02FT056.eop-nam02.prod.protection.outlook.com (10.152.76.56) by BL2NAM02HT174.eop-nam02.prod.protection.outlook.com (10.152.77.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.19; Thu, 14 Mar 2019 04:47:05 +0000 Original-Received: from BN8PR04MB5555.namprd04.prod.outlook.com (10.152.76.56) by BL2NAM02FT056.mail.protection.outlook.com (10.152.77.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.19 via Frontend Transport; Thu, 14 Mar 2019 04:47:06 +0000 Original-Received: from BN8PR04MB5555.namprd04.prod.outlook.com ([fe80::890f:1d5c:65a6:f0d3]) by BN8PR04MB5555.namprd04.prod.outlook.com ([fe80::890f:1d5c:65a6:f0d3%3]) with mapi id 15.20.1686.021; Thu, 14 Mar 2019 04:47:05 +0000 Thread-Topic: bug#34842: 26.1; Alist documentation: let-alist Thread-Index: AQHU2WfoQNkpN7Cxwka7S9tpV8PRbKYJrKYAgAAUn+uAABa5AIAAtyOc In-Reply-To: <1fa49979-2e67-44bd-86cd-080bb9f7e1de@default> Accept-Language: en-US Content-Language: en-US x-incomingtopheadermarker: OriginalChecksum:971221099B9269B35864B760771A12C92C03C3AE66E1E7998F7A42D04B05CB10; UpperCasedChecksum:CEB0FD8A312FBA73130F8E0381014D3CC17650EF2052CC2F9F28C71B6D99FC52; SizeAsReceived:7049; Count:44 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [j1LfxDLN5BMe+r/hC9k4ZA9/fUslgIxW] x-ms-publictraffictype: Email x-incomingheadercount: 44 x-eopattributedmessage: 0 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031322404)(2017031323274)(2017031324274)(1601125500)(1603101475)(1701031045); SRVR:BL2NAM02HT174; x-ms-traffictypediagnostic: BL2NAM02HT174: x-microsoft-antispam-message-info: eEbOHvMONu2lRCI/jYoqSTqcuK4BiGInb4uA1O7gArjdQu5zjMscdDh2gEO2da99 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 28f9957e-9f81-4ad1-7c27-08d6a8381be3 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Mar 2019 04:47:05.8261 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2NAM02HT174 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:156316 Archived-At: --_000_BN8PR04MB5555A6BF2B41241F94807CAA8B4B0BN8PR04MB5555namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I think when it says nested let-alist uses, it refers to the fact that let-= alist automatically went to the next level of depth to provide a binding fo= r .title Without that feature you would need a second let-alist: (let-alist .company= # more code here) Sorry for the lack of formatting I'm on mobile. Hope that made sense! --------------------------------------------------- Why Emacs? http://david.rothlis.net/emacs/why.html From: Drew Adams Sent: Wednesday, March 13, 11:51 AM Subject: RE: bug#34842: 26.1; Alist documentation: let-alist To: Sebasti=E1n Mon=EDa, 34842@debbugs.gnu.org Thanks for filing the bug, BTW. > I thought that the example in the docstri= ng was > too long compared to the smaller/simpler examples > in the rest of= the page, but wouldn't be against > using that instead if it's more clear.= The example could be shorter, yes. But it needs to be correct and show wha= t `let-alist' does. > The nested access example is in .site.contents, But t= he doc talks about nested uses of `let-alist'. There is only one `let-alist= ' in the example that the doc claims shows the behavior of nesting `let-ali= st'. --_000_BN8PR04MB5555A6BF2B41241F94807CAA8B4B0BN8PR04MB5555namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I think when it says nested let-alist uses, it refers to the fact that let-= alist automatically went to the next level of depth to provide a binding fo= r .title

Without that feature you would need a second let-alist: (let-alist .company= # more code here)

Sorry for the lack of formatting I'm on mobile. Hope that made sense!

---------------------------------------------------
Why Emacs? 



From: Drew Adams
Sent: Wednesday, March 13, 11:51 AM
Subject: RE: bug#34842: 26.1; Alist documentation: let-alist
To: Sebasti=E1n Mon=EDa, 34842@debbugs.gnu.org


Thanks for filing the bug, BTW. > I thought that the example in the docs= tring was > too long compared to the smaller/simpler examples > in th= e rest of the page, but wouldn't be against > using that instead if it's= more clear. The example could be shorter, yes. But it needs to be correct and show what `let-alist' does. > The nested= access example is in .site.contents, But the doc talks about nested uses o= f `let-alist'. There is only one `let-alist' in the example that the doc cl= aims shows the behavior of nesting `let-alist'.

--_000_BN8PR04MB5555A6BF2B41241F94807CAA8B4B0BN8PR04MB5555namp_--