minput_config_file(3m17n)

✨ NAME ✨

minput_config_file — bestie, this is the one that tells you where your personal m17n config file lives 💖 (and yeah, the manual name is m17n, the manual is 3m17n, if you were wondering 🎀)

---

🌸 SYNOPSIS 🌸

char* minput_config_file (void)

---

🦋 DESCRIPTION 🦋

okay so. minput_config_file() hands you the name of your per-user customization file. 🫶

It returns the absolute path name of that per-user customization file — the exact one that minput_save_config() writes your configurations into. 💅

Usually? It's config.mic chillin' inside the directory ${HOME}/.m17n.d (where ${HOME} is, duh, your home directory 🏠).

⚠️ but bestie, listen — it is not assured that a file with the returned name actually exists, and it's not assured that it's readable or writable. it's giving "here's a path, good luck." 😭

So if minput_save_config() fails and returns -1, an application program might wanna check that file, make it writable (if possible 💀), and then try minput_save_config() again. main character problem-solving energy, honestly. 👑

---

👑 RETURN VALUE 👑

This function returns a string. ✨

And here's the catch, no cap: because that string is kept in the library, the caller must not modify nor free it. 🙈 hands off, it's not yours.

---

🎀 SEE ALSO 🎀

• minput_save_config()

---

💜 COPYRIGHT 💜

Copyright (C) 2001 Information-technology Promotion Agency (IPA)
Copyright (C) 2001-2011 National Institute of Advanced Industrial
Science and Technology (AIST)
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License
<http://www.gnu.org/licenses/fdl.html>.

---

Version 1.8.4, dated Mon Sep 25 2023 — and that's the whole page, bestie. slay, go save your configs. 💅💖🌸🦋✨