From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: eshell and jobs
Date: Wed, 29 Jan 2003 16:52:01 +0100 [thread overview]
Message-ID: <841y2w6jj2.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 84wukobex3.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
A code explanation was requested. I basically copied from
eshell/make, so I don't fully grok it. Here comes what I know:
> (defun eshell/ec (&rest args)
If you type "foo" at an eshell prompt, eshell will look for the Lisp
function eshell/foo first thing and run that if it exists.
> "Use `compile' to do background makes."
> (if (eshell-interactive-output-p)
It seems the `then' branch here is what is normally invoked. I have
no idea what the `else' branch does. John, are you listening?
> (let ((compilation-process-setup-function
> (list 'lambda nil
> (list 'setq 'process-environment
> (list 'quote (eshell-copy-environment))))))
This copies the current environment so that `compile' will pick it up.
> (compile (eshell-flatten-and-stringify args))
To see what compile does, type M-x compile RET and enter some shell
command. The eshell-flatten-and-stringify just takes the rest of the
command line args and munges them until they are what `compile'
expects. (I think `compile' expects just a single string, so I guess
that eshell-flatten-and-stringify concats all args, separated with
spaces.)
> (pop-to-buffer compilation-last-buffer))
Make sure to display the *compilation* buffer.
> (throw 'eshell-replace-command
> (let ((l (eshell-stringify-list (eshell-flatten-list args))))
> (eshell-parse-command (car l) (cdr l))))))
Can anyone explain what this might mean?
> (put 'eshell/ec 'eshell-no-numeric-conversions t)
It seems that eshell can recognize numbers and do something with
them. But what?
--
Ambibibentists unite!
next prev parent reply other threads:[~2003-01-29 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 17:27 eshell and jobs Michael Spittel
2003-01-28 17:39 ` David Kastrup
2003-01-28 18:17 ` Michael Spittel
2003-01-29 7:20 ` Kai Großjohann
2003-01-29 13:16 ` eshell and jobs. THANK YOU KAI Michael Spittel
2003-01-29 15:52 ` Kai Großjohann [this message]
2003-01-29 16:20 ` eshell and jobs Romain FRANCOISE
2003-01-29 16:41 ` Michael Spittel
2003-01-29 18:54 ` Kevin Rodgers
2003-01-29 19:11 ` Stefan Monnier <foo@acm.com>
2003-01-30 20:28 ` John Wiegley
2003-01-30 20:29 ` John Wiegley
2003-01-30 21:03 ` Michael Spittel
2003-01-30 21:56 ` John Wiegley
2003-01-30 22:25 ` Michael Spittel
2003-01-31 14:34 ` Kai Großjohann
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=841y2w6jj2.fsf@lucy.is.informatik.uni-duisburg.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).