From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch* Date: Sat, 18 May 2024 08:33:23 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="596"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 60450@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 18 08:35:06 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s8Der-000AYt-PF for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 May 2024 08:35:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s8Dem-0006JO-UX; Sat, 18 May 2024 02:35:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s8Del-0006Ig-Eo for bug-gnu-emacs@gnu.org; Sat, 18 May 2024 02:34:59 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s8Del-0005pq-6k for bug-gnu-emacs@gnu.org; Sat, 18 May 2024 02:34:59 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s8Deo-0003NU-EB for bug-gnu-emacs@gnu.org; Sat, 18 May 2024 02:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 May 2024 06:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60450 X-GNU-PR-Package: emacs Original-Received: via spool by 60450-submit@debbugs.gnu.org id=B60450.171601407612957 (code B ref 60450); Sat, 18 May 2024 06:35:02 +0000 Original-Received: (at 60450) by debbugs.gnu.org; 18 May 2024 06:34:36 +0000 Original-Received: from localhost ([127.0.0.1]:59610 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s8DeN-0003Mv-N5 for submit@debbugs.gnu.org; Sat, 18 May 2024 02:34:35 -0400 Original-Received: from mail-wr1-f54.google.com ([209.85.221.54]:48205) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s8DeL-0003Mm-Ql for 60450@debbugs.gnu.org; Sat, 18 May 2024 02:34:34 -0400 Original-Received: by mail-wr1-f54.google.com with SMTP id ffacd0b85a97d-351ae94323aso661004f8f.0 for <60450@debbugs.gnu.org>; Fri, 17 May 2024 23:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716014004; x=1716618804; darn=debbugs.gnu.org; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=SZ2V12GNswFx+Iyi41Tj2nusqW0ObNS2ynLAWhhSDqk=; b=UUJ6u1/uX09VU69a2SbADg1RcNxO2CBz7D96oUrAX1nFwiNnUcm6TXTSuDgSqgXLCd Ky2sRVSAlnb5gA3NqlW3RAt11Uq1CySVttMGLXbbbTOm0Pe0i1MvWFxX7ZMxoxhE9Shh wEfbGDFtk0Toxca29APG7nzUpkCyVDGYVQX4FLu11W630hvBRIsqtUmVKRG8hN/rct/c 1j7JexqdVFC4vIvinuRzK3wdMWgKCfceYtZnb9hUd5XxkbstlvD7u27kbwL07ugbsWjJ q/S8qVUxo1yQlCyUCiBchhe+4U8DfUUi5eltzYAw1Ev3enwjteEl9H604ilgsRwf4bst FlUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716014004; x=1716618804; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=SZ2V12GNswFx+Iyi41Tj2nusqW0ObNS2ynLAWhhSDqk=; b=SyOz7HvEmxrJ9mlmywO0O8vyZsvPmSx/LXLU8tOoYp+N6aYqYwOG40u8vC8K+YjHY4 u1U7qvCcJIEo6zCN11PEOUA0nNWcTQljpoknBaHNjlEIdHFAvc2GX2rnCJFs91h1/vI3 v1681CSTNHrp4yYlxsevoj126Vsu7tqnFfniZIHS52268b91IE9T8TL8Xb7UXM7eYCSV fzbiKfjjFb9fifsX7mMMYM8dGLLO/l+hiXqxjRXPF8gIZdZ4HAPIWCYujisk6ULQixiH lpprZB5J149QK0zPethHz8FRkRQJZCQK2TQ1NO1w4YKX4ERf8Amv7WpbGZfvIP/CjnED aDFA== X-Gm-Message-State: AOJu0YzK3jrN8fDbp045g3dA7a3jqipVWC0FSTKz3I/KWja8aryi2O5N ikG/1XwDBSeU+m4lzKln0eWvY2cecgM0OcNBiQf6nltPzITnCrHTyIXPqg== X-Google-Smtp-Source: AGHT+IFWD+QGYWxNafgOrnPXQ9oM6lpMpltrZcSeUFiZOYlOrzhIeSNkvBgLyX6mAnJpF1M/6GveOA== X-Received: by 2002:adf:e501:0:b0:34d:8c1f:3194 with SMTP id ffacd0b85a97d-3504a7375b0mr16494033f8f.35.1716014004494; Fri, 17 May 2024 23:33:24 -0700 (PDT) Original-Received: from pro2.fritz.box (pd9e36a11.dip0.t-ipconnect.de. [217.227.106.17]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3502b79bc3bsm23302308f8f.13.2024.05.17.23.33.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 17 May 2024 23:33:24 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Mon, 08 May 2023 08:25:41 -0400") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:285282 Archived-At: Stefan Monnier writes: >> The doc string of cl-define-compiler-macro says >> "This is like =E2=80=98defmacro=E2=80=99, but macro expansion occurs o= nly if the call to >> FUNC is compiled (i.e., not interpreted)." > > `cl-define-compiler-macro` is built on top of the "new" ELisp compiler > macro feature. I think that feature is documented vaguely (poorly?) > enough that it does allow expansion (or not) for interpreted code. > >> C-j is bound to eval-print-last-sexp, which I wouldn't expect to compile >> anything, and its doc string doesn't mention anything AFAICS. Not sure = if >> that's a bug in the code or something missing in the docs. > > Trying to distinguish those calls to `macroexpand-all` which come from > the compiler from those that come from elsewhere doesn't seem worth the > trouble, so I'd rather consider it as a doc bug. > > The doc should also make it clear that contrary to `defmacro` there is > no guarantee that it will be called (nor *when* it's called). I don't think that this will be changed, so I'm closing this bug.