unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: Loops and scripting in eshell
Date: Tue, 21 Oct 2003 01:44:15 +0200	[thread overview]
Message-ID: <87he234gq8.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: 867k2zk3be.fsf@slowfox.dyndns.org

Kai Grossjohann <kai.grossjohann@gmx.net> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> for f in ${ls -1} { echo $f; }
>
> Hm.  The fact that the -1 is needed hints at some potential problem.
> In the shell, ls behaves differently.  (The -1 is not needed there.)
> So maybe some other programs break when used in a similar way?
>
> (I guess the difference has to do with isatty(3).  No idea how
> difficult would it be for eshell to do this right.)
>
> What do people think?
[...]

I don't know about the isatty issue. I don't know much about the
underlying lower operating system level. But I'd like to note, that it
seems to work in *some* directories, but not in others:

[lisp] $ for f in ${ls} {echo $f}
2cyr.txt                draw.el           iso646-de.el         single-frame.el

*much more output snipped*

[lisp] $ mkdir test
[lisp] $ cd test
[test] $ touch alpha beta gamma delta
[test] $ for f in ${ls} {echo $f}
Wrong type argument: listp, #("alpha  beta  delta  gamma" 0 25 (escaped t))
[test] $ for f in ${ls -l} {echo $f}
total 0
usage: echo [-n] [object]

    -n                   terminate with a newline
    -h, --help           output this help screen


Does anybody know offhand where in the eshell code `for' is implemented?

    Oliver
-- 
30 Vendémiaire an 212 de la Révolution
Liberté, Egalité, Fraternité!

  reply	other threads:[~2003-10-20 23:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 19:36 Inject some eshell features into shell? Kai Grossjohann
2003-10-15 21:07 ` Stefan Monnier
2003-10-17 19:31 ` Kevin Rodgers
2003-10-17 22:44   ` Kevin Rodgers
2003-10-19 10:56     ` Kai Grossjohann
     [not found]     ` <mailman.1974.1066561040.21628.help-gnu-emacs@gnu.org>
2003-10-20 16:55       ` Kevin Rodgers
2003-10-19 12:31 ` Loops and scripting in eshell (was: Inject some eshell features into shell?) Oliver Scholz
2003-10-19 15:06   ` Loops and scripting in eshell Kai Grossjohann
     [not found]   ` <mailman.1980.1066576051.21628.help-gnu-emacs@gnu.org>
2003-10-19 20:04     ` Oliver Scholz
2003-10-19 20:15       ` Oliver Scholz
2003-10-19 20:45         ` David Kastrup
2003-10-20 21:27           ` Kai Grossjohann
2003-10-20 23:44             ` Oliver Scholz [this message]
2003-10-21  9:05               ` David Kastrup
2003-10-21 16:05                 ` Kai Grossjohann
2003-10-20 19:48   ` Reiner Steib
2003-10-21  8:55     ` Oliver Scholz
2003-10-22 10:55 ` Inject some eshell features into shell? Matthias Meulien

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=87he234gq8.fsf@ID-87814.user.dfncis.de \
    --to=alkibiades@gmx.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).