From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eshel Yaron Newsgroups: gmane.emacs.devel Subject: Re: How do I find out, in a Lisp program, what is the current buffer? Date: Tue, 05 Dec 2023 16:03:18 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38918"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 05 16:04:20 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 1rAWyC-0009xj-8B for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Dec 2023 16:04:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rAWxS-0007mx-BI; Tue, 05 Dec 2023 10:03:34 -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 1rAWxJ-0007m0-V9 for emacs-devel@gnu.org; Tue, 05 Dec 2023 10:03:26 -0500 Original-Received: from mail.eshelyaron.com ([107.175.124.16] helo=eshelyaron.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rAWxI-00084C-Bj for emacs-devel@gnu.org; Tue, 05 Dec 2023 10:03:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eshelyaron.com; s=mail; t=1701788601; bh=p20jtTpF9do6jqy5RmLcDSHEhzEoFVbThotQzTMgAKA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=gjh4jf8PFfLSKsatGYi831rqLj3bHV+rGJXQKIbyOzgPF8/0UUzmN9twXgllAPhz4 4fhlkm8vzMZ7+8rh/qfX9Kpc2SM6QUalP1cYsxEzDWSkHLxi8ZaguOcQeSDA2snTYa UhwSTQvX/PjQtpRyu1lO0siVoyngXLHHubW1SnnsHxxFA+xSlbpG6VlqE+qj7HJv46 Cw8xZDqONhNfOUaBVYBCyuAwMLlLAGyh8pHFTST4+8DAX7nawIP/ph8aBdGjmJom4p 0R9oB0S6uL2GXbQ0Nx90NfrLtvxQC31eZCKA+3Yz2MpGCwhqRXv0y+7z9Si/KDsuG3 lfoLu8akW9dsQ== In-Reply-To: (Alan Mackenzie's message of "Tue, 5 Dec 2023 14:35:48 +0000") Received-SPF: pass client-ip=107.175.124.16; envelope-from=me@eshelyaron.com; helo=eshelyaron.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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:313541 Archived-At: 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 "#". 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. 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. Good luck, Eshel