Command line expansions of ~ and other special characters

Command line expansions of ~ and other special characters

[Phil Muldoon]

Right now the fhpd command line understands the ~ character as 
/home/user, and will on tab navigate to the correct location. However 
passing ~/core.1234 to the CorefileCommand will fail as Java's File 
apparently does not. This would also be the case with load command. As 
there is a potential for many areas of duplicate code grappling over 
Linux special special character expansion, does it make sense to have 
these expanded before they reach the sub-commands? What about special 
cases like `pwd  `/core.1234? If so, where does this extraction and 
expansion need to occur?

Regards

Phil

Re: Command line expansions of ~ and other special characters

[Mark Wielaard]

Hi Phil,

On Fri, 2007-11-16 at 08:03 +0000, Phil Muldoon wrote:
> Right now the fhpd command line understands the ~ character as 
> /home/user, and will on tab navigate to the correct location. However 
> passing ~/core.1234 to the CorefileCommand will fail as Java's File 
> apparently does not.

File should handle ~. Try for example:

import java.io.*;

public class F
{
  public static void main(String args[]) throws Exception
  {
    System.err.println(new File(args[0]).getCanonicalPath());
  }
}

$ gcj -C F.java
$ gij F ~/.emacsrc
/home/mark/.emacsrc

>  This would also be the case with load command. As 
> there is a potential for many areas of duplicate code grappling over 
> Linux special special character expansion, does it make sense to have 
> these expanded before they reach the sub-commands? What about special 
> cases like `pwd  `/core.1234? If so, where does this extraction and 
> expansion need to occur?

I think that should be in jline. It is probably related to this bug:
http://sourceware.org/bugzilla/show_bug.cgi?id=5330
"fhpd file arguments don't tab complete when they are relative to the
current working directory"

Cheers,

Mark