CSA_DELETE_CALENDAR(3)

💅 csa_delete_calendar — delete a calendar from the calendar service 🗑️✨

okay so real talk, bestie — this one's a library call, and it's the one that ghost-deletes a whole calendar off the calendar service. yeeting a calendar, basically. icon behavior, honestly.

---

🌸 SYNOPSIS 🌸

#include <csa.h>
CSA_return_code csa_delete_calendar(
CSA_session_handle session,
CSA_extension *delete_calendar_extensions);

like, that's the whole summoning ritual. two args, no drama. 💅

---

🦋 DESCRIPTION 🦋

so csa_delete_calendar deletes a calendar on the calendar service. that's it, that's the function. 💀

but here's the ✨vibe check✨ and it's kinda the whole thing: only the owner of the calendar, or a user with the owner authority, can remove the calendar from the calendar service. like if you're not the owner and you don't have owner authority, bestie, you are not getting in. no cap. 🙈

---

🎀 ARGUMENTS 🎀

⭐ Session (Session Handle)

an opaque session handle that represents a session with the calendaring service. iykyk — it's opaque, so don't go poking at its insides, that's not the vibe. 🫶

session handles are created by a logon function call and invalidated with a logoff function call. so like, a session handle is born at logon and it ✨perishes✨ at logoff. if the session handle is invalid, then the error CSA_E_INVALID_SESSION_HANDLE is returned. periodt. 💅

🌈 Delete Calendar Extensions (Extension)

a pointer to an array of CSA_extension structures for this function. and it's giving versatile because the array may contain both input extensions (for providing additional information to the function) and output extensions (for receiving information from the function). multitasking queen. 👑

a value of NULL indicates that the caller is not using any extensions. see the extensions structure for more information. 📚

---

🔥 RETURN VALUE 🔥

🍓 Delete Calendar Extensions (Extension)

if output extensions were passed to the function in the extensions list, the results from the service will be available in the extension. see the extensions structure for more information. 📬

and then the big question, the one we all care about: whether the function succeeded or not, and, if not, why. it may be success or one of the values listed under ERRORS below. so like… vibe check passed or vibe check failed, and if it failed you get receipts. 🧾

---

💀 ERRORS 💀

the csa_delete_calendar function returns the following error values. brace yourself bestie, there's a whole roster:

• CSA_E_DISK_FULL — insufficient disk space was available to complete the requested operation (this may refer to local or shared disk space). storage said no. 😭
• CSA_E_FAILURE — there was a general failure that does not fit the description of any other error code. the classic "something happened, don't ask me what" energy. 🫠
• CSA_E_INSUFFICIENT_MEMORY — insufficient memory was available to complete the requested operation.
• CSA_E_INVALID_FUNCTION_EXT — the function extension requested is invalid.
• CSA_E_INVALID_FLAG — a flag value in the flags argument was invalid.
• CSA_E_INVALID_PARAMETER — a function parameter was invalid.
• CSA_E_INVALID_SESSION_HANDLE — the specified Session Handle is invalid or no longer valid (e.g., after logging off). you logged off, girl, the handle's gone 💀
• CSA_E_NO_AUTHORITY — the user has insufficient authority for this function. you're not the owner and you don't have owner authority, so respectfully… no. 🚫
• CSA_E_NOT_SUPPORTED — the operation requested is not supported by this implementation.
• CSA_E_SERVICE_UNAVAILABLE — the requested calendar service is unavailable. she's not answering her phone rn. 📵
• CSA_E_UNSUPPORTED_FLAG — the flag requested is not supported.
• CSA_E_UNSUPPORTED_FUNCTION_EXT — the specified function extension is not supported or CSA_EXT_REQUIRED is set.

fr fr though — that last one has a little or in it: not supported or CSA_EXT_REQUIRED is set. both paths land you on the same error, so don't @ me. 💜

---

👑 SEE ALSO 👑

csa/csa.h — csacsa(5), csa_add_calendar(3), csa_add_entry(3), csa_call_callbacks(3), csa_delete_entry(3), csa_free(3), csa_free_time_search(3), csa_list_calendar_attributes(3), csa_list_calendars(3), csa_list_entries(3), csa_list_entry_attributes(3), csa_list_entry_sequence(3), csa_logoff(3), csa_logon(3), csa_look_up(3), csa_query_configuration(3), csa_read_calendar_attributes(3), csa_read_entry_attributes(3), csa_read_next_reminder(3), csa_register_callback(3), csa_unregister_callback(3), csa_update_calendar_attributes(3), csa_update_entry_attributes(3).

like the whole friend group showed up. the roster ate. 🌈✨

---

and that's the page, bestie 🫶 — this one's from the csa_delete_calendar(library call) corner of the manual (that's the title up top and the header/footer too, yeah they really put it twice, iconic of them), and it's filed as a library call. mwah 💋 go delete a calendar (only if you own it, i'm not getting in trouble for you)