[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dev workflow in Emacs with containers
From: |
James Thomas |
Subject: |
Re: Dev workflow in Emacs with containers |
Date: |
Fri, 27 Dec 2024 06:18:09 +0530 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Sébastien Gendre wrote:
> Hello,
>
> I got a few questions about how to integrate Emacs with a development
> workflow who use containers.
>
>
> First, a bit of context:
>
> Emacs provide some great tools to integrate with the dev workflow:
>
> - The `compile` function to compile or to run tests
>
> - Integration with multiple debuggers (GDB, PDB, etc)
>
> - Integration with multiple REPL (Python, Lua, etc)
>
> - Shell and terminal to launch the newly developed software
>
>
> These tools are great when the complied/tested/debugged/run software is
> local. But I use more and more the containers. Even for micro-controller
> firmware dev.
>
> I use Podman, but the situation is similar with Docker. And my Emacs
> process run outside of the containers.
>
>
> My questions are:
>
> What are your experience with using Emacs, the tools cited above and
> containers ?
>
> Do you use a `.dir-locals.el` to set the commands run by Emacs to
> debugg/compile/etc ? Or do you use a Makefile with pre-defined targets
> for test, debug, build, etc ?
>
> How do you manage when Emacs highlight a link to a file, but the
> obtained path correspond to the container file system while Emacs can
> access this file from the host file system ?
Have you tried simply with Tramp's docker/podman methods?
--