Re: return value of find_file()

[Tom Culliton <culliton@xxxxxx>]

Whoops, I must have misread your message and thought you said writable. 
My bad.

On Sat, 7 Jun 2003 16:39:58 +0000 (UTC) Joerg Sommer <joerg@xxxxxxxxxxxx> wrote:
> begin  Tom Culliton <culliton@xxxxxx> wrote:
> > On Sat, 7 Jun 2003 11:40:37 +0000 (UTC) Joerg Sommer <joerg@xxxxxxxxxxxx> wrote:
> > 
> >> But I still have wish: find_file() shouldn't open a buffer for a file,
> >> that isn't readable like /bin or /etc/shadow.
> > 
> > But sometime you just want to look at a file for reference.  What you're
> 
> But, this files aren't readable. Please call find_file("/bin")!
> 
> > suggesting would cripple the editor.  Haven't you ever found yourself
> > opening read-only files like /usr/include/time.h to lookup the fields in
> 
> Yes, I does so, but /bin isn't a file and /etc/shadow is _non_ readable.
> You can't look into it and you can't save a file with the same name. So,
> why open a buffer associated with such a file?
> 
> Joerg.
> 
> --------------------------
> To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
> the word "unsubscribe" in the message body.
> Need help? Email <jed-users-owner@xxxxxxxxxxx>.

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.