From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <1469103.jPehuaMYEC@coil> References: <1469103.jPehuaMYEC@coil> Date: Mon, 9 Sep 2013 10:14:43 -0400 Message-ID: From: Lee Fallat To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d0443041a85fa6004e5f402d0 Subject: Re: [9fans] programmable pathname completion in Acme? Topicbox-Message-UUID: 7d774c1a-ead8-11e9-9d60-3106f5b1d025 --f46d0443041a85fa6004e5f402d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Source code says: no. Check out line 725* in text.c, and begin your journey! *Code at line 725 in text.c for 9front acme: case 0x06: case Kins: //interesting, didn't know you could use the insert key to invoke this too. rp =3D textcomplete(t); //the path completion if(rp =3D=3D nil) return; nr =3D runestrlen(rp); break; /* fall through to normal insertion case */ On Mon, Sep 9, 2013 at 9:38 AM, dexen deVries wrot= e: > currently the ^F pathname completion is handled internally by Acme. is > there a > way to pass the argument of ^F to a script instead? > > > my use case: find an existing pathname by supplying /any/ substring of it > and > invoking completion, as opposed to current requirement of providing whole > leading part. i have a script that takes part of pathname in $1 and retur= ns > all (hopefully exactly one) matching pathnames, and i want to plumb the ^= F > from Acme to it. > > > -- > dexen deVries > > [[[=E2=86=93][=E2=86=92]]] > > > --f46d0443041a85fa6004e5f402d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Source code says: no.

Check out line 72= 5* in text.c, and begin your journey!

*Code at lin= e 725 in text.c for 9front acme:

case 0x06:
case Kins: //intere= sting, didn't know you could use the insert key to invoke this too.
rp =3D textcompl= ete(t); //the path completion
if(rp =3D=3D nil)<= /div>
return;
nr =3D runestrlen= (rp);
break; /* fall through to normal insertion case = */


On Mon, Sep 9, 2013 at 9:38 AM, dexen deVries <dexen.devries@gmail.= com> wrote:
currently the ^F pathname completion is handled internally= by Acme. is there a
way to pass the argument of ^F to a script instead?


my use case: find an existing pathname by supplying /any/ substring of it a= nd
invoking completion, as opposed to current requirement of providing whole leading part. i have a script that takes part of pathname in $1 and returns=
all (hopefully exactly one) matching pathnames, and i want to plumb the ^F<= br> from Acme to it.


--
dexen deVries

[[[=E2=86=93][=E2=86=92]]]



--f46d0443041a85fa6004e5f402d0--