Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!tymix!antares!pnelson From: pnelson@antares.UUCP (Phil Nelson) Newsgroups: comp.sys.amiga Subject: Re: New 1.3 file protection bits Summary: wierd problem with TxEd Plus Keywords: editor TxEd Plus 1.3 protection bits Message-ID: <235@antares.UUCP> Date: 31 Oct 88 00:08:54 GMT References: <3431@leo.UUCP> <2462@m2-net.UUCP> Reply-To: pnelson@antares.UUCP (Phil Nelson) Organization: Tymnet QSATS, San Jose CA Lines: 35 In article <2462@m2-net.UUCP> ba@m-net.UUCP (Bill Allen) writes: >It appears that editing and re-saving any script file with any editor >destroys all pure/script/arc/h bits. >Everything gets reset to "----rwed". >Makes debugging scripts very inconvienent. Why does this happen? >-- A related? problem; I now have two files in my s: dir (on jh0:) that TxEd will not write, no matter how I set the protection bits. I had a script with -s--r--- which I tried to edit, when I tried to save and exit, TxEd did not write the file (of course), but it _said_ it had, twice. the third time I realized my mistake, and set the bits to -s--rw--. Still it would not write the file. So I set to -s--rwed, no go. Also no go for ----rwed. MicroEmacs had no problem with the same file, although it did reset all the extra bits, as above. Also, I can create new files in s: and edit them with TxEd, but after I tinker with the protection, TxEd won't touch them. All this is making me nervous about using TxEd, does anyone know what is going on? >--------------------------------------------------------- >Reply-To: ba@m-net.UUCP (Bill Allen Beogelein) >Organization: M-NET, Ann Arbor, MI >--------------------------------------------------------- -- {ames|pyramid}oliveb!tymix!antares!pnelson | Parallel IQ (the IQ of a group) OnTyme: NSC.P/Nelson POTS: (408)922-7508 | may be easily calculated given Disclaimer: Not officially representing | the IQ of each member - use the McDonnell Douglas Corporation policy. | formula for parallel resistance.