| Re: [AD] Re: file_select_ex patch |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Re: file_select_ex patch
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Fri, 16 Sep 2005 16:18:15 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=GVZbz57S2gTXcA9w/vSM7cLcG6+6bRAhSurT/wefaAuv4CXXIzr799UVINjoQSJBLe9dBD8MjSJG8xg2aGlBAv/P6BdMQy1aL5aq0CwNmQVyn0j4u5n0gp4fagc1FCj4l49I/g/cXmS0kIb9RXWIYMsGI/5Q+9Zk6h+E0SFeELU=
On Friday 16 September 2005 04:01 pm, Elias Pschernig wrote:
> No, I have /home/web there. My home dir is not outside readable, so
> apache accessible files have their own home under the web user. Oh,
> and /var/www is another example of a directory which would get
> inaccessible with -r with your change. /var is read-only, still /var/www
> is where I drop apache files into.
You can still type in /var/www or /home/web into the path bar. Or, you can
create symlinks in your home folder to those areas.
> Well, from the implementation view, I'd agree, -r should not show
> read-only directories. But from any possible use scenario, I think it
> must show all directories which may contain writeable files in them -
You can say the same about hidden directories, though. Should it show hidden
directories because they may contain unhidden files? And it is far more
likely for a directory to be marked hidden with unhidden files than to be
read-only with writeable files.
> the "-r" is for files after all, and not directories.
Directories can have a read-only attribute. It affects all files created in
them, and has an affect that you can't delete/move it, or its contents. At
most, you can only modify files in it *if* (and that's a big if) there's
files marked writeable to you.