unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: mohkale@kisara.moe
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Project out of sources compilation
Date: Mon, 22 Apr 2024 20:48:55 +0200	[thread overview]
Message-ID: <fow2vlvsbedbzvhlivr3lp3jqivlwtpp362ojjmtbexn4yh2xc@faqmdsd46zfv> (raw)
In-Reply-To: <2bpiuffyzhqvirscyn5prs4rb6m5ito7xnwqvc53obm32isp3g@w73yut5uku4y>

Adding Mohsin Kaleem to the discussion.


On Mon, Apr 22, 2024 at 07:05:20PM GMT, Ergus wrote:
>Hi Juri:
>
>Give a look to this:
>
>https://github.com/mohkale/projection
>
>It seems similar to what we may consider to support in vanilla. OR at
>least provide the interactive interface wrapper functions in order to
>make project.el a bit more standard.
>
>On Sun, Apr 14, 2024 at 04:44:36AM GMT, Dmitry Gutov wrote:
>>Hi Ergus!
>>
>>On 06/04/2024 05:05, Ergus wrote:
>>
>>>Here I attach a new patch with what I think is the best approach to
>>>handle the extra info for projects. This implementation is pretty simple
>>>for both sides (user, project.el and backends) and uses your main idea
>>>of the generics + a custom.
>>>
>>>However I decided not to use only the custom as you suggested, because
>>>considering the project initialization it will require a complex and
>>>error prone approach to initalize the backend variables correctly (for
>>>example, when some buffers are already open).
>>>
>>>With this implementation the backends only need to define the optional
>>>generic specializations and the policy is pretty simple to explain (see
>>>the doc strings).
>>>
>>>I also modifies the backend project on github to match this new api, so,
>>>you can check it as well.
>>
>>How about the idea with the orthogonal hook, then, as in the 
>>attached patch? Something I described before.
>>
>>I think your github code would be easy enough to adapt to use it.
>>
>>WDYT?
>
>
>



  reply	other threads:[~2024-04-22 18:48 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4wwljrdnra3bsloehioa46y24ozxajajmvf2elvskxxq3mhtg2.ref@pyv2z5snot6h>
2024-03-16 13:12 ` Project out of sources compilation Ergus
2024-03-16 16:50   ` Konstantin Kharlamov
2024-03-16 19:00     ` Ergus
2024-03-16 20:56       ` Konstantin Kharlamov
2024-03-17  2:53   ` Dmitry Gutov
2024-03-17  7:22     ` Ergus
2024-03-17  8:45       ` Eli Zaretskii
2024-03-17 17:33         ` Ergus
2024-03-17 17:38           ` Eli Zaretskii
2024-03-17 17:58             ` Ergus
2024-03-17 11:36   ` Augusto Stoffel
2024-03-17 17:47     ` Ergus
2024-03-19 18:36       ` Ergus
2024-03-27 16:38         ` [PATCH] " Ergus
2024-03-31  2:41           ` Dmitry Gutov
2024-03-31 21:07             ` Ergus
2024-04-01  7:49               ` Dirk-Jan C. Binnema
2024-04-01 13:52                 ` Ergus
2024-04-01 15:09                   ` Dirk-Jan C. Binnema
2024-04-01 17:18                     ` Ergus
2024-04-02 23:23                   ` Dmitry Gutov
2024-04-03 19:47                     ` Ergus
2024-04-06  2:05                     ` Ergus
2024-04-14  1:44                       ` Dmitry Gutov
2024-04-16 14:56                         ` Ergus
2024-04-22 17:05                         ` Ergus
2024-04-22 18:48                           ` Ergus [this message]
2024-04-22 21:20                             ` Mohsin Kaleem
2024-04-23 15:17                               ` Ergus
2024-04-23 19:26                                 ` Mohsin Kaleem
2024-04-26  0:47                               ` Dmitry Gutov
2024-04-02 21:39               ` Richard Stallman
2024-04-02 22:43                 ` Dr. Arne Babenhauserheide
2024-04-05 21:40                   ` Richard Stallman
2024-04-03 10:40                 ` Konstantin Kharlamov
2024-04-03 11:45                   ` Eli Zaretskii
2024-04-03 13:31                     ` Konstantin Kharlamov
2024-04-03 14:11                       ` Eli Zaretskii
2024-04-03 15:00                         ` Konstantin Kharlamov
2024-04-03 15:47                           ` Eli Zaretskii
2024-04-03 17:27                             ` Konstantin Kharlamov
2024-04-03 18:22                               ` Eli Zaretskii
2024-04-03 19:08                                 ` Konstantin Kharlamov
2024-04-03 20:12                                   ` Ergus
2024-04-04  5:26                                     ` Eli Zaretskii
2024-04-04  9:59                                       ` Ergus
2024-04-04 11:59                                         ` Eli Zaretskii
2024-04-04 12:34                                           ` Ergus
2024-04-04 13:02                                             ` Eli Zaretskii
2024-04-04 14:27                                               ` Ergus
2024-04-04 14:41                                                 ` Eli Zaretskii
2024-04-04 18:15                                                   ` Ergus
2024-04-04 18:56                                                     ` Eli Zaretskii
2024-04-04 20:16                                                   ` Konstantin Kharlamov
2024-04-05  5:11                                                     ` Eli Zaretskii
2024-04-04  5:07                                   ` Eli Zaretskii
     [not found]                               ` <87jzlefgi9.fsf@dick>
2024-04-03 18:44                                 ` Konstantin Kharlamov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fow2vlvsbedbzvhlivr3lp3jqivlwtpp362ojjmtbexn4yh2xc@faqmdsd46zfv \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=mohkale@kisara.moe \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).