From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Control help- and Info-mode buffers from other buffers Date: Sat, 03 Jun 2023 17:04:03 +0300 Message-ID: <83ilc48wx8.fsf@gnu.org> References: <87h6ruf09e.fsf@ledu-giraud.fr> <861qixbum2.fsf@mail.linkov.net> <86wn0opgpi.fsf@mail.linkov.net> <86ilc78zc2.fsf@mail.linkov.net> <834jnrek7w.fsf@gnu.org> <86v8g77iof.fsf@mail.linkov.net> <83o7lzcxm8.fsf@gnu.org> <837csncfz1.fsf@gnu.org> <83o7lybaph.fsf@gnu.org> <83ttvpao80.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2021"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, manuel@ledu-giraud.fr, emacs-devel@gnu.org To: Arthur Miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 03 16:04:14 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 1q5RrZ-0000Lx-RX for ged-emacs-devel@m.gmane-mx.org; Sat, 03 Jun 2023 16:04:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q5Rqf-0002nF-7j; Sat, 03 Jun 2023 10:03:17 -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 1q5Rqd-0002ml-Gu for emacs-devel@gnu.org; Sat, 03 Jun 2023 10:03:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q5Rqc-0004EX-Hz; Sat, 03 Jun 2023 10:03:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=cXSDDF8hX/JObzvPk72lt8MGOUl+s3TJCnXR0sYGAQU=; b=cOSHB/6h8Kx+ j6W7OpBDwNLMx8FjflLOVBaUG/AysuAFL0Az/nHQCjwvf37xDXGN6omNw9A7aAfBpwGRPnFeE2n9F edSpEYjGygom72bdpsraaj9ftRtGxktK+OoebmtV2mII+m1qvpEiGYk2lfCw1tFJNYRa+cHmM779j YUt0/fB3sscttNjgDD4AFk10zFIrTKUIUMiMFRXrHkIKHDYR9FClO/uyFwbpZwq42fe21I+1NI2r0 tlyiJV/07uGMHOIZxxCHPWt9j4bJ97JRllyfZvLYhtsyShHV/36qdBcYymYcTFcD7TTHR9ijvkj0x sJgWFXfum8T8v2rN7tsC0Q==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q5Rqc-0003Nt-1f; Sat, 03 Jun 2023 10:03:14 -0400 In-Reply-To: (message from Arthur Miller on Sat, 03 Jun 2023 15:53:22 +0200) 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:306590 Archived-At: > From: Arthur Miller > Cc: juri@linkov.net, manuel@ledu-giraud.fr, emacs-devel@gnu.org > Date: Sat, 03 Jun 2023 15:53:22 +0200 > > The interactive form has to be the very first form in a function body, which > makes it impossible to just wrap the entire function into > with-selected-window. I still don't understand why you need the entire function to be wrapped in with-selected-window. > However, that is just a side note as answer to your remark, but unfortunately I > have found that there is a bigger problem. I am not sure if it is Emacs or my > X11 window manager, but I do suspect the WM in this case. > > I have both in my WM and in Emacs that focus should follow mouse. Now what > happens is that, despite the function jumpiing to correct Emacs window on > another frame, due to cursor being in old frame, all input goes to the old > frame, so at least this particular function does not work with multiple > frames. I don't understand: I thought we were talking about causing the other window to do something without the user selecting that window. So why does it matter where input goes? what input do you want to go to the non-selected window or frame? For example, the command "M-PgUp" scrolls "the other" window without selecting it, and I don't want in this case to have input switched to that other window. Same will be my expectation when there will be a command to show me the source of a function whose doc string is displayed in the *Help* buffer shown in the other window: I want just to see the source in that other window, I don't want to start typing there. What am I missing or misunderstanding? Why are you suddenly talking about redirecting input? > I do have another question too: what is a good strategy if there are multiple info > windows open? Prompt user to select with a completing read, or just leave as-is, > i.e. return the first info window? You are talking about a situation where multiple *Help* windows are shown?