Re: SuSv3 violation by jed

[Joerg Sommer <joerg@xxxxxxxxxxxx>]

Hello Adam,

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 :)

But jed behaves the same way if you specify a file at the commandline and
it's common practice to concatenate path by simply append one to the
other. This can produce paths like /home/alpha//etc/passwd which jed do
not resolve the way as the unix spec says.

Yes, it is a question if jed would like to be unix conform, but it's a
terrible feature, if you ask me.

Regards, Jörg.
-- 
Nichts ist so langweilig, wie die Wiederholung seinerselbst.
                                        (Marcel Reich-Ranicki)

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