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:36:08 +0200 [thread overview]
Message-ID: <CAOCRf5XoSqnaBKg6nbEz5pS_Wrn0P722iKP4cbyJuW=zZB5pWA@mail.gmail.com> (raw)
In-Reply-To: <CAKzHxzFH-y==4e82MFGAN2d7z_L7pKh0yrrT5CYUEMPtXeqMiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
Yep. That way it is hard :)
Although i think you could do it with acid without changing code.
If you are masochistic.
2013/9/9 Lee Fallat <lee.fallat@muraculous.ca>
> On Mon, Sep 9, 2013 at 10:20 AM, Bence Fábián <begnoc@gmail.com> wrote:
>
> nothing prevents textcomplete from forking.
>>
>
> Sorry, I mean it is not possible without having to change some source
> code. :)
>
>
[-- Attachment #2: Type: text/html, Size: 1131 bytes --]
next prev parent reply other threads:[~2013-09-09 14:36 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
2013-09-09 14:26 ` Lee Fallat
2013-09-09 14:36 ` Bence Fábián [this message]
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='CAOCRf5XoSqnaBKg6nbEz5pS_Wrn0P722iKP4cbyJuW=zZB5pWA@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).