elfeed-score VS use-package

I'm trying to set up elfeed-score for some arXiv feeds -- in the manner of this blog post. The scoring and sorting work out great, but the adjust-tags rule (described here) for labeling posts which have a score higher or lower than a certain threshold seems to be failing.

Of course, that's NOT an UI design issue, that's a social issue, but still the issue is there and not much can be done software-side to really solve it. Recommendation engines became popular because they can filter out more, classic scoring (that elfeed now have, aside https://github.com/sp1ff/elfeed-score) is another option...

Some time ago I made a package that lets you score elfeed entries according to rules you setup (like Gnus scoring). Since then, I've (gratefully) received a number suggestions & contributions, and the package has grown in size & complexity. It's most recent release includes some major changes including: - refactoring elfeed-score.el, which had become difficult to read, maintain & reason about, into a number of smaller files - breaking-up the documentation into a README covering the basics and a Texinfo manual (with HTML format hosted at my personal site) - introducing a new score file format: instead of serializing rules as flat lists, they are now serialized as property lists (enabling better validation & error messages)

Another way would be to redefine parts of the bind-key macro or its use-package support functions

The package-install call installs use-package that provides a utility of the same name to make it easier to manage packages. It's admittedly a little overkill for this specific config, but it's a cheap investment that sets you up for later success.

Granted, the Doom macro makes your code looks nice and compact. But you can get very close to that just by using do-list and define-key together. Or by using the bind-key.el package, which is included with Use-package.

> Deps is well documented.

> The issue I personally found is that I needed to look at a bunch of OS project's deps.edn to see how people commonly structure things. Other than that it is a simple tool.

This strikes me as a contradiction, because if it was well documented you wouldn’t need to look at other people’s configs to see how to use it.

My experience with deps.edn is that every time I start a project and make a deps.edn file, I immediately draw a blank and don’t know how to structure it, so I open ones from other projects to start lifting stuff out of them.

I still don’t know how to reliably configure a project to use nrepl or socket repl without just using an editor plugin. I definitely have no idea how to use those in conjunction with a tool like reveal.

To me, none of that is simple. Simple would be like Emacs’ use-package. With that I know how to add dependencies, specify keybinds, and do initialization and configuration off the top of my head. And it has really nice documentation with tons of examples.

https://github.com/jwiegley/use-package

Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).

I'm using use-package as my package manager and the package ligature for the ligatures.

I have been crafting my emacs config for about 10 years. I started with vanilla and intentionally stayed away from frameworks. About two years ago I declared config bankruptcy and went down for a rewrite using use-package and straight.

ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package

use-package! is a macro over use-package, and respect its syntax, with a few additions. Useful reference on use-package keywords.