all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA package submission: buffer-env
Date: Mon, 28 Feb 2022 14:40:43 -0500	[thread overview]
Message-ID: <jwvlexupyyh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sfs2u8jh.fsf@gmail.com> (Augusto Stoffel's message of "Mon, 28 Feb 2022 19:53:54 +0100")

> I would like to propose the following package for inclusion in ELPA:
>
>    https://github.com/astoff/buffer-env
>
> The immediate purpose of the package (for me) is to deal with Python
> virtualenvs.  But it should be useful when working on any project with
> dependencies that are not globally installed.
>
> Some time ago I started a thread on this list explaining why I thought
> Emacs should have better support for setting the process environment per
> project / buffer locally [1].  But it's not clear there's a case for a
> built-in facility; and while this package is not extremely beautiful it
> solves the matter satisfactorily.  So after quite some incubation time I
> decided it's worth sharing.

That sounds useful (and I think we should improve Emacs's core to better
support such features; we already have some ad-hoc
frame-local-environment support and it would be good to make that less
ad-hoc).

The default value for `buffer-env-command` is a gaping security hole, tho.
Any hope we can make this a bit less dangerous?


        Stefan




  reply	other threads:[~2022-02-28 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 18:53 ELPA package submission: buffer-env Augusto Stoffel
2022-02-28 19:40 ` Stefan Monnier [this message]
2022-02-28 19:54   ` Augusto Stoffel
2022-02-28 19:58     ` Stefan Monnier

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=jwvlexupyyh.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=arstoffel@gmail.com \
    --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.