From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: =?UTF-8?B?YnVnIzIzOTE3OiBQbGVhc2UgY29uc2lkZXIgbWFraW5nIEJ1ZyAj?= =?UTF-8?B?MjM5MTcgYSBibG9ja2VyIGZvciAyNS4xICh3YXMgUmU6IG9yZy1jYXB0dXJl?= =?UTF-8?B?OiBDYXB0dXJlIHRlbXBsYXRlIOKAmGfigJk6IE1hdGNoIGRhdGEgY2xvYmJl?= =?UTF-8?B?cmVkIGJ5IGJ1ZmZlciBtb2RpZmljYXRpb24gaG9va3Mp?= Date: Mon, 18 Jul 2016 22:10:42 +0300 Message-ID: <83h9bm224t.fsf@gnu.org> References: <87vb066ejv.fsf@linaro.org> <8360s67qcp.fsf@gnu.org> <87bn1yyaui.fsf@linaro.org> <87mvlhmv0x.fsf_-_@moondust.awandering> <837fcl5zs9.fsf@gnu.org> <87a8hgkwcb.fsf@linaro.org> <8360s42mcb.fsf@gnu.org> <87eg6rgmlg.fsf@gmail.com> <83lh0y24y6.fsf@gnu.org> Reply-To: Eli Zaretskii Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPDxY-0004FG-UF for emacs-orgmode@gnu.org; Mon, 18 Jul 2016 15:12:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPDxY-0005IM-0P for emacs-orgmode@gnu.org; Mon, 18 Jul 2016 15:12:08 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: (message from John Wiegley on Mon, 18 Jul 2016 12:04:11 -0700) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: John Wiegley Cc: 23917@debbugs.gnu.org, rpluim@gmail.com, alex.bennee@linaro.org, monnier@iro.umontreal.ca, nljlistbox2@gmail.com > From: John Wiegley > Cc: Robert Pluim , Stefan Monnier , 23917@debbugs.gnu.org, alex.bennee@linaro.org, nljlistbox2@gmail.com > Date: Mon, 18 Jul 2016 12:04:11 -0700 > > >>>>> Eli Zaretskii writes: > > > My suggestion to fix this is below. I ask for opinions on (1) whether this > > looks like TRT, (2) whether it is safe enough for emacs-25, and (3) whether > > someone has better ideas. > > I didn't even know match-data took arguments, so I defer to your judgment on > this issue, Eli. Neither did I, but I've read the code through which I stepped ;-)