From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: new elpa packages for ada-mode project related stuff
Date: Wed, 16 Jan 2019 14:18:48 -0500 [thread overview]
Message-ID: <jwv4la8h144.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 86zhs0o2g0.fsf@stephe-leake.org
> Then defines a project defstruct that declares/undeclares
> environment variables when it is selected/deselected.
Shouldn't the right env-var simply be automatically selected based on
the project of the current buffer?
IOW, I'd rather have a cl-generic `project-envvars` and then somehow
make sure these envvars are passed to any sub-process.
I often work on several projects basically at the same time in a single
Emacs session, so manually "selecting" a project would be inconvenient.
> path-iterator.el -- 243 lines
> Provides an iterator for directory paths;
You mean something similar to locate-file (but returning "all matches"
and in the form of an iterator)? Sounds fine to me.
> Probably should be rewritten to use generator.el.
I haven't seen the current code, so I don't know what it's using now
instead of generator.el.
> uniquify-files.el -- 687 lines
> Provides a completion style and completion table that presents
> uniquified file names to the user for completion.
Sounds cool.
> Ok to create these ELPA packages (in elpa/packages)?
The usual answer for this question is "yes". If you're unsure, making
it an "external" (rather than a plain directory inside `packages`) makes
it easy to get rid of it without leaving traces in the Git history.
Stefan
next prev parent reply other threads:[~2019-01-16 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 18:57 new elpa packages for ada-mode project related stuff Stephen Leake
2019-01-16 19:18 ` Stefan Monnier [this message]
2019-01-16 21:43 ` Stephen Leake
2019-01-17 1:41 ` Stefan Monnier
2019-01-17 13:22 ` Michael Heerdegen
2019-01-17 2:31 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv4la8h144.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.