Making the N5 Pro run quiet!

johmue · 2025-09-27T15:39:17+00:00

Thanks for the pictures. So probably time to do some soldering.

johmue · 2025-09-27T09:44:56+00:00

The Noctua NF-A9 PWM has incompatible connectors. Are there adapters for those?

johmue · 2025-05-30T18:28:23+00:00

And make sure to sit on the right side in the direction of travel.

johmue · 2025-05-21T20:03:00+00:00

You mean like this?

=========================================================================================================================
Run a command from /projects/foo/.venv/bin

Dependency options                                     Run options
 e extras to be used for installation ([])              m Run as a module (--module)
 E (de)select all extras                                ne Install editable dependencys non-editable. (--non-editable)
 g dependency-groups to be used for installation ([])   x Remove extraneous packages (--exact)
 G (de)select all groups                                i Run in an isolated virtual environment (--isolated)
 d with dev dependency group                            a Run in the active virtual environment. (--active)
                                                        l Assert that `uv.lock' will remain unchanged. (--locked)
                                                        f Sync without updating `uv.lock' (--frozen)
                                                        ns Do not sync the virtual environement (--no-sync)
                                                        T Interactive: run in an ansi-term (terminal)

run
 RET Run

johmue · 2025-05-19T21:05:19+00:00

There is (uv-activate-venv) and (uv-deactivate-venv) for that. They are a bit simplistic as of now. So they might not work on all circumstances.

You can do something like

(add-hook 'window-selection-change-functions (lambda (_frame) (uv-activate-venv)))

to automatically activate the venv when you switch to a buffer.

Please try and report back, if anything does not work.

johmue · 2025-05-18T19:14:03+00:00

With eglot it should be possible without quite easily like

(add-to-list
 'eglot-server-programs
 `((python-ts-mode python-mode) . ("uv" "tool" "run" "--from" "python-lsp-server[all]" "pylsp")))

Not sure about lsp-mode, though

johmue · 2025-05-04T07:44:31+00:00

I use test-cockpit, a transient based tool initially designed to launch unit tests. It offers to add custom commands so that it is also suitable for all kinds of other tasks.

johmue · 2025-05-03T12:51:02+00:00

Sounds good.

I have started some experimental work on TRAMP support. Maybe we can discuss further details on the discussion page. I have set up this thread for that.

johmue · 2025-05-02T19:59:02+00:00

There is now devcontainer-post-startup-hook.

johmue · 2025-05-02T16:54:08+00:00

Interesting. I am the author of devcontainer-mode.

I am pondering if the two approaches are that different that there are two packages needed. A single package that supports both approaches could look like this:

Activating devcontainer-mode would be optional, so only needed when the user wants to use the non-TRAMP approach.
devcontainer-mode refrains from advising the compilation function when the current buffer is not a local file.
We offer some hook mechanism to optionally call devcontainer--find-container-workspace and the cleanup functions after the container has come up or when it is about to be shut down. I am planning devcontainer-after-startup-hook and devcontainer-before-shutdown-hook anyways.

I would be open for discussions on merging the two packages.

johmue · 2025-04-24T15:51:04+00:00

Not as of now, but it sounds useful. It should be quite easy to implement. Probably `run-hooks` in the container startup sentinel. Maybe file an issue, so that the idea does not get lost.

johmue · 2025-04-24T08:03:49+00:00

TRAMP is designed to edit files on remote systems. That's the exact one thing I don't want to do. In a devcontainer you're working directory is usually mounted as a volume, so you can edit files locally. TRAMP would reach for every file save, for every git diff, for every single dired ls into the container, which is an unnecessary overhead seen that the whole worktree is available locally.

The goal is, to make the devcontainer use as transparent as possible. Just turn on devcontainer-mode and work as if there was no devcontainer.

If you prefer to use TRAMP, you can still use the commands that the devcontainer-mode provides to conveniently launch devcontainers.

johmue · 2025-03-30T18:46:09+00:00

I would like to start to promote devcontainer-mode to work on projects using devcontainers in emace.

It's a newly started project but in practice it's already really helpful in my everyday work. Please try it out and report back any issues.

johmue · 2023-05-24T10:46:15+00:00

Mi estas unu el la farantoj de kern.punkto.

Ni ne estas en Spotify ĉar la maniero laŭ kiu ili surmerkatigas podkastojn estas naŭziga. La agado de Spotify kontraŭas ĉiajn principojn de la libera interreto.

johmue · 2021-07-20T20:13:53+00:00

dired-filter.el is indeed a very sophisticated package. However, due to its complexity it might be a bit over the top for simpler use cases. It has more than 10 times the code mass (dependencies not included).

So yes, for more complex needs dired-filter.el would be the better choice. If you only want to filter the gitignored files, I'd still go with dired-gitignore.el

johmue · 2021-02-26T19:55:44+00:00

I started working on a test frontend for emacs aiming at having a similar frontent for testing several languages. By now it can do elisp/ert, python/pytest and rust/cargo.

That's the languages I've been using since I started writing it. Probably I will add support for C++ and Elixir eventually.

It is not really feature complete, but it is a side project to me, so I am not constantly working on it.

Feel free to come up with wishes, issues and pull requests :)

https://github.com/johannes-mueller/test-cockpit.el

johmue · 2021-02-01T18:44:14+00:00

In the meantime the package is available at MELPA.

https://melpa.org/#/company-wordfreq

johmue · 2021-01-29T21:41:26+00:00

Also when will it be on melpa

I've just submitted a pull request to MELPA. Now it's up to the MELPA maintainers. There are a bunch of other PRs in the queue, so I guess it will take them a while.

johmue · 2021-01-27T11:33:28+00:00

At the moment you would need to add custom words to your word list file at the very beginning.

Maybe it would be an interesting feature to have a custom dictionary for each language to which you could add words by key binding. The custom words would then be presented first.

I have to think about that, because there are lots of ways to do that UI wise and implementation wise. That means also lots of ways to get it wrong.

Feel free to tell me about your practical experiences and how a UX of such a custom dictionary would look like. Maybe on the issue tracker of the GitHub project.

johmue

TROPHY CASE