Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: completion ignoring
- X-seq: zsh-users 1557
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Sven Guckes <guckes@xxxxxxxxxxxxxxxxx>, zsh-users@xxxxxxxxxxxxxxx
- Subject: Re: completion ignoring
- Date: Wed, 27 May 1998 09:31:47 -0700
- In-reply-to: <19980527174141.G1747@xxxxxxxxxxxxxxxxx>
- References: <199805221523.QAA17745@xxxxxxxxxxxxxxxx> <199805221534.LAA13850@xxxxxxxxxxxxxxx> <vb67iyi9c4.fsf@xxxxxxxxxxxxxxx> <980522095232.ZM29476@xxxxxxxxxxxxxxxxxxxxxxx> <19980527142048.A20324@xxxxxxxxxxx> <vbogwj26nw.fsf@xxxxxxxxxxxxxxx> <19980527174141.G1747@xxxxxxxxxxxxxxxxx>
On May 27, 5:41pm, Sven Guckes wrote:
} Subject: Re: completion ignoring
}
} I think Vincent.Lefevre meant this:
}
} When using command name expansion (correct term?)
} can the zsh check the permissions on the executable files
} and present those that are actually executable for the user?
That already happens; that's what Bruce Stevens' meant.
When you check an executable into RCS, the ,v file has write permission
removed but not execute permission:
zagzig[23] ci bleep
bleep,v <-- bleep
initial revision: 1.1
done
zagzig[24] ls -l bleep*
-r-xr-xr-x 1 schaefer schaefer 249 May 27 09:27 bleep,v*
That's how RCS keeps track of what permissions to assign when checking
the file out again. But zsh has no way of knowing that the ,v file is
"not really" executable.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author