zsh-workers
 help / color / mirror / code / Atom feed
From: Mr M P Searle <csubl@csv.warwick.ac.uk>
To: schaefer@brasslantern.com (Bart Schaefer)
Cc: zsh-workers@math.gatech.edu
Subject: Re: PATCH: NO_CLOBBER
Date: Thu, 23 Apr 1998 18:43:27 +0100 (BST)	[thread overview]
Message-ID: <199804231743.SAA25751@crocus.csv.warwick.ac.uk> (raw)
In-Reply-To: <980423094444.ZM28976@candle.brasslantern.com> from Bart Schaefer at "Apr 23, 98 09:44:44 am"

> 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.

I meant a list of all such devices possible on a system - including those
not installed. Of course this list could be overridden or added to from
config files, but without any reconfiguration all devices could be
checked for. There wouldn't usually be other devices except when the OS
was upgraded, where the zsh port also would be. 

> 
> -- 
> Bart Schaefer                                 Brass Lantern Enterprises
> http://www.well.com/user/barts              http://www.brasslantern.com
> 


  reply	other threads:[~1998-04-23 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-23  9:13 Andrew Main
1998-04-23 14:22 ` Peter Stephenson
1998-04-23 14:49   ` Bruce Stephens
1998-04-23 15:26     ` Mr M P Searle
1998-04-23 16:44       ` Bart Schaefer
1998-04-23 17:43         ` Mr M P Searle [this message]
1998-04-23 18:44   ` Andrew Main

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199804231743.SAA25751@crocus.csv.warwick.ac.uk \
    --to=csubl@csv.warwick.ac.uk \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).