girzel / ebdb

An EIEIO port of BBDB, Emacs' contact-management package
67 stars 11 forks source link

snarfing unreliable #58

Closed jave closed 6 years ago

jave commented 6 years ago

I guess snarfing works as advertized, that is, it is unreliable.

is there some other way to do low-budget snarfing? perhaps just have the cursor on an email address and do thing-at-point or something?

girzel commented 6 years ago

What's most unreliable is parsing large chunks of free-form text and finding field information from it. If you narrow down the focus, it should work okay. Email addresses, in particular, should be okay, so long as you put the region around them fairly tightly. If you've got this:

name@domain.com

And just mark that, ebdb-snarf should do the right thing. Same with:

John Doe name@domain.com

If John Doe is already in the database, EBDB will just offer to add the mail address to the record.

Use the region!

jave commented 6 years ago

okay, i think i got bitten by ";-s" being bound to ebdb-mua-snarf-article, rather than ebdb-snarf

girzel commented 6 years ago

ebdb-mua-snarf-article is currently mostly wishful thinking. At some point in the next few months I will sit down and try to make it work better, and so I'll leave this bug report open. In the meantime, though, you'll have to do it manually, with the region.

girzel commented 6 years ago

@jave If you're running this from github and still interested, give these changes a try -- I hope message snarfing will be a bit more reliable now. I haven't yet flushed the changes to Elpa, tho.

girzel commented 6 years ago

Anyhoo, I'm going to close this one, as I think the general "it doesn't work" problem is resolved. Further bugs can have their own issues.

jave commented 6 years ago

Eric Abrahamsen notifications@github.com writes:

Anyhoo, I'm going to close this one, as I think the general "it doesn't work" problem is resolved. Further bugs can have their own issues.

Thanks, I'll try it out soonish, but I'm a bit swamped atm.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

-- Joakim Verona joakim@verona.se