zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Reinsertion of file prefix for accepted completion?
Date: Fri, 3 Jan 2003 05:56:53 +0000	[thread overview]
Message-ID: <1030103055654.ZM28760@candle.brasslantern.com> (raw)
In-Reply-To: <20030103043321.GC14622@gulag.guild.uwa.edu.au>

On Jan 3, 12:33pm, James Devenish wrote:
} 
} Is there some way (that isn't too outrageous, but perhaps involves the
} calling of a 'fixup' function) to reinsert a compadd -W file prefix when
} the completion is accepted?

Not really, no.

It's a completion system, not an abbreviation system.  The focus is on
producing on the command line an argument in the form that is expected
by the command.  If the command expects a full path, then the completer
should insert the full path.

In other words, instead of

    _path_files -W "( . /not/current/directory )" -g '*(.)'

you should be using something like

    _alternative \
	"local-files:: _path_files -g '*(.)'" \
	"other-files:: _path_files -g '/not/current/directory/*(.)'"

If you have a particular command for which you'd like to be able to use
abbreviated file names as arguments, then write a wrapper function for
that command; e.g. (crudely, for a command named "foo"):

    foo () {
	setopt localoptions noksharrays noshwordsplit
	integer i=$ARGC
	while ((--i))
	do
	    if [[ -f ./$argv[i] ]]; then
		continue
	    elif [[ -f /not/current/directory/$argv[i] ]]; then
		argv[i]=/not/current/directory/$argv[i]
	    fi
	done
	command foo $*
    }

However, you don't both get to use the abbreviations *and* see the full
paths in the command history.

If you *really* wanted to work for it, you could write a new ZLE widget
to replace accept-line, which would walk through the command buffer
every time you press enter to do this same sort of rewriting before
finally calling `zle .accept-line'.  I'm not going to attempt to show
an example of that, because it's fraught with potential problems, but
it could be done.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2003-01-03  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03  4:33 James Devenish
2003-01-03  5:56 ` Bart Schaefer [this message]
2003-01-03  6:35   ` James Devenish

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=1030103055654.ZM28760@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).