I have an ExFAT drive which carries my works, including codes that I'll be using between Mac and Windows. I've always used TUI GNU Emacs on this drive to ensure no resource fork is accidentally created.
Recently, I re-installed the entire operating system to eliminate a problem with Native Instruments softwares that I didn't manage to find the cause. Since then, whenever I create or modify a file on the ExFAT drive from iTerm2 command line, resource fork for that file gets created. I tried the Apple Terminal, it won't create resource fork even for the exact same commands I've typed on iTerm2.
How should I prevent resource fork from being created by iTerm2 in this case?
Thanks for the answer from @Tetsujin (刺青人?), But I insist on finding the problem with iTerm2. This ExFAT drive is primarily for coding and exchanging data with other computers (Win, Linux, BSDs, whatever other lesser known OSs.)
Lacking ACL and permissions is considered a plus for my purposes. Also, my creativity works are on another APFS drive to get backed up in Time Machine, so no worry they get harassed by a foreign OS.