From: Fabian Ezequiel Gallina <galli.87@gmail.com>
To: Jorgen Schaefer <forcer@forcix.cx>
Cc: emacs-devel@gnu.org
Subject: Re: A unified project root interface
Date: Sat, 9 Mar 2013 14:12:05 -0300 [thread overview]
Message-ID: <CABq4mQsHXLbztaif+y6VirWUejH7DsczGQUceKmRPwpu3GAQpA@mail.gmail.com> (raw)
In-Reply-To: <20130309174419.6e1cadb4@forcix.kollektiv-hamburg.de>
2013/3/9 Jorgen Schaefer <forcer@forcix.cx>:
>
> It would be really useful if there was a single standard way to define
> the project root, so that extensions can just use that standard way
> without each and every one of them writing the same code over and over
> again. Sadly, as the code is not exactly difficult and so many projects
> have already used their own way, it's highly unlikely that a random
> third-party library would simply "emerge" as the standard way of doing
> things. Which makes me believe the only way to solve this is via a bit
> of a top-down decision to include a library in Emacs and declare it as
> "the default".
>
There's a standard way of defining variable values for files inside a
parent folder (read project). This mechanism is the Directory Local
variables [M-: (info "(emacs)Directory Variables")]. And it works, and
works good, in fact python.el makes use of this a lot and is able to
even to set the virtualenv for all your project files (without messing
with external others) thanks to it[0].
Normally I would consider the .dir-locals.el file location as the
project root, but then perhaps the user needs to override some values
in a sub-folder. So in that case I think it might be a good idea to
introduce an additional standard name for .dir-locals.el files that
are ought to be used only at the project root. I propose the name of
.project-locals.el. With this detecting if a file belongs to a project
and what's the project root is as easy as to find the
.project-locals.el.
>
> So this is my somewhat verbose request to say "yes, let's do this" and
> pick a library to provide the functionality. The library itself doesn't
> have to be big at all, in theory a single variable `project-root'
> that everyone is encouraged to use would be enough. Adding some
> basic functionality to this would be helpful, though. If we keep the
> functionality to a minimum, this lets other extensions use it without
> being annoyed at the features they drag in.
>
With something like the .project-locals.el, the only thing missing is
some UI for people fearing associations lists. I think, the best way
to go is a similar interface of what you get with customize-group
(hopefully most of its code could be borrowed).
[0] See Directory Local Variables section at: http://bit.ly/ZzUxxL
Regards,
Fabián
next prev parent reply other threads:[~2013-03-09 17:12 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 16:44 A unified project root interface Jorgen Schaefer
2013-03-09 17:12 ` Fabian Ezequiel Gallina [this message]
2013-03-10 5:38 ` Stefan Monnier
2013-03-10 10:06 ` Jorgen Schaefer
2013-03-11 18:57 ` Lluís
2013-03-12 23:28 ` Eric M. Ludlam
2013-03-12 23:42 ` Jorgen Schaefer
2013-03-13 2:02 ` Eric M. Ludlam
2013-03-13 18:03 ` David Engster
2013-03-13 19:11 ` Sudish Joseph
2013-03-16 0:47 ` Eric M. Ludlam
2013-03-16 14:18 ` David Engster
2013-03-16 15:02 ` Jorgen Schaefer
2013-03-16 22:27 ` Phil Hagelberg
2013-03-16 22:59 ` David Engster
2013-03-16 23:16 ` Jorgen Schaefer
2013-03-17 17:40 ` David Engster
2013-03-17 18:18 ` Jorgen Schaefer
2013-03-18 22:50 ` David Engster
2013-03-19 1:57 ` John Yates
2013-03-19 7:18 ` David Engster
2013-03-19 12:23 ` Eric M. Ludlam
2013-03-19 13:06 ` Stefan Monnier
2013-03-19 19:09 ` David Engster
2013-03-20 3:21 ` Stefan Monnier
2013-03-20 4:48 ` Leo Liu
2013-03-20 7:04 ` joakim
2013-03-20 7:05 ` David Engster
2013-03-20 7:13 ` David Engster
2013-03-20 12:57 ` Stefan Monnier
2013-03-20 16:14 ` Davis Herring
2013-03-20 17:41 ` Stefan Monnier
2013-03-20 17:48 ` Stefan Monnier
2013-03-20 18:20 ` Bruce Korb
2013-03-20 22:14 ` Stefan Monnier
2013-03-20 16:34 ` David Engster
2013-03-20 17:47 ` Stefan Monnier
2013-03-21 0:55 ` Eric M. Ludlam
2013-03-21 3:27 ` Stefan Monnier
2013-03-21 4:07 ` Eric M. Ludlam
2013-03-21 14:33 ` Stefan Monnier
2013-03-22 2:12 ` Eric M. Ludlam
2013-03-23 11:04 ` EIEIO split (was: A unified project root interface) David Engster
2013-03-21 16:32 ` A unified project root interface David Engster
2013-03-22 0:47 ` Eric M. Ludlam
2013-03-22 20:30 ` David Engster
2013-03-23 17:10 ` Eric M. Ludlam
2013-03-23 17:26 ` Jorgen Schaefer
2013-03-23 18:02 ` Dmitry Gutov
2013-03-23 20:51 ` Pascal J. Bourguignon
2013-03-24 4:25 ` Dmitry Gutov
2013-03-24 10:13 ` Jorgen Schaefer
2013-04-06 13:25 ` Jorgen Schaefer
2013-04-06 17:13 ` Eric M. Ludlam
2013-04-08 19:03 ` David Engster
2013-12-31 20:12 ` Daniel Colascione
2013-03-20 17:49 ` Jorgen Schaefer
2013-03-19 7:33 ` Jorgen Schaefer
2013-03-17 8:08 ` joakim
2013-03-12 15:34 ` Sudish Joseph
2013-03-12 16:51 ` Dmitry Gutov
2013-03-12 18:23 ` Ted Zlatanov
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=CABq4mQsHXLbztaif+y6VirWUejH7DsczGQUceKmRPwpu3GAQpA@mail.gmail.com \
--to=galli.87@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=forcer@forcix.cx \
/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).