From: Bastien <firstname.lastname@example.org> To: Maxim Nikulin <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [PATCH] org-protocol: Fix missing '+' in js snippet Date: Fri, 30 Apr 2021 09:21:34 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Maxim Nikulin's message of "Wed, 28 Apr 2021 19:42:28 +0700") Hi Maxim, Maxim Nikulin <email@example.com> writes: > On 28/04/2021 12:40, you wrote: >> Hi Maxim, >> Would you like to volunteer as the maintainer for org-protocol.el? >> For now org-protocol.el indicates that Sebastian Rose, the original >> author, is the maintainer, but I don't think he would mind handing it >> to someone else. > > I am proud to get such offer, but I am afraid, it is too early. I do > not have enough experience with elisp and emacs. Beware of putting a > vimer into maintainer position... Fine :) > Example of my ignorance: I suspect, I did not recognize that > apostrophe needs special escaping in doc strings > https://firstname.lastname@example.org/ > > Actually, I do not think, org-protocol requires a dedicated > maintainer. There are a few things that may be improved, but they > should be discussed at first. It seems, all current user already > managed to configure their handlers and prefer to not experiment any > more. So there is a little interest in this area. I don't use org-protocol.el myself and I'd rather have someone using it being able to reproduce bugs and help maintainers fix problems. Anyway, glad to have your input/patches on org-protocol.el anyway. Thanks, -- Bastien
next prev parent reply other threads:[~2021-04-30 7:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-19 10:53 David Asabina 2021-04-23 12:21 ` Maxim Nikulin 2021-04-28 5:40 ` Bastien 2021-04-28 12:42 ` Maxim Nikulin 2021-04-30 7:21 ` Bastien [this message] 2021-05-02 11:34 ` Maxim Nikulin [not found] ` <20210503152514.bx5gghrqjr3vmxd7@bina> [not found] ` <email@example.com> 2021-05-08 22:32 ` David Asabina 2021-04-28 5:38 ` Bastien
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 \ --subject='Re: [PATCH] org-protocol: Fix missing '\''+'\'' in js snippet' \ /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).