From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Subprojects in project.el Date: Sat, 26 Nov 2022 14:38:22 +0200 Message-ID: <0323877a-2198-c295-61c1-5fcb1813f409@yandex.ru> References: <87zgcq68zp.fsf@ericabrahamsen.net> <877czqtyfy.fsf@dfreeman.email> <87zgcml7g7.fsf@gmail.com> <2ba04533-097a-a1da-ff3f-2c9506fd488e@yandex.ru> <875yf9bbzb.fsf@gmail.com> <87wn7oa0aw.fsf@gmail.com> <7a5b76fd-fb15-8c1e-ea29-bf11f7e0d2ae@yandex.ru> <87bkoya815.fsf@gmail.com> <0024a67d-b8e5-b35c-1b22-82541a170eb3@yandex.ru> <871qptai4d.fsf_-_@gmail.com> <33292672-2a59-ba63-05ab-a7995118a822@yandex.ru> <87pmdau6wo.fsf@gmail.com> <87zgcesg8l.fsf@gmail.com> <79a17a5c-d1c1-ce69-d29a-9127150fb1d7@yandex.ru> <87edtqrr0b.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40305"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Cc: Stefan Monnier , Danny Freeman , Eric Abrahamsen , emacs-devel To: =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 26 13:38:56 2022 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 1oyuSO-000AIn-6N for ged-emacs-devel@m.gmane-mx.org; Sat, 26 Nov 2022 13:38:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oyuS0-0001bQ-QN; Sat, 26 Nov 2022 07:38:32 -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 1oyuRw-0001b7-Sd for emacs-devel@gnu.org; Sat, 26 Nov 2022 07:38:29 -0500 Original-Received: from mail-wm1-x330.google.com ([2a00:1450:4864:20::330]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oyuRv-00022x-4N for emacs-devel@gnu.org; Sat, 26 Nov 2022 07:38:28 -0500 Original-Received: by mail-wm1-x330.google.com with SMTP id h131-20020a1c2189000000b003d02dd48c45so2231321wmh.0 for ; Sat, 26 Nov 2022 04:38:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=8wS1uBcdHgui4W/Yk2GYKQXLVIOrwluzzLP06lgLiBU=; b=ZS7ZKaEMMebhr6erD9UDej0S1gyCrFfcK4rnV7hiD8VIfy6uW//M4ktwG0CXdgxE0K PJqbst9/cQJ7Nx91g3VDYWyjWWxI/qGsmmAg/8AuHtdiFdyA07lXkTu4jr7bw4T46/GA TJ1m0ZduW6ByzMQTfpQuu/fZ0PjmtB5fzyFKYUwClJ03HLe3dbfLFvAmqHDJBKh9fFAq qRue3Yu+yIjaOLPEAomBn4SttooDPr55EgdJ56jBGrZsIwzTYZFHsNmbUPznTFAPD2hh IH+VBLtW/d3SZL/hvQLAf/aq2JbXuSE6ataxYqmiZSQNHSxdQkEC6POIAs8+Fgy8qjlr XaxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8wS1uBcdHgui4W/Yk2GYKQXLVIOrwluzzLP06lgLiBU=; b=JanFcVQp+/XBAKVYAOdpmbQMpfU9iJpuvLxr8zWYNgmYftvjr9RE/zEe3pIzYaUo8w qIbjTwmJMGwxfcGw/LXx3wSFbzgWRMaG8lc0vUTLiyyAmvNZNyuomtM0v/xQGna6Fqep O4BVEXWuFdUo3SpqTqDikp7Lh04LW4h/Jvb+macS23nlPxOVsDCsneHKwKD2C4rpmPrt sFyvTXrST78ipdnNQkus+q3hh8TMnrG7Bn8B/YatbTaSbMgeI0NZgrKBQ0jgka+S4TM8 JjdGMR1Zozvjn+xX7qtBf/hQ2qzrpd1/FtVZZEBhEvKPA5v3XydTgLIygMjQ3ZrD84mz +ccA== X-Gm-Message-State: ANoB5pn3afp+mWKapXZZP/nckNC6+IODSSIT3EB1Qx9LV2JaINgWQzJm dNQdT2REiBE2p2c2sl01oJc= X-Google-Smtp-Source: AA0mqf6Jluw9GzEHc3XvmBsfwG8peOJNKUl/LBunvhVUbkfIWQiZmth+bmk37/SSjFVx5E04Ln4pVw== X-Received: by 2002:a05:600c:444b:b0:3cf:c56c:1db2 with SMTP id v11-20020a05600c444b00b003cfc56c1db2mr22162067wmn.136.1669466304687; Sat, 26 Nov 2022 04:38:24 -0800 (PST) Original-Received: from [192.168.0.6] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id f2-20020a1c6a02000000b003b4868eb71bsm12093204wmc.25.2022.11.26.04.38.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 26 Nov 2022 04:38:24 -0800 (PST) Content-Language: en-US In-Reply-To: <87edtqrr0b.fsf@gmail.com> Received-SPF: pass client-ip=2a00:1450:4864:20::330; envelope-from=raaahh@gmail.com; helo=mail-wm1-x330.google.com X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.183, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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:300563 Archived-At: On 26/11/22 11:42, João Távora wrote: > Dmitry Gutov writes: > >> On 26/11/22 02:37, João Távora wrote: >>> Dmitry Gutov writes: >>> >>>>>>> I can't understand what is discourteous about this. >>>>>> That would be not following the procedure the maintainer has asked you >>>>>> to follow. >>>>> If that means silencing me on emacs-devel, then you're out of luck. >>>> >>>> Is that what you do when you ask somebody to use the bug tracker? >>> I'll use the bug tracker when I think it's appropriate. Let's not >>> insinuate I'm some kind of inconsiderate delinquent for not moving the >>> discussion there as you would want. I'm not reporting a bug and I've >>> politely declined your suggestion, so stop beating this horse. >> >> Must be nice to be the person who gets to decide what is appropriate >> in any situation. > > As long as this list's maintainer doesn't object, I get to decide where > _I_ post to, thank you very much. I'll keep that in mind. >> By modifying each and every command. I don't think it would be >> appropriate for 'project-current' itself to react to the value of >> current-prefix-arg. > > It's very unfortunate to modify "each and every command" unless of > course you mean doing it via a uniform interface. > > I don't understand why these "project" commands that operate on a > project don't befittingly take a PROJECT argument. That argument's > value could be interactively calculated from a > project-read-project-maybe command that decides if and how to prompt. Hysterical raisins. But 'C-x p f' and 'C-x p g' call 'project-current' directly. What's that about some new command? >>>> What's missing in the infrastructure? >>> Not much, I would say. But I think at least: >>> * A way that I can add an element to project-find-functions that >>> understands that a super-project has been detected already in the >>> current search and proceeds to find sub-projects inside it. This is >>> what I posted code for. >>> * A way for M-- (or similar) to consistently affect all (or most) of >>> the >>> operations in the C-x p keymap so that we can choose if the operation >>> operates on the super-project, if it exists. Unfortunately some of >>> these commands (like project-find-files) already take a prefix >>> argument to mean different things. But it's not too bad. >>> * A new project type, similar to the '(transient . "dir") project >>> (and >>> inheriting most of its operations) that also keeps a record of the >>> super-project found. This might not be strictly necessary, but could >>> come in handy later for efficiency reasons. >> >> Sounds pretty complicated. See if the latest patch solves your >> immediate problems just as well. > > In your patch to be cramming it all into the VC type (which the comment > itself admits becomes "VC and etc.") and trying very hard not to create > a new subproject type. But if you did that you could easily e.g. reuse > the super-project's ignore rules etc in the sub-project. How does one "easily reuse the super-project's ignore rules"? Would the sub-project type be called "sub-project"? What if one VC repository is nested inside another? What if one "plain" project is nested inside another?