From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Sven Guckes <guckes@math.fu-berlin.de>, zsh-users@math.gatech.edu
Subject: Re: completion ignoring
Date: Wed, 27 May 1998 09:31:47 -0700 [thread overview]
Message-ID: <980527093147.ZM23941@candle.brasslantern.com> (raw)
In-Reply-To: <19980527174141.G1747@math.fu-berlin.de>
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
next prev parent reply other threads:[~1998-05-27 16:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-22 15:01 Timothy J Luoma
1998-05-22 15:22 ` Matthew Lovell
1998-05-22 15:23 ` Andrew Main
1998-05-22 15:34 ` Timothy J Luoma
1998-05-22 16:00 ` Bruce Stephens
1998-05-22 16:52 ` Bart Schaefer
1998-05-27 12:20 ` Vincent Lefevre
1998-05-27 13:18 ` Bruce Stephens
1998-05-27 15:41 ` Sven Guckes
1998-05-27 16:21 ` Bruce Stephens
1998-05-29 14:14 ` Vincent Lefevre
1998-05-29 15:36 ` Bruce Stephens
1998-05-29 16:59 ` Vincent Lefevre
1998-05-29 18:55 ` Bart Schaefer
1998-05-27 16:31 ` Bart Schaefer [this message]
1998-05-27 22:34 ` Shawn Leas
1998-05-22 15:32 ` Bruce Stephens
[not found] <"hsoX92.0.773.iEPPr"@tequila.systemsz.cs.yale.edu>
1998-05-22 20:07 ` Stefan Monnier
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=980527093147.ZM23941@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=guckes@math.fu-berlin.de \
--cc=zsh-users@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).