unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Manuel Uberti <manuel.uberti@inventati.org>,
	mardani29@yahoo.es, 54228@debbugs.gnu.org,
	Rudolf Schlatte <rudi@constantly.at>
Subject: bug#54228: 29.0.50; project.el: Support local projects
Date: Sat, 5 Mar 2022 03:31:18 +0200	[thread overview]
Message-ID: <e528ab83-47e5-8bf7-f8b4-a391cece7d41@yandex.ru> (raw)
In-Reply-To: <564b8ac4-3d6f-3c7f-15ac-7dc661a18868@inventati.org>

Hey folks,

Check out https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41572, of which 
this is a duplicate.

If the discussion seems daunting (and it is overly long), you can start 
at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=41572#82.

Comments welcome.

On 04.03.2022 20:15, Manuel Uberti via Bug reports for GNU Emacs, the 
Swiss army knife of text editors wrote:
> On 04/03/22 18:48, Daniel Martín wrote:
>> I use similar code in my config.  It's specially useful for monorepos,
>> where there is only one big .git folder, but multiple projects that you
>> want to handle separately.
> 
> In my case it's super useful for projects where I do not have VC 
> involved, of which I have a few. I just can't live without project.el 
> facilities in my daily Emacs any more. :)
> 
>> If we want to contribute this to project.el, I wonder if it makes sense
>> to generalize it a little bit by making ".project" the default value of
>> a customization variable.  That'd avoid the name clash with some Eclipse
>> files.  We could also detect files from common build systems, but I
>> don't know if that would be out of scope for the rather minimalist
>> project.el (vs projectile.el, for example).
> 
> I did not think about making ".project" the value of a defcustom, 
> because I do not use anything that relies on ".project" files. But if as 
> you say there is a chance of name clashing, then yes, making 
> customizable seems about right.
> 
> I'd wait for Dmitry to jump in on this. I'd like to hear his opinion as 
> well.






  reply	other threads:[~2022-03-05  1:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03  7:15 bug#54228: 29.0.50; project.el: Support local projects Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-03 12:36 ` Rudolf Schlatte
2022-03-04 17:48 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-04 18:15   ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05  1:31     ` Dmitry Gutov [this message]
2022-03-05  7:42       ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-05 16:15   ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=e528ab83-47e5-8bf7-f8b4-a391cece7d41@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=54228@debbugs.gnu.org \
    --cc=manuel.uberti@inventati.org \
    --cc=mardani29@yahoo.es \
    --cc=rudi@constantly.at \
    /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).