On Sat Dec 3 2011 Ivan Kanis wrote: > >> I got tired of people's name being highlighted red when composing > >> e-mail with flyspell. So this bit of code does an export of peoples > >> first and last name from bbdb to aspell custom dictionaries. > > > > I assume you have the situation in mind that a name appears > > somewhere in the body of a message so that something like > > ispell-message is not solving the problem. > > I don't understand the above, I have read it many times ;)
For the headers of a message spell-checking often does not make much sense. So ispell-message ignores the headers of a message. I don't know much about flyspell. But a quick test shows me that it is looking also into the headers of a message. (It seems to ignore some parts of the headers.) So first I thought your code was supposed to fix the problem that flyspell might find "typos" in the names appearing in the From and To headers of a message, not knowing the spelling of these names. Then it would be a better solution to modify flyspell similar to ispell-message. But of course names from BBDB may appear also in the main body of a message (and there's a good chance you write whatever other text document, where you use such names, too). That's when I thought it can make sense to tell aspell about the spelling of the names in BBDB. > > With my limited time, these days I'd like to focus, first of all, on > > a proper release of BBDB. > > Maybe we could add a contrib directory for this type of things? I know > that stumpwm and slime do that. BBDB used to have that, too, and I guess it still makes sense. At the same time it might help to add things not just randomly as they pop up. (For me a first constraint is that for any new code on savannah I want to make sure the copyright is assigned to the FSF. You already did that.) > > - Could you try to clean up your code such that it separates the > > part that could be useful for more people from your personal > > customizations? > > Of course, I will do that, I first wanted to check if you would > consider it for inclusion. Fine! > I agree with your three specifications. Let me know where you think > the code should belong (maybe bbdb-com.el?) and I'll prepare a > patch. In any case, your code would be self-contained, not requiring any changes in the existing BBDB. In that sense one can decide later where to put it. > > I just realized that this mail was also sent to gnu-emacs-sources. > > This list is for posting code only (and no links). > > I wasn't aware, I prefer a link since it always point to the latest > version... The rationale with gnu-emacs-sources is the other way round. In a year your link might be gone. gnu-emacs-sources gets archived for that very reason. Roland ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
