public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/5330] fhpd file arguments don't tab complete when they are relative to the current working directory
Date: Thu, 15 Nov 2007 14:29:00 -0000	[thread overview]
Message-ID: <20071115142922.1917.qmail@sourceware.org> (raw)
In-Reply-To: <20071115142112.5330.mark@klomp.org>


------- Additional Comments From mark at klomp dot org  2007-11-15 14:29 -------
OK, the original report was bogus.

The real issue was that neither command autocompletes for relative files
(absolute files starting with / are fine for both run and load).

Changed the subject to mention that it is about relative file paths.

This also doesn't work when prefixed with ./
$ frysk/bindir/fhpd
(fhpd) run ./<tab>

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|fhpd load command argument  |fhpd file arguments don't
                   |doesn't tab complete        |tab complete when they are
                   |                            |relative to the current
                   |                            |working directory


http://sourceware.org/bugzilla/show_bug.cgi?id=5330

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


  reply	other threads:[~2007-11-15 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 14:21 [Bug general/5330] New: fhpd load command argument doesn't tab complete mark at klomp dot org
2007-11-15 14:29 ` mark at klomp dot org [this message]
2007-11-16 14:50 ` [Bug general/5330] jline file arguments don't tab complete when they are relative to the current working directory cagney at redhat dot com

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=20071115142922.1917.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /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).