From: Bastien <firstname.lastname@example.org> To: Daryl Manning <email@example.com> Cc: Julien Danjou <firstname.lastname@example.org>, Org-mode <email@example.com> Subject: Re: Improving org-contacts performance (and state of development in general) Date: Sun, 06 Sep 2020 18:27:51 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAL9aZkvT5XqWaMTHJyree4G_Ri0Kupx_Xc1yD3-e8VPHYvngVw@mail.gmail.com> (Daryl Manning's message of "Mon, 7 Sep 2020 00:20:35 +0800") Hi Daryl, Daryl Manning <email@example.com> writes: > Is there a solid, forked branch anywhere that focuses on enhancing > performance anywhere? Note that I'm aware of, but I don't use org-contacts.el, so maybe other will have more information. > I'm tempted to wade in and add features and improvements myself but > my elisp-fu is dodgy at best (more golang these days.). I'm copying Julien, the original author of org-contacts.el, to check if he plans to maintain org-contacts.el further and if he's okay for someone to take over. That someone could be you: better to have a maintainer than no one. Also, org-contacts.el is part of the "contrib/" directory in Org's repository and soon after 9.4 we will strip this directory out of the org-mode.git repo, so having someone taking care of individual contrib packages would be really appreciated. > I'd be interested in what people are doing to speed it up (and if it > is under anything like active development for improvements. It does > feel super handy, and feels like it just needs a performance and more > modern features overhaul - more on interoperability and less on > in-emacs interoperability.). I'm afraid most tricks will be general Org tricks, no directly related to the code in org-contacts.el -- but perhaps I'm wrong. Best, -- Bastien
next prev parent reply other threads:[~2020-09-06 16:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-06 16:20 Daryl Manning 2020-09-06 16:27 ` Bastien [this message] 2020-09-07 8:27 ` Julien Danjou 2020-09-07 14:41 ` Bastien 2020-09-07 2:26 ` Ihor Radchenko 2020-09-07 2:52 ` Daryl Manning 2020-09-07 8:36 ` Ihor Radchenko 2020-09-07 14:43 ` Bastien 2020-09-07 15:01 ` Ihor Radchenko 2020-09-10 21:45 ` TRS-80
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.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Improving org-contacts performance (and state of development in general)' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git 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).