From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Pogonyshev Newsgroups: gmane.emacs.devel Subject: Re: (unknown) Date: Sun, 19 Mar 2017 20:36:21 +0100 Message-ID: References: <87k27ljcv2.fsf@holos> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1489952191 15721 195.159.176.226 (19 Mar 2017 19:36:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 19 Mar 2017 19:36:31 +0000 (UTC) Cc: Emacs developers To: Mark Oteiza Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 19 20:36:26 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cpgcp-0003Mt-R2 for ged-emacs-devel@m.gmane.org; Sun, 19 Mar 2017 20:36:23 +0100 Original-Received: from localhost ([::1]:57832 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cpgcv-0005BG-Pr for ged-emacs-devel@m.gmane.org; Sun, 19 Mar 2017 15:36:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34718) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cpgcq-00059j-0F for emacs-devel@gnu.org; Sun, 19 Mar 2017 15:36:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cpgcp-0000qn-D0 for emacs-devel@gnu.org; Sun, 19 Mar 2017 15:36:24 -0400 Original-Received: from mail-pf0-x233.google.com ([2607:f8b0:400e:c00::233]:33009) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cpgcp-0000qe-5k for emacs-devel@gnu.org; Sun, 19 Mar 2017 15:36:23 -0400 Original-Received: by mail-pf0-x233.google.com with SMTP id e129so18046257pfh.0 for ; Sun, 19 Mar 2017 12:36:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0VpkoXI+7Hq2SMCUq3wAAk75z5HP4xF4j8v4gk/Fa6c=; b=ktqDZK/dYBWIwUH6X5f7z52svdF0fC1y81pZJ14M8RUaKnwWlbpNzPt+0N8FRsLZtp O5SJdzCJWKYAOj2G/jRT3VbxztRf5nFCC47okSaWytZ26qBXdb1A1wh58CZ0eiQ+jG09 /zh0ptxfzoJ+nn/wSghQZc4taazN+9jTl66Eb5xBxJl9b/Q5c6ZAjoWAiRT7ATZWZUEI mzSTzaNclhGKENOBp1ZfgRRf0Kqd1xVtZ8ZDMJJAQzoglWcgNuAJhNQSXjjmqH4S3vqU OD5oOUWgQRhgypvyHkLcCHFgLtBkAYFgNCeSK+7ocMEdEKrREYJVj2c0ei8tW+TjGcsc DwNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0VpkoXI+7Hq2SMCUq3wAAk75z5HP4xF4j8v4gk/Fa6c=; b=CyQpItHjqWMhe3YNgD3O/ZESUgMISwSW78uoxp1FoJd2hU7ex6dYf6mjh9kmtiGPvs pFc9Fvy1O/7E2DW86EPSe/QE4bLSDIokQ0Uyyx6e+Fw6+xHNa7mf1fOcVgFAJkqozt0P q8kR52CcwGVensJz6FfzlOBjxmL+ER9tTNyNgOthUnA6ZGfo3gi2rFKnnCChDLNMKqBS iWBM7wTJk5yw3wnijd2p3znJRT8lGY6ry3KKe6E7LepFsHx6v9zjEh1Gn9kno1in7Vpt ToTG8HbCaV4BFR62e+1+CRF5Yo6JtwFzbk3egTc43omYRyacjW8tzELxHyqOxUGOT3lY G1DA== X-Gm-Message-State: AFeK/H1FSx7Q9U8O2ox2TN6aoHL0lbzVPfX46JSrW5yC/PFrUoDY9MZAzkh88bjRHegFZPbp25HEEIn/t6PHnw== X-Received: by 10.84.148.134 with SMTP id k6mr35284929pla.128.1489952182163; Sun, 19 Mar 2017 12:36:22 -0700 (PDT) Original-Received: by 10.100.138.13 with HTTP; Sun, 19 Mar 2017 12:36:21 -0700 (PDT) In-Reply-To: <87k27ljcv2.fsf@holos> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400e:c00::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:213165 Archived-At: >> I would just be glad if someone applied the patch from bug 26068. It's a >> fix, not an optimization, and there is example of a form, evaluation of >> which it fixes. > > Applied, thanks. AFAICT it didn't break any tests and didn't exacerbate > bug#12119 which the previous code was fixing. Thank you. If you are familiar with the code involved, can you please also look at bug 26073? It's related, but more difficult to fix. I added a patch to the bug report, but I don't think the patch is ready for application. Maybe someone could finish it. Paul