all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Cc: Wojciech Meyer <wojciech.meyer@googlemail.com>
Subject: Re: Eshell broken - piping?
Date: Sat, 31 Jul 2010 13:46:33 +0100	[thread overview]
Message-ID: <871vaj7r9y.fsf@gmail.com> (raw)
In-Reply-To: <87pqy4fmw3.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Sat, 31 Jul 2010 03:41:48 +0200")

Óscar Fuentes <ofv@wanadoo.es> writes:

> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.devel as well.
>
> Wojciech Meyer <wojciech.meyer@googlemail.com> writes:
>
>> I've noticed that examples from the wiki + sample command from comments
>> in Eshell source code don't not work anymore, e.g:
>>
>> cat eshell-io.el | wc -l # taken from source code
>>
>> just hangs (probably wc -l is waiting for input)
>
> It works fine here
>
> GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, X toolkit) of 2010-07-30
>
> BTW, from where is eshell-io.el ? I have lisp/eshell/esh-io.el.
>

That was just a random example.

I don't really understand why it does not here, however I don't remember
if that was working. I use bzr HEAD. Problem is verified here with emacs
-Q. I will file a bug then. Is anybody else who got it working?

> [snip]

TIA
Wojciech



  reply	other threads:[~2010-07-31 12:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31  1:09 Eshell broken - piping? Wojciech Meyer
2010-07-31  1:41 ` Óscar Fuentes
2010-07-31 12:46   ` Wojciech Meyer [this message]
2010-07-31 16:03     ` Chad Brown
2010-07-31 17:00       ` Jan Djärv
2010-07-31 18:21         ` Óscar Fuentes
2010-07-31 18:52           ` Wojciech Meyer
2010-07-31 20:00             ` Jan Djärv
2010-07-31 20:00             ` Óscar Fuentes
2010-07-31 19:55           ` Wojciech Meyer

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=871vaj7r9y.fsf@gmail.com \
    --to=wojciech.meyer@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.