On Monday, August 6 2001 10:15:30, Colin Rafferty wrote:
[...]
> I hate changing names just for the sake of changing names.
Well me too, but they are not just changed for the sake of
changing names, but also for minor functionality changes and
better naming.
> > Your are right, bbdb-one-line-display-* is much better than
> > *elided*, at least in my eyes.
>
> This I might agree with, since the t/list seems like its being
> overloaded a little too much. However, having two different variables
> makes the interactive weird. Namely, the variable with the list of
> fields is unused if we are in single-line mode.
I do not really get the point, what variable are you speaking
of? And what do you mean by "makes the interactive weird"?
> All in all, I like the idea of having one variables.
And I like to be able configuring one-line and multi-line
layout separately.
> > o.k. so how about renaming the other variables to
> > bbdb-multi-line-display-*?
>
> > bbdb-one-line-display-fields (bbdb-elided-display-fields)
> > list of fields which should be displayed in one-line display
>
> This is the exact opposite of the -elided- version, and a bad choice.
No it is exactly the same. The variable bbdb-elided-display-fields
is the only way to allow displaying different fields in one-line
layout. BBDB in one-line layout used to display just the
name, comp, phones, net and when adding a new field it was
never displayed before ...
> If I add a new field interactively, I now need to add that field to
> this variable. This is like something that I will not remember.
Yes you have to add it by hand.
> Anyway, how do I specify that I want to see everything? With a nil?
> Remember that a nil is just an empty list, so nil is the only way to
> say that I want to see nothing but the name.
There is no way so far, but how about `nil' for omitting all
fields and `t' for all/rest? E.g. '(phone net t) to get
phone and net first and then the remaining fields and `t' or
'(t) for displaying all fields?
> In general, using -elided- style is easier, since if I see something
> that I don't want to, I can just add it to my list. However, I would
> never know that I am not seeing something that I would like to.
Somehow you misunderstood something, since my docs were
missleading, maybe it becomes cleared here by:
bbdb-multi-line-display-fields-order (bbdb-display-fields-order)
list of fields that should be displayed first in multi-line display.
BTW bbdb-display-fields-order this is a new variable I just
added with the last commit, and so I feel kind of free to
change its name to something more reasonable.
> > How about theses warnings of name/functionality changes
> > should they go into the code (warn/compile) or the
> > documentation?
>
> See `make-obsolete-variable'.
And howlong do one retains this before removing the variable
finally?
Bye Robert
_______________________________________________
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
