From: James Thomas via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists <emacs-tangents@gnu.org>
To: emacs-tangents@gnu.org
Subject: Re: 2024-12-23 Emacs news
Date: Sun, 29 Dec 2024 13:57:40 +0530 [thread overview]
Message-ID: <86ikr251xf.fsf@gmx.net> (raw)
In-Reply-To: <877c7qf325.fsf@sachachua.com> (Sacha Chua's message of "Mon, 23 Dec 2024 17:27:14 -0500")
Sacha Chua wrote:
> * Using uv in Emacs | MClare Blog - python environment
>> The only source of frustration has been the lack of support/tooling
>> for uv on Emacs (though I would be happy to be proven wrong!)
This is right below:
> * New packages:
>
> ..
> * uv-mode: Integrate uv with python-mode (MELPA)
..but why not buffer-env? ( https://github.com/astoff/buffer-env )
--
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
parent reply other threads:[~2024-12-29 8:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <877c7qf325.fsf@sachachua.com>]
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=86ikr251xf.fsf@gmx.net \
--to=emacs-tangents@gnu.org \
--cc=jimjoe@gmx.net \
/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.
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).