Open brabalan opened 6 months ago
What's happening is that EBDB thinks this is a person's name, and assumes that OCSF is the surname (in accordance with the UN-style of notation where the family name is all-caps). The right solution here is to create this record as an organization, not a person (I'm assuming it's not a person) which you can do with "C" instead of "c" in the EBDB buffer. The name field passes through unmolested, that way.
If the default behavior is annoying to you for person records, as well,
you can set ebdb-read-name-articulate
to t.
Thank you, I see. I was using ebdb-create-record
for this… I do not see the name of the same function for organizations. What is it? And can I convert a record or do I need to delete it and re-create it? (I have many records for mailing lists which should not be persons either…)
There isn't a separate command for making organizations, instead you can use the "extended create" command (bound to capital-c "C"), which will prompt you for the record type.
Unfortunately there's no good way to convert records from one type to another. There's also no mailing list record type yet (though I'm sort of working on it, see #92). If you have any ideas in that direction, feel free to contribute to that bug report!
Thank you for these details, I’ll have a look.
When entering new records in ebdb, the casing of what I enter is modified and I cannot seem to change it back. For instance, if I create a record for "OCSF ComExec", I get the name "ComExec Ocsf". Is there an option I can set to disable this behavior?