From mboxrd@z Thu Jan 1 00:00:00 1970 From: dexen deVries To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Date: Mon, 3 Sep 2012 10:22:39 +0200 Message-ID: <1836341.rNiiQUvYyi@coil> User-Agent: KMail/4.9 (Linux/3.5.0-l45; KDE/4.9.0; x86_64; ; ) In-Reply-To: References: <20120828150521.GA10731@intma.in> <0d2163b339e8b9211593ad0c636e070a@brasstown.quanstro.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Subject: Re: [9fans] rc vs sh Topicbox-Message-UUID: b59fd0c2-ead7-11e9-9d60-3106f5b1d025 On Monday 03 of September 2012 09:31:12 Rudolf Sykora wrote: > I too believe that unless the mechanism of autocomplete is well-enoug= h > resolved, rc won't work for many people. I understand the reasons why= > readline is not in the shell, but on the other hand I often get angry= > when I can't autocomplete. >=20 > Sometimes I just do not remember the exact name of a command, > sometimes I can't use variables in a path on the command line since I= > do not exactly remember what should come next (like sam > $directory^/something; ctrl-f doesn't help), etc. Also the problem of= > not being able to repeat last few commands so simply as can be done > elsewhere is disappointing (if there is a lot of error output from th= e > previous command, saying that one must look back, find the command, > change it, ...). Rsc's " and "" scripts help much, but still are not > so straightforward as an up-arrow. (Again, I understand that for the > latter-like behaviour one needs cursor addressing.) my use case: in acme, upon hitting ^F, before breaking up completion su= bject =20 into directory/file part and passing it to complete(), do filter the=20= completion subject through Rc to expand both variable names and wildcar= ds. somewhere around /usr/local/plan9/src/cmd/acme/text.c:/^textcomplete --=20 dexen deVries [[[=E2=86=93][=E2=86=92]]] I'm sorry that this was such a long lett=C2=ADer, but I didn't have tim= e to write=20 you a short one. -- Bla=C2=ADise Pasc=C2=ADal