Re: SuSv3 violation by jed

[Michael Stillwell <mjs@xxxxxxxxx>]

On 10/4/05, Adam Byrtek <alpha@xxxxxxxxxxxx> wrote:
> On Fri, Sep 30, 2005 at 08:57:13PM +0000, Joerg Sommer wrote:
> > I looked into the SuSv3 (the Unix standard) and found in section "4.11
> > Pathname Resolution", that a path with more than one backslash should be
> > treated a the path with one backslash. Ergo the above path must expand to
> > /usr/share/jed/compile/jed-common and not /jed-common. Otherwise it is
> > not Unix conform.
>
> I think the reason it was implemented like this is that when you get
> the filename prompt (like when you try to find a file), it is already
> filled with current directory, like:
>
> Find file: /home/alpha/
>
> Now you can open absolute path by just typing the it without the need
> to clean the prompt:
>
> Find file: /home/alpha//etc/passwd
>
> will open /etc/passwd. However I don't claim this is compliant in any
> way :)

You can also use ~ in the same way, at least inside jed.  I quite like
this feature, though perhaps it should only apply to filenames
specified within jed, not filenames on the command-line.


--M.

--
http://beebo.org
+44 78 2118 9049


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