From: Mark Wielaard <mark@klomp.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: Command line expansions of ~ and other special characters
Date: Fri, 16 Nov 2007 11:31:00 -0000 [thread overview]
Message-ID: <1195212656.3001.50.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <473D4EE3.3060408@redhat.com>
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
prev parent reply other threads:[~2007-11-16 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 8:03 Phil Muldoon
2007-11-16 11:31 ` Mark Wielaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195212656.3001.50.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=pmuldoon@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).