org-super-agenda VS melpa

I've been configuring a custom agenda view for use with org-super-agenda similar to the very last example in the examples page. I also use org-modern.

Maybe org-super-agenda can help you with that.

But for me the most important aspect is org-agenda and in particular with packages like org-super-agenda, org-ql, and orgzly an excellent Android app. You configure the parameters and it shows you tasks/notes grouped/sorted by whatever attributes you want--priority, tags, deadline, keywords, etc. It takes a matter of 3 seconds to search for tasks with priority A to do within 2 weeks, for example (or you can of course pre-configure that search parameter bound to a hotkey--I have agenda views for different aspects of my life like school, work, business, shopping, etc.). The interface provides you the ability to quickly mark tasks and modify their properties in bulk like priorities and deadlines, etc.

Maybe https://github.com/alphapapa/org-super-agenda ?

I am a big fan of alpahapapa's org-super-agenda for my GTD dashboard (tho need to update it for org-ql). However, I have this weird thing that happens with my config that I've been unable to figure out:

Yes it's an old post , so might as well link to one of my fav org-agenda items: org-super-agenda https://github.com/alphapapa/org-super-agenda

Highly recommend looking into org-super-agenda to clean things up, I use it with custom views to only show what I want and in the order I need, helps organize the chaos.

Watch the new pull requests to melpa: https://github.com/melpa/melpa/pulls

(require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t) (package-initialize) (package-install 'use-package) (use-package exec-path-from-shell :ensure t :config (exec-path-from-shell-initialize)))

MELPA is definitely the biggest package archive, probably mostly on account of the lower barrier to entry compared to GNU ELPA (maybe the difference would have been less pronounced if NonGNU ELPA had been there from the beginning, but one can only speculate). MELPA has its own requirements for packages, but indeed copyright assignment to the FSF is not one of them.

I would suggest to start at reading the manual first. Then I would recommend reading the Melpa guidance, even if you do not plan to contribute your package to Melpa, since it contains very useful info about linting, writing your code etc.

The mxtoolbox link checks for SMTP blacklisting.. People won't be able to send mail from host with the IP address 178.128.185.1(which is the melpa.org webserver, not their mailserver, so everything's fine there).

Xah asked for his packages to be removed from MELPA a while back: https://github.com/melpa/melpa/issues/7755

Observe that package.el compile files when they are installed, and they are not compiled in any particular order (actually whatever directory-files returns, which is what OS returns). So if you have multiple files that depend on each other, it is something to think of. There are also some guidelines on how to structure your project on Melpa.