From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: How do I find out, in a Lisp program, what is the current buffer? Date: Tue, 5 Dec 2023 15:20:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14744"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eshel Yaron Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 05 16:21:25 2023 Return-path: Envelope-to: ged-emacs-devel@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 1rAXEi-0003dZ-Gc for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Dec 2023 16:21:24 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rAXDv-000473-CS; Tue, 05 Dec 2023 10:20:35 -0500 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 1rAXDs-000460-0q for emacs-devel@gnu.org; Tue, 05 Dec 2023 10:20:32 -0500 Original-Received: from mail.muc.de ([193.149.48.3]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rAXDp-0004QR-Dz for emacs-devel@gnu.org; Tue, 05 Dec 2023 10:20:31 -0500 Original-Received: (qmail 61784 invoked by uid 3782); 5 Dec 2023 16:20:23 +0100 Original-Received: from acm.muc.de (pd953a0d8.dip0.t-ipconnect.de [217.83.160.216]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Tue, 05 Dec 2023 16:20:23 +0100 Original-Received: (qmail 17457 invoked by uid 1000); 5 Dec 2023 15:20:23 -0000 Content-Disposition: inline In-Reply-To: X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.3; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:313542 Archived-At: Hello, Eshel. Thanks for such a rapid reply! On Tue, Dec 05, 2023 at 16:03:18 +0100, Eshel Yaron wrote: > Hi Alan, > Alan Mackenzie writes: > > I want to find out what is the current buffer, and I mean the REAL > > current buffer. > > In particular, if that is the minibuffer, I want to be told it's the (or > > a) minibuffer, not the buffer it was invoked from. The function > > current-buffer won't do this. > My two cents: AFAICT, `current-buffer` does do this, in some sense at > least. To see that, type `M-x (current-buffer) C-x C-e`, here Emacs > says "#". Ah. Thanks for the clarification. > Note that when you say `M-: (current-buffer) RET` the form is read in > the minibuffer, but it's evaluated in the original buffer. That's why you > get the original buffer as the return value. > `M-: (current-buffer) C-x C-e` points at the minibuffer as expected OTOH. > > I want to use this for writing the current buffer into the new position > > info in the doc string (bug #67455). Evaluating a defun in the > > minibuffer is different from evaluating one in *scratch*. > > Is there some way I can get this information from Lisp, or do I have to > > write a new C primitive? > IIUC, you need the buffer from which the form was read, not the one in > which it was evaluated. Yes, indeed. Thanks! If I read a form from the minibuffer with M-:, which then evaluates it, the current buffer for the evaluation is not the minibuffer any more. > Perhaps `read_internal_start` could store its `stream` argument in > some variable so if you immediately evaluate a form with that variable > it would tell you where it was read from. It's just a rough idea, > though. It might be a good one, though. I'll have a close look at lread.c, and see whether or not I can slip that in. > Good luck, > Eshel -- Alan Mackenzie (Nuremberg, Germany).