[email protected]
[Top] [All Lists]

Bug#418529: marked as forwarded (jed: evalfile() no longer supporting ~

Subject: Bug#418529: marked as forwarded jed: evalfile() no longer supporting ~ in path name
From: Debian Bug Tracking System
Date: Thu, 12 Apr 2007 15:15:07 +0000
Your message dated Thu, 12 Apr 2007 11:13:17 -0400
with message-id <[email protected]>
has caused the Debian Bug report #418529,
regarding jed: evalfile() no longer supporting ~ in path name
to be marked as having been forwarded to the upstream software
author(s) .

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Subject: Re: Bug#418529: jed: evalfile() no longer supporting ~ in path name
From: "John E. Davis"
Date: Thu, 12 Apr 2007 11:13:17 -0400
Jörg Sommer <[email protected]> wrote:
>@John: Can you explain, why the handling of ~ in path names changed
>between 0.99.16 and now? Is this intended or a bug?

It was intended.  evalfile is slang's lowest level file loading
function, and as such it should not tamper with the name passed to it.
For example, under Unix ~ is a perfectly valid directory name and it
should be possible to load a file in that directory.  For filename
expansion, use the expand_filename function.  While not as convenient,
you can also use evalfile("$HOME/foo.sl"$);

--John

--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>