ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texexec completion script for zsh
Date: Tue, 18 Dec 2007 13:16:14 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.0.9999.0712181309470.19196@nqv-yncgbc> (raw)
In-Reply-To: <200712181818.21885.matija.suklje@rutka.net>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1443 bytes --]

On Tue, 18 Dec 2007, Matija Šuklje wrote:

> Dne ponedeljek 17. decembra 2007 je Aditya Mahajan napisal(a):
>> I just put together a simple completion script for texexec in zsh.
>
> Sweet, thanks :]
>
>> This is my first attempt to write a zsh completion script. Any feedback is
>> welcome.
>
> Well, I'm a Zsh newbie,

So am I. Been using it for about two weeks now.

> so I'm in no position to claim anything to be wrong.
> But what bothers me with your script (as it is right now) is that when apart
> from 'texexec' there is also a 'texexec_completer' command present.

Yes. All the completer functions are available as commands. Try _<tab> and 
you will see all the in-built ones.

If you want, you can rename texexec_completer to _texexec. That way, you 
will not get prompted for it on normal commands. I do not know if _ is 
reservered for distribution level completers or not, so did not name it 
_texexec.


> Otherwise, really great work! It inspired me to perhaps even take on some Zsh
> scripting of my own at some point.

I have been fairly impressed zsh tab completion. For example, suppose 
firefox has hung, and you want to kill it. Earlier, I did something like

ps aux | grep firefox

look at the pid and kill that process. With zsh, I can do

kill -9 firefox<tab> and it finds the pid for me. Sweet.

At some point, I hope to get a more sophisticated completer for texexec.

Aditya

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2007-12-18 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  1:15 Aditya Mahajan
2007-12-18 17:18 ` Matija Šuklje
2007-12-18 18:16   ` Aditya Mahajan [this message]
2007-12-18 18:29     ` Matija Šuklje

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=alpine.DEB.0.9999.0712181309470.19196@nqv-yncgbc \
    --to=adityam@umich.edu \
    --cc=ntg-context@ntg.nl \
    /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).