CONFLICT(1)

💖 CONFLICT(1) — the manual page, but make it a group chat 💖

okay bestie, welcome to conflict, a lil User command that's literally just here to spill the tea on your filename conflicts. no cap. 🫶

---

✨ NAME ✨

conflict — filename conflict listing 🌸

---

✨ SYNOPSIS ✨

conflict [options] [file-specifications]

---

✨ DESCRIPTION ✨

So here's the vibe: conflict shows you all the conflicting filenames hanging out in your execution path. And like, unlike the csh command which? it shows all of the (non-alias) executable files in your path. all of them. the whole squad. 👑

Here's how it does its thing: conflict reports pathname conflicts by making a list of the directories that are listed in the environment variable PATH, and then it scans those directories for executable files. If you give it arguments, the test for executable files gets limited to the names you gave it (after stripping the directory-prefix, obviously 💅).

The first instance of a name in a given path (and those hard-linked to it) gets marked with "*". The ones that come after it get marked with "+" marks. iconic behavior honestly.

The report goes to standard output and it always shows you the list of directories. Conflicting names are reported on the succeeding lines. periodt. ✨

---

✨ OPTIONS ✨

• -c — do not ignore case when comparing filenames (go peek at -i for the flip side of this).
• -e name — specify a different environment variable than PATH (like, say, INFOPATH or LD_LIBRARY_PATH, you get it).
• -I path — for compatibility with C-preprocessor options, build up the search path with the given directory. (The matching -D and -U options are ignored, they're just there for the vibe.) Heads up: using -I or -L overrides the use of environment variables for the search path. 💀
• -i — ignore case when comparing filenames (see -c).
• -L path — for compatibility with C-compiler options, build up the search path with the given directory.
• -p — print pathnames only, rather than the table. no table bestie, just names. 🎀
• -r — look for readable files 👀
• -t types — specify a list of file types that get treated as conflicting. The option value is a list of file suffixes (a "." followed by zero or more other characters). The list separator is the "." which begins each suffix, like:

conflict -t.exe.com

If you don't give a -t option at all, a built-in list of executable file types gets used for systems where this is known. 🦋

• -v — Use verbose option to control how much is shown. Repeat the option for different levels:
  • 1 — show all directory names
  • 2 — show all filenames which are found in the directories
  • 3 — directs conflict not only to print a summary line for each file, but also to print a running summary, showing executable file (with its full path) as it is found). 🔥
• -V — print the version, exit. bye bestie 👋
• -w — look for writable files
• -W number — expand width of display by number of columns (default: one column per path).
• -x — look for executable files (the default). the classic. the moment. ✨

You may combine the "-r", "-w" and "-x" options, they play nice together 🫶. And if you don't specify one of these, conflict just assumes "-x". no thoughts, default head.

---

✨ OPERATIONS ✨

You can use conflict to list all the conflicting names in your path (if you give it no arguments), or to find conflicts for one specific name. And if you wanna list only conflicts from a particular directory path, you may type:

conflict -a path/*

An example of the use of conflict is shown below 👇

bsd4.2(5) conflict
Current working directory is "/home/dickey/src/conflict"
-> .
--> /home/dickey/bin
---> /home/dickey/com
----> /bin
-----> /usr/bin
------> /usr/ucb
-------> /usr/local/bin
-*----+: args
----*-+: calendar
---*--+: cc
*+-----: conflict
...

the arrows?? the asterisks?? it's giving tree diagram but make it chaos 🌈

---

✨ ENVIRONMENT ✨

conflict runs in a POSIX environment, as well as MSDOS, Win32 and OS/2 command-line. versatile queen. 💅

---

✨ FILES ✨

conflict is a single binary module, which uses no auxiliary files. self-sufficient. main character energy only, no entourage. 👑

---

✨ ANTICIPATED CHANGES ✨

• add option to get aliases from the shell
• handle compound directory structures such as MANPATH.
• show symbol conflicts from object files and libraries.

(someday bestie, someday 🌸)

---

✨ AUTHORS ✨

Thomas Dickey 🫶

---

✨ SEE ALSO ✨

• sh(1) for a discussion of type.
• csh(1) for a discussion of which.

---

and that's the whole page bestie, we ate and left zero crumbs 💖 this was Check filename-conflicts, version-dated 2024-04-29, filed under CONFLICT(1) in the manual — mwah, tysm for reading, go check your PATH fr fr ✨🎀🦋