Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: NO_CLOBBER
- X-seq: zsh-workers 3863
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx (Zsh hackers list)
- Subject: Re: PATCH: NO_CLOBBER
- Date: Thu, 23 Apr 1998 09:44:44 -0700
- In-reply-to: <199804231422.QAA15790@xxxxxxxxxx>
- In-reply-to: <vbson4vbj7.fsf@xxxxxxxxxxxxxxx>
- In-reply-to: <199804231526.QAA09055@xxxxxxxxxxxxxxxxxxxxxxxx>
- References: <199804231422.QAA15790@xxxxxxxxxx> <vbson4vbj7.fsf@xxxxxxxxxxxxxxx> <199804231526.QAA09055@xxxxxxxxxxxxxxxxxxxxxxxx>
On Apr 23, 4:22pm, Peter Stephenson wrote:
} Subject: Re: PATCH: NO_CLOBBER
}
} Andrew Main wrote:
} > Looks like someone got too clever, and decided that NO_CLOBBER shouldn't
} > stop you opening a FIFO.
}
} hmm, it wasn't me, but now:
} /etc/zshrc: file exists: /dev/null [243]
} am I just going to have to live with this? Seems quite a lot to live with.
Device special files are not FIFOs, so even if the ksh incompatibility needs
to be rectified (which doesn't seem essential to me), the code needs to work
right for devices. The old code with errno saved/restored would be better.
On Apr 23, 4:26pm, Mr M P Searle wrote:
} Subject: Re: PATCH: NO_CLOBBER
}
} IMO a list that can be changed would be better than just checking for
} /dev/null. An example on my system is the sound devices /dev/audio,
No, a list is not acceptable either. New devices can appear, even on a
running system; having to recompile or reconfigure zsh every time one
does, is just plain wrong.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author