From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: dabbrev-expand should escape kbd macros, shouldn't it? Date: Wed, 17 Jul 2019 17:39:46 +0000 (UTC) Message-ID: <4d9496fd-5287-47af-af6b-875d4308af4e@default> References: <4ea4470ad1919b2f1915d6ec77f7d2b8.squirrel@dancol.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="100651"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Andreas Schwab , Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 17 19:40:13 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 1hnnuX-000Q4U-MM for ged-emacs-devel@m.gmane.org; Wed, 17 Jul 2019 19:40:13 +0200 Original-Received: from localhost ([::1]:59362 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnnuW-0001pE-8N for ged-emacs-devel@m.gmane.org; Wed, 17 Jul 2019 13:40:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42664) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnnuN-0001jO-S1 for emacs-devel@gnu.org; Wed, 17 Jul 2019 13:40:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnnuM-0000aH-Vi for emacs-devel@gnu.org; Wed, 17 Jul 2019 13:40:03 -0400 Original-Received: from userp2120.oracle.com ([156.151.31.85]:40426) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hnnuM-0000Zl-NF for emacs-devel@gnu.org; Wed, 17 Jul 2019 13:40:02 -0400 Original-Received: from pps.filterd (userp2120.oracle.com [127.0.0.1]) by userp2120.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x6HHSo2L065183; Wed, 17 Jul 2019 17:39:51 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=Sx/HBlTKIsgrKNPLmIeU8ie8awH0fKMU5HWd6mIsCx8=; b=T1EM2u4M24MZ6d9Ima1hkzxpuUbVoe0qkc+tZWQJZLiXGYE3mF0SqbDf4slHi0NDNDQ4 7N+3DXA5KSQKOHVpwTkJo7R2q9skR5decMgRSyzB0X7cgcbs1Fa2N40iPA0qbdjwv5Pa ErBeSIBbjPTcK2SeqWyfWmFiWHGcQBgbJVpKkLiny4eI8ENh/80pYwIpQDzSzxsYjc4M EGQRGS8hqtenTvAMDDB52w0DT1M/6rHdA6mYDsMFAE1kWvKNoBMKeDXa+vIOTUB/KtZp 8ggiLgcEwrJVnqpPNn6yQ3/5y9DwNvEANfBfTCfRPxp3jLiOFs+Om8pXcsBnLOiHnnz9 4w== Original-Received: from userp3030.oracle.com (userp3030.oracle.com [156.151.31.80]) by userp2120.oracle.com with ESMTP id 2tq7xr4ay8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 17 Jul 2019 17:39:51 +0000 Original-Received: from pps.filterd (userp3030.oracle.com [127.0.0.1]) by userp3030.oracle.com (8.16.0.27/8.16.0.27) with SMTP id x6HHRo7b082940; Wed, 17 Jul 2019 17:39:51 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userp3030.oracle.com with ESMTP id 2tt77h95ce-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 17 Jul 2019 17:39:50 +0000 Original-Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id x6HHdlY5032220; Wed, 17 Jul 2019 17:39:49 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4861.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9321 signatures=668688 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=923 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907170202 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9321 signatures=668688 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=978 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907170202 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 156.151.31.85 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:238618 Archived-At: > > 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 r= un > > 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? >=20 > 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 the= ir > binding). +1 A keyboard macro is essentially a command. You generally want to be able to replay a keyboard macro (keystrokes) in various contexts. You generally do not want to capture the original context as part of the macro.