9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] programmable pathname completion in Acme?
Date: Mon,  9 Sep 2013 16:20:19 +0200	[thread overview]
Message-ID: <CAOCRf5V0Myz1Rev9RQ4FyD7pzFa-4N1zDwjh0vU3s=Jms61Wuw@mail.gmail.com> (raw)
In-Reply-To: <CAKzHxzGsG0W-H=VdCQ6rpHm1sgf+rOkmc8FqKwOQEoyUo-J_gg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

nothing prevents textcomplete from forking.


2013/9/9 Lee Fallat <lee.fallat@muraculous.ca>

> 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 = textcomplete(t); //the path completion
>  if(rp == nil)
> return;
> nr = 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
>> 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
>> returns
>> all (hopefully exactly one) matching pathnames, and i want to plumb the ^F
>> from Acme to it.
>>
>>
>> --
>> dexen deVries
>>
>> [[[↓][→]]]
>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 2371 bytes --]

  reply	other threads:[~2013-09-09 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 13:38 dexen deVries
2013-09-09 14:14 ` Lee Fallat
2013-09-09 14:20   ` Bence Fábián [this message]
2013-09-09 14:26     ` Lee Fallat
2013-09-09 14:36       ` Bence Fábián
2013-09-09 15:59         ` Matthew Veety

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='CAOCRf5V0Myz1Rev9RQ4FyD7pzFa-4N1zDwjh0vU3s=Jms61Wuw@mail.gmail.com' \
    --to=begnoc@gmail.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).