From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Friendlier dired experience [CODE INCLUDED] Date: Mon, 09 Nov 2020 18:20:13 -0500 Message-ID: References: <20201103104340.q34kqfita55w2u7h@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36991"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Boruch Baum , Emacs-Devel List To: Mathias Dahl Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 10 00:21:36 2020 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 1kcGTe-0009Ub-Gx for ged-emacs-devel@m.gmane-mx.org; Tue, 10 Nov 2020 00:21:34 +0100 Original-Received: from localhost ([::1]:35148 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kcGTd-0008IR-K3 for ged-emacs-devel@m.gmane-mx.org; Mon, 09 Nov 2020 18:21:33 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kcGSZ-0007jK-B6 for emacs-devel@gnu.org; Mon, 09 Nov 2020 18:20:27 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:37863) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kcGSW-0002RK-Hb for emacs-devel@gnu.org; Mon, 09 Nov 2020 18:20:26 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 2AB5E440F0E; Mon, 9 Nov 2020 18:20:20 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 6EA6C440DBD; Mon, 9 Nov 2020 18:20:14 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1604964014; bh=DNHdkvtpP67lErJivZcjIUy/HEkg25cPFBLQF07pXxU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=iN8KefffHiRW1bkCYfV8O6UZ0O+F9g804d3abAn3g0Zi9WyasNKhfQuZI0zpur9bd dN49ZSbGzZYqtRnkgR7mWOeRjDOL2Es5JIjdp6SzjZOLUEItAeR1TCGiS3f/9pL5XJ vAgINbgrIM3TeErOq3iBLYF1W8oJLa1xsCzrh6jK5HZMI2dsIlXgSeT3aJybLt/Sh6 NOHy2qkgeefmLeLiCSUC4NSquUMvfTecSRCKLl7jeI01oWOCDEUO7RCqdCev5BLZHA Jw+yVD2JAUhjnfSex+cVQ8roI137STzZVYNXYDlBa52wmHOLsyzfe+YK80TZOkBhqZ ADjXOaVZ+FoBw== Original-Received: from alfajor (unknown [157.52.9.240]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 373E5120445; Mon, 9 Nov 2020 18:20:14 -0500 (EST) In-Reply-To: (Mathias Dahl's message of "Mon, 9 Nov 2020 23:45:26 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/09 18:20:20 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:258959 Archived-At: > environment variables. It's a limitation however that the values are only > set (right?) when you go from the diredc buffers to the shell again, using > the special command. It would be super cool if the shell just "knew", > without diredc needing to set those things explicitly. Could Emacs' > different shells and terminals have this ability automatically by using > some pre-processing of each command invocation, looking for open Dired > windows in the same frame? I don't think this can be done "right" (actually in general even what diredc provides can't be done reliably without re-launching a new shell) by make the shell somehow aware of "where we are" (it would require a much tighter integration between the shell and Emacs than what's currently available). I can see two ways to do it: 1- ask the users to setup some kind of "support code" in their shell which implements a particular communication protocol with Emacs (and provide implementations for the most popular shells). 2- keep all the processing on Emacs's side, i.e. add special notations that can be used in the *shell* buffer and that are expanded by Emacs before sending them to the shell. Option 2 is probably the easiest, but it may get tricky to find a good syntax for it that's lightweight enough and doesn't get too much in the way of normal use. I don't think option 2 can work with `M-x term`, OTOH. > Did not try them but like others, I felt it might be better to integrate > with the normal bookmark functionality in some way. A command that simply > filters out the existing bookmarks that point to directories should not be > hard to add to Dired, or simply make part of selecting a directory > regardless of where you are in Emacs. BTW, I remember thinking that it would be nice/natural to allow specifying a (file) bookmark name when doing `C-x C-f`, and similarly `C-x C-d` could allow specifying a (directory) bookmark. > Resilient dedicated dual-pane frame > > I liked this and I used the default keybinding (S-f11). I also felt we > could make the same thing or something very similar using Winner, the new > tab functionality, or some of the other ways we can work with window > configurations. I get that a lot of work has been put into making this, as > the author says, resilient, and I don't want to down-play that. I don't know what diredc currently uses, but Emacs has grown the notion of "Atomic Windows" (see the Info doc, or `display-buffer-in-atom-window`) which might also be a good fit for diredc (or not: I haven't used it enough nor know diredc enough to be sure). Stefan