EKB_INSERT(1)

💖 EKB_INSERT(1) — the ekb_insert glow-up 💖

okay bestie, gather round, because today we're learning about ekb_insert, a genuinely iconic little User Commands girlie from the E crew. she's giving "quiet utility that does one job and does it well", and honestly? we stan. 🫶

---

✨ NAME ✨

ekb_insert — literally the manual page for ekb_insert 3.5.1. that's it, that's the name section. she's self-aware. 💅

---

🌸 SYNOPSIS 🌸

ekb_insert [options] [names]

---

🦋 DESCRIPTION 🦋

so this is ekb_insert, version 3.5.1, no cap. ✨

her whole thing? she inserts example files into an E knowledge base. every non-option argument you hand her gets treated as one individual example file — one file, one argument, she's not merging them, she's not being cute about it, they're separate. periodt.

🚨 real talk though: for most applications this is obsolete. like, lowkey retired. if you're wondering what to use instead — it's ekb_ginsert. go give her sister a call. 💀

🎀 Options 🎀

okay this is the part where we go through every single flag because bestie we do NOT skip the details in this house. every option, all of them, no exceptions. 💖

• -h, --help — prints a short description of program usage and options. it's giving "hi hello here's how to use me". 👑
• -V, --version — prints the version number of the program. icon behavior, she knows who she is. ⭐
• -v, --verbose[=<arg>] — verbose comments on the progress of the program. ngl she will narrate what she's doing to you. 🗣️ and here's the tea: the short form -v, or the long form without the optional argument, is equivalent to --verbose=1.
• -n <arg>, --name=<arg> — gives the name of the new problem. and if you don't give her one? she's resourceful, she figures it out: she'll take the name of the first input file. OR, if <stdin> is read, she'll cook up a name of the form '__problem__i' — and i is magically computed from the existing knowledge base. yes, magically. that's the word the page uses. manifesting your problem name as we speak. 🧚
• -k <arg>, --knowledge-base=<arg> — selects the knowledge base. if you don't tell her which one, she selects E_KNOWLEDGE by default. she's got a favorite and she's not sorry. 💜

---

😭 REPORTING BUGS 😭

found a bug? spill. report bugs to <schulz@eprover.org>. and please, if possible, include the following, because a bug report with no info is giving "help me help you" energy:

• the version of the package as reported by eprover --version.
• the operating system and version.
• the exact command line that leads to the unexpected behaviour.
• a description of what you expected and what actually happened.
• if possible all input files necessary to reproduce the bug.

---

👑 COPYRIGHT 👑

Copyright 1998-2026 by Stephan Schulz, schulz@eprover.org, and the E contributors (see DOC/CONTRIBUTORS).

This program is a part of the distribution of the equational theorem prover E. You can find the latest version of the E distribution as well as additional information at http://www.eprover.org

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program (it should be contained in the top level directory of the distribution in the file COPYING); if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

We welcome bug reports and even reasonable questions. If the prover behaves in an unexpected way, please include the following information:

• What did you observe?
• What did you expect?
• The output of eprover --version
• The full commandline that lead to the unexpected behaviour
• The input file(s) that lead to the unexpected behaviour

Most bug reports should be send to <schulz@eprover.org>. Bug reports with respect to the HO-version should be send to or at least copied to <jasmin.blanchette@gmail.com>. Please remember that this is an unpaid volunteer service.

The original copyright holder can be contacted via email or as

Stephan Schulz
DHBW Stuttgart
Fakultaet Technik Informatik
Lerchenstrasse 1
70174 Stuttgart
Germany

---

and that's the whole vibe check, bestie — this was ekb_insert version 3.5.1, dated August 2026, out here doing her User Commands thing as EKB_INSERT(1). go forth, insert responsibly, and remember: ekb_ginsert is usually the move. 🌈💖✨