zsh-users
 help / color / mirror / code / Atom feed
From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@sunsite.dk
Subject: Re: "autoload -U" expanding alias
Date: Wed, 24 Mar 2004 21:41:25 +0100	[thread overview]
Message-ID: <18er7fb2633if$.dlg@thorstenkampe.de> (raw)
In-Reply-To: <1040324183610.ZM16086@candle.brasslantern.com>

* Bart Schaefer (2004-03-24 19:36 +0100)
> On Mar 23, 10:43pm, Thorsten Kampe wrote:
> } I have a script that zcompiles some rcfiles. It's asking whether to
> } overwrite files:
> } re-compiling /home/thorsten/.zsh/.zlogout.zwc: mv: overwrite
> } `/home/thorsten/.zsh/.zlogout.zwc.old', overriding mode 0400? 
> 
> This message is happening because of the 0400 file mode, not because of
> any option being passed to the "mv" command.  Files that are not writable
> in directories that are writable trigger this behavior unless "mv -f" is
> used.

I see. But these "0400" ".zwc.old" files are created from zrecompile
itself. This happens only on my Linux box. My Cygwin host has no
problems mv a 0400 file.
  
> } What's happening and how can I prevent this question?
> 
> chmod 0600 the .zwc.old files.  How did they end up mode 0400 ?  Does
> your umask setting typically cause you to create files you can't write?

My umask is 077 so the newly created file from zrecompile should be
mode 600 - not 400.

Thorsten


  reply	other threads:[~2004-03-24 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 21:43 Thorsten Kampe
2004-03-24 18:36 ` Bart Schaefer
2004-03-24 20:41   ` Thorsten Kampe [this message]
2004-03-24 20:53     ` Peter Stephenson
2004-03-25  3:51       ` Bart Schaefer
2004-03-25 10:13         ` Peter Stephenson

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='18er7fb2633if$.dlg@thorstenkampe.de' \
    --to=thorsten@thorstenkampe.de \
    --cc=zsh-users@sunsite.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).