zsh-workers
 help / color / mirror / code / Atom feed
From: "Brian P. Barnes" <bbarnes@dev.tivoli.com>
To: zsh-workers@sunsite.auc.dk
Subject: ZSH and umask on nt?
Date: Thu, 11 Mar 1999 14:27:00 -0600	[thread overview]
Message-ID: <36E82714.CA4B4D8E@dev.tivoli.com> (raw)

Hi,

I am wondering why zsh refused to overwrite any file any time. For all
commands which redirect to an output file, I have to prefix the command
with a "rm OUTPUTFILE;"

I have set the umask to 000 so as not to remove any permissions, and
even files which I own, I can't overwrite. Even if I chmod it to 777 I
can't overwrite it. Here is an example:

C:/bin>umask
000
C:/bin>touch asdf
C:/bin>ll asdf
-rw-rw-rw-   1 544      everyone        0 Mar 11 14:13 asdf
C:/bin>cat asdf > asdf
zsh: permission denied: asdf
C:/bin>chmod 777 asdf
C:/bin>cat asdf > asdf
zsh: permission denied: asdf

It is completely ignoring file ownership.

One other thing I would like to mention is that long command lines (> 72
chars) mangle the input line. After 72 chars, the line is correct:

C:/bin>111111111122222222223333333333444444444455555555556666666666777777777788

After typing the 3rd 8, my command disappears and I get this:

x ç\x03    ?     O 3 x Q

I use ZSH on NT and it is so much better that cmd or even Cygnus Bash.
It's refusal to overwrite files is most aggravating. Then having to
prefix every redirect command with a rm command increases the line size,
often pushing it over the 72 char limit. Again, doubly aggravating.

Thank you,

    Brian




                 reply	other threads:[~1999-03-11 20:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=36E82714.CA4B4D8E@dev.tivoli.com \
    --to=bbarnes@dev.tivoli.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).