From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Jorge P. de Morais Neto <jorge+list@disroot.org>
Cc: 38918@debbugs.gnu.org
Subject: bug#38918: 26.3; EBDB fails to edit (add) tags
Date: Tue, 07 Jan 2020 09:37:02 -0800 [thread overview]
Message-ID: <87h817uq0x.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87d0bv1mmb.fsf@disroot.org> (Jorge P. de Morais Neto's message of "Tue, 07 Jan 2020 09:23:24 -0300")
Jorge P. de Morais Neto <jorge+list@disroot.org> writes:
> Em [2020-01-06 seg 11:40:30-0800], Eric Abrahamsen escreveu:
>
>> Oh, sorry, these two were actually the same problem, and all should be
>> fixed now. I've done a 0.6.12 release -- would you update when it's
>> available and check that this fixes everything? Though I'm not sure
>> if it will address your other error. Let's get this closed out first.
>
> Yes, with EBDB 0.6.12 I can insert and edit tags, and I can edit them
> with both "e" and "E". The error message when, in the extended
> customize interface ("E"), I hit "[Apply]" and then "[Accept]", also
> seems to have been fixed. There is still one quirk: when I insert a
> tags field on a record that already has a tags field, EBDB overwrites
> the old field and, when it asks for the tags, it does not offer the
> previous ones as default. It would be more user-friendly if EBDB either
> offered the previous tags as default, or simply signaled an error with a
> short and clear message.
Yes, this isn't ideal; there's no indication of which fields are
"singletons" and which aren't. I think you're right that inserting a new
field should essentially behave like editing the old one -- actually
maybe that's all that needs to happen. That plus a message afterwards.
I'll take a look.
> And two feature requests:
>
> 1. Undo. So far I have never suffered much for the lack of undo (it is
> only an inconvenience) and of course I leave it up to you to
> prioritize this feature, but it would be useful, though clearly not
> as useful as 2:
I've thought about this in the past. Each record has a "cache" object
that stores metadata and computed strings for the record, and this would
be natural place to store undo information. A dumb implementation could
store entire copies of the record as it is edited, and allow you to
switch them out. Alternately, the vCard specs provide for a versioning
system for individual properties
(https://tools.ietf.org/html/rfc6350#section-7), maybe I could adapt
that once I've gone and figured out how it works.
> 2. Compatibility with other contacts formats. I would like to import my
> Gmail contacts and complete my transition away from G$$gle spyware.
This is definitely on the roadmap, and taking me too long. Presumably
you'd export your Gmail contacts as a vCard file? Or something else? I'm
in the middle of writing a vCard parser, which is actually a separate
library from EBDB (so other software can use it), but will be used in
EBDB code.
Anyway, if we're talking about importing vCards, that's on the way.
> Should I open two bug reports for these two feature requests?
For the undo feature, please -- it's not high priority but it would be
good to keep track of. I've already got Github issues open for the other
request.
Thanks,
Eric
next prev parent reply other threads:[~2020-01-07 17: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 [this message]
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
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=87h817uq0x.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=38918@debbugs.gnu.org \
--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).