On Sunday, 21 January 2024 08:43:05 CET Otto Kekäläinen wrote:
> What editors and extensions are you using to augment your productivity
> and minimize mistakes when editing debian/* files?
That's not exactly an editor extension, but I use 'cme edit dpkg' to modify
debian files.
This tool provide
Hi Otto,
Quoting Otto Kekäläinen (2024-01-29 07:06:51)
> > > It would be nice though if the version in Debian was newer :)
> >
> > I probably won't update it until it is suitable for inclusion in a
> > stable release. This means at minimum being relatively safe to run in
> > an untrusted source
Hi!
> > It would be nice though if the version in Debian was newer :)
>
> I probably won't update it until it is suitable for inclusion in a
> stable release. This means at minimum being relatively safe to run in
> an untrusted source tree, probably by using debvm to generate a VM
> containing
On Thu, 2024-01-25 at 22:22 -0800, Otto Kekäläinen wrote:
> Yeah, I remember looking into cats some years back as a place to learn
> what commands exist. Similarly I also occasionally browse
> https://pre-commit.com/hooks.html.
Yeah, there are lots of other tools similar to cats, many of them
Hi!
> Thats beginning to look like the history of check-all-the-things.
Yeah, I remember looking into cats some years back as a place to learn
what commands exist. Similarly I also occasionally browse
https://pre-commit.com/hooks.html.
The challenge with having all possible checkers is that they
On Sat, 2024-01-20 at 23:43 -0800, Otto Kekäläinen wrote:
> PS. Related, these are commands I frequently run manually but don't
> have any editor integration for:
Thats beginning to look like the history of check-all-the-things.
Initially I maintained such a list of commands on the wiki:
> I looked into better tooling/editor support in general for Debian
> languages in general. I think the industry answer is that "someone"
> ought to build a "language (LSP) server" for the Debian languages, which
> would enable editors with LSP support[1] to get the same basic features.
True -
Otto Kekäläinen:
Hi!
Thanks for the tip, Niels!
It would be cool if dh_assistant had some kind of generic command like
"dh_assistant validate" which would attempt to introspect all
information silently and emit output only if it fails to parse
something.
That might be an option. The question
Hi!
Thanks for the tip, Niels!
It would be cool if dh_assistant had some kind of generic command like
"dh_assistant validate" which would attempt to introspect all
information silently and emit output only if it fails to parse
something. Additionally it could emit a non-zero exit code on errors.
Niels Thykier:
[...]
Btw, `debhelper` has a `dh_assistant` command that can do some very
basic analysis as well. Not sure any of it is useful for editor
integration (especially because some of the features requires that it
receives the same arguments as `dh` or/and `dh_auto_configure`).
Otto Kekäläinen:
Hi!
What editors and extensions are you using to augment your productivity
and minimize mistakes when editing debian/* files?
I am aware of dpkg-dev-el for Emacs mentioned in the DD reference[1].
I am a big fan of Pulsar[2] and recently found a 'language-debian'
plugin for
Hi!
What editors and extensions are you using to augment your productivity
and minimize mistakes when editing debian/* files?
I am aware of dpkg-dev-el for Emacs mentioned in the DD reference[1].
I am a big fan of Pulsar[2] and recently found a 'language-debian'
plugin for Pulsar[3], but didn't
12 matches
Mail list logo