From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Andreas Schwab Newsgroups: gmane.emacs.devel Subject: Re: dabbrev-expand should escape kbd macros, shouldn't it? Date: Wed, 17 Jul 2019 17:52:26 +0200 Message-ID: References: <4ea4470ad1919b2f1915d6ec77f7d2b8.squirrel@dancol.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="179591"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2.90 (gnu/linux) Cc: emacs-devel@gnu.org To: "Daniel Colascione" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 17 17:52:41 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hnmES-000kaV-OP for ged-emacs-devel@m.gmane.org; Wed, 17 Jul 2019 17:52:41 +0200 Original-Received: from localhost ([::1]:58596 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnmER-0007oE-BT for ged-emacs-devel@m.gmane.org; Wed, 17 Jul 2019 11:52:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37237) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnmEI-0007o8-MX for emacs-devel@gnu.org; Wed, 17 Jul 2019 11:52:31 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnmEH-0004kY-K9 for emacs-devel@gnu.org; Wed, 17 Jul 2019 11:52:30 -0400 Original-Received: from mx2.suse.de ([195.135.220.15]:60018 helo=mx1.suse.de) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hnmEH-0004jV-EA for emacs-devel@gnu.org; Wed, 17 Jul 2019 11:52:29 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Original-Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 88541AF8F; Wed, 17 Jul 2019 15:52:27 +0000 (UTC) X-Yow: Will the third world war keep ``Bosom Buddies'' off the air? In-Reply-To: <4ea4470ad1919b2f1915d6ec77f7d2b8.squirrel@dancol.org> (Daniel Colascione's message of "Wed, 17 Jul 2019 08:13:05 -0700") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 195.135.220.15 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:238617 Archived-At: On Jul 17 2019, "Daniel Colascione" wrote: > Right now, if you record a kbd macro and hit M-/, the act of hitting M-/ > is recorded like any other command in the kbd macro. On replay, we'll run > dabbrev-expand. The problem is that dabbrev-expand produces radically > different results depending on buffer context, making macro replay > unpredictable. Should the *result* of dabbrev-expand just get put into the > kbd macro instead? How is that different from any other key that is part of the macro? The point of a kbd macro is to record keys, not their effect (or even their binding). Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."