From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Deus Max <deusmax@gmx.com>
Cc: "Jorge P. de Morais Neto" <jorge+list@disroot.org>,
38918@debbugs.gnu.org
Subject: bug#38918: 26.3; EBDB fails to edit (add) tags
Date: Sat, 18 Jan 2020 10:37:51 -0800 [thread overview]
Message-ID: <87r1zwpq4g.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878sm468in.fsf@aia00054aia.gr> (Deus Max's message of "Sat, 18 Jan 2020 18:20:48 +0200")
On 01/18/20 18:20 PM, Deus Max wrote:
> On Tue, Jan 14 2020, Eric Abrahamsen wrote:
>
>> Jorge P. de Morais Neto <jorge+list@disroot.org> writes:
>>
>>
>>> Besides, it seems that the function `org--tag-add-to-alist' does not
>>> exist on the Org Mode version (9.1 IIRC) that comes with Emacs 26.3. I
>>> think you should document that the Org Tags functionality depends on
>>> recent Org Mode. Also, maybe (I don't know if this would be worth your
>>> time) EBDB could provide a clear error message when the user attempts to
>>> use that functionality on an old Org Mode. Currently it lets Emacs
>>> complain that the symbol's value as a function is void.
>>
>> This is a bigger problem -- I'm committed to supporting Emacs 25. I
>> think I'll just write my own function (read: copy and paste Org's) to do
>> the same thing.
>>
>> Thanks,
>> Eric
>
> Hi Eric,
>
> It's a bad practice to duplicate functions from other packages. At least
> maybe you could enclose the definition in a (eval-after-load 'org ...)
> construct and provide org--tag-add-to-alist only if it is not defined.
> That way you will also be able to provide a message recommending an
> upgrade to a more recent org-mode.
I would definitely do that, except the function is "private" to begin
with. I raised this on the Org mailing list, but got no response. I
suppose the proper thing to do would be to contribute a public function
to Org that does what I want, then also define it in EBDB, and do a
`defalias' in `eval-after-load', as you describe.
next prev parent reply other threads:[~2020-01-18 18:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 14:17 bug#38918: 26.3; EBDB fails to edit (add) tags Jorge P. de Morais Neto
2020-01-04 17:58 ` Eric Abrahamsen
2020-01-04 18:55 ` Eric Abrahamsen
2020-01-05 0:02 ` Jorge P. de Morais Neto
2020-01-05 0:35 ` Eric Abrahamsen
2020-01-05 0:43 ` Eric Abrahamsen
2020-01-05 10:49 ` Jorge P. de Morais Neto
2020-01-06 18:43 ` Jorge P. de Morais Neto
2020-01-06 18:46 ` Jorge P. de Morais Neto
2020-01-06 20:25 ` Eric Abrahamsen
2020-01-06 20:49 ` Eric Abrahamsen
2020-01-06 19:40 ` Eric Abrahamsen
2020-01-07 12:23 ` Jorge P. de Morais Neto
2020-01-07 17:37 ` Eric Abrahamsen
2020-01-12 13:49 ` Jorge P. de Morais Neto
2020-01-12 17:10 ` Eric Abrahamsen
2020-01-14 11:50 ` Jorge P. de Morais Neto
2020-01-14 22:46 ` Eric Abrahamsen
2020-01-18 16:20 ` Deus Max
2020-01-18 18:37 ` Eric Abrahamsen [this message]
2020-01-07 19:14 ` Eric Abrahamsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1zwpq4g.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=38918@debbugs.gnu.org \
--cc=deusmax@gmx.com \
--cc=jorge+list@disroot.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).