[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
YAPCQ (Yet Another Programmable Completion Question)
From: |
Richard S. Smith |
Subject: |
YAPCQ (Yet Another Programmable Completion Question) |
Date: |
23 Nov 2000 21:39:57 GMT |
User-agent: |
tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.5-RELEASE (i386)) |
User-agent: |
tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.5-RELEASE (i386)) |
I'm a ClearCase user, and ClearCase provides many opportunities to do
cool stuff using programmable completion. When one is in a ClearCase-
controlled filsystem, the filenames are "sticky" and there are special
commands you can use to access a file's entire version history.
Without getting into excessive detail, here is what I want to do.
Let's say I have a function called "clearcase_complete_file" that does
ClearCase-enhanced filename completion. It's easy enough to bind this
function to specific ClearCase commands, but what if I want to make it
into a generalized function that works in any filename context,
regardless of what command I'm using?
What I want is some way to hook the default readline-based behavior
and have it use my function instead. The other way to win would be to
bind my special function to a keyboard sequence using .inputrc or some
comparable mechanism.
Any ideas? Thanks, as always.
--
--------------------------------------------------------------------------
Richard S. Smith / Email: rss@idiom.com / Web: http://www.idiom.com/~rss
--------------------------------------------------------------------------
- YAPCQ (Yet Another Programmable Completion Question),
Richard S. Smith <=