From: "Sébastien Gendre" <seb@k-7.ch>
To: Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
Subject: Dev workflow in Emacs with containers
Date: Fri, 29 Nov 2024 15:32:09 +0100 [thread overview]
Message-ID: <87h67qnmae.fsf@k-7.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
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 ?
Best regards
-------
Gendre Sébastien
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next reply other threads:[~2024-11-29 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:32 Sébastien Gendre [this message]
2024-11-29 17:32 ` Dev workflow in Emacs with containers Yuri Khan
2024-11-29 18:20 ` Leo Butler
2024-11-30 10:44 ` Yuri Khan
2024-11-30 18:21 ` Sébastien Gendre
2024-12-01 9:41 ` Yuri Khan
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=87h67qnmae.fsf@k-7.ch \
--to=seb@k-7.ch \
--cc=help-gnu-emacs@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.
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).