From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: eshell completers?
Date: Sun, 01 Dec 2002 14:40:19 +0100 [thread overview]
Message-ID: <84ptsl3lj0.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: of86etz4.fsf@ID-23066.news.dfncis.de
clemens fischer <ino-qc@spotteswoode.de.eu.org> writes:
> i need an eshell completer for the type of external commands that
> issue all kinds of helpful information themselves that just needs to
> be parsed out. prime candidates: "./configure --help", "openssl
> -help" or "[g]make" (if simply collecting all words that start off a
> line in the Makefile, ending in a colon). i got the completers ready
> for the bash, but don't know how to get it done in eshell.
`make' works out of the box on my system.
For the others, hm... I'm afraid you've got to do it yourself.
pcomplete is another library that you might want to look at -- eshell
uses it.
--
~/.signature is: umop ap!sdn (Frank Nobis)
prev parent reply other threads:[~2002-12-01 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-30 19:30 eshell completers? clemens fischer
2002-12-01 13:40 ` Kai Großjohann [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84ptsl3lj0.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@uni-duisburg.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).