On 17 Jul 2000, Alex Schroeder wrote:
> I prefer the "plain string zip codes" patch to adding strings as a new
> zip code datastructure, because it simplifies the code. The "plain
> string zip codes" patch already has migrations functions that work.
>
> I think simplification of the code is a g
Sam Steingold <[EMAIL PROTECTED]> writes:
> > Hm, if we have bbdb-zip-canonicalize, then the old problem re-appears:
> > whenever a new format of zip codes is "discovered", somebody has to
> > update the code.
>
> you missed the whole point!
>
> 1. canonicalization can be turned off at any ti
> * In message <[EMAIL PROTECTED]>
> * On the subject of "Re: Postal codes"
> * Sent on 17 Jul 2000 13:16:45 +0200
> * Honorable Alex Schroeder <[EMAIL PROTECTED]> writes:
>
> Sam Steingold <[EMAIL PROTECTED]> writes:
>
> > I think we sh
Sam Steingold <[EMAIL PROTECTED]> writes:
> I think we should keep all phone numbers as strings, and have a user
> variable bbdb-phone-canonicalize which should be nil for "as is" or a
> function which is applied to the phone and should return the
> canonicalized phone string.
>
> Same for zip c
On July 15, [EMAIL PROTECTED] said:
> I think we should keep all phone numbers as strings, and have a user
> variable bbdb-phone-canonicalize which should be nil for "as is" or a
> function which is applied to the phone and should return the
> canonicalized phone string.
>
unless I'm mistaken, y
Sam Steingold <[EMAIL PROTECTED]> writes:
> I find phone canonicalization enormously useful.
>
> I think we should keep all phone numbers as strings, and have a user
> variable bbdb-phone-canonicalize which should be nil for "as is" or a
> function which is applied to the phone and should return
Kevin Davidson writes:
> John F. Whitehead writes:
> John> `bbdb-north-american-phone-numbers-p'
> Sorry. Doesn't work for the default area code stuff. The Edinburgh
^
Well, that could actually be made a string, or are there any
objections ?
Jamie Zawinski writes:
> All of you damned furriners should just get your green cards or
> something and quit whining.
And what would it help with my grandma´s phone number ;-?
Even permanently moving to the US doesn´t make you American (i.e.,
playing World Series without including Japan ;-)
>>>> In message <[EMAIL PROTECTED]>
>>>> On the subject of "Re: Postal codes"
>>>> Sent on 14 Jul 2000 17:04:33 +0100
>>>> Honorable Kevin Davidson <[EMAIL PROTECTED]> writes:
>>
>> If I had time I'd rip
> "Jamie" == Jamie Zawinski <[EMAIL PROTECTED]> writes:
Jamie> All of you damned furriners should just get your green
Jamie> cards or something and quit whining.
What would I do with it?
Is there a
green card <-> BBDB
interface?
Jamie> --
Jamie> Jamie Zawinski
Jamie> [
All of you damned furriners should just get your green cards or
something and quit whining.
--
Jamie Zawinski
[EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
___
bbdb-info mailing list
[EMAIL PROTECT
Kai Großjohann writes:
> Is there anybody who likes the default behavior
> (bbdb-north-american-phone-numbers-p non-nil)?
I like the default behavior as I deal mostly with North American
numbers.
> let's remove the North America specific code
I would prefer that the default value of
``bbdb-north-
On 14 Jul 2000, Kevin Davidson wrote:
>> In article <[EMAIL PROTECTED]>, "John
>> F. Whitehead" <[EMAIL PROTECTED]> writes:
> John> and re, phone # behavior, you can change this with:
>
> John> `bbdb-north-american-phone-numbers-p' (buffer: *Hyper
> John> Apropos*, mode: Hyper-Apropos)
>
/ Kevin Davidson <[EMAIL PROTECTED]> was heard to say:
| If I had time I'd rip out all the phone number parsing stuff (does it
| actually do anything useful ?) and just replace it all with opaque
| strings. In fact given the number of US phone numbers I've seen that
+1 :-)
> In article <[EMAIL PROTECTED]>, "John F. Whitehead"
><[EMAIL PROTECTED]> writes:
John> and re, phone # behavior, you can change this with:
John> `bbdb-north-american-phone-numbers-p' (buffer: *Hyper Apropos*, mode:
Hyper-Apropos)
Sorry. Doesn't work for the default area code stuff. The
> On July 13, Kevin Davidson <[EMAIL PROTECTED]> wrote:
> BBDB actually does a fairly good job of the last, with the exception
> of non-human entries who get sorted by the last word in their `name',
you can sort on any word you want by giving a prefix argument to
bbdb-record-edit-name.
> In article <[EMAIL PROTECTED]>, Norman Walsh <[EMAIL PROTECTED]> writes:
Norman> / Alex Schroeder <[EMAIL PROTECTED]> was heard to say:
Norman> | Maybe we should make it our goal for the next file version to switch
Norman> | to plain strings... :)
Norman> It gets my vote.
Me too
I've j
/ Alex Schroeder <[EMAIL PROTECTED]> was heard to say:
| Maybe we should make it our goal for the next file version to switch
| to plain strings... :)
It gets my vote.
Be seeing you,
norm
--
Norman Walsh <[EMAIL
be stored in a number,
therefore next time around, the leading zero has disappeared.
> I've long been puzzled by the attempt to store postal codes in some
> semantic way (as numbers or lists of strings). Would it not make more
> sense to store them as opaque strings (in V6, I suppose
Jul 2000
I've long been puzzled by the attempt to store postal codes in some
semantic way (as numbers or lists of strings). Would it not make more
sense to store them as opaque strings (in V6, I suppose :-)
I ran into another problem with a three-part international postcode.
The BBDB seemed to
20 matches
Mail list logo
