[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimal emacs shell for coding
From: |
ken |
Subject: |
Re: Optimal emacs shell for coding |
Date: |
Tue, 12 Aug 2008 15:11:24 -0400 |
User-agent: |
Thunderbird 2.0.0.0 (X11/20070326) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/12/2008 03:02 PM Lennart Borgman (gmail) wrote:
| Eli Zaretskii wrote:
|>> Date: Tue, 12 Aug 2008 20:40:35 +0200
|>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
|>> CC: help-gnu-emacs@gnu.org
|>>
|>> Eli Zaretskii wrote:
|>>>> Date: Tue, 12 Aug 2008 14:06:02 +0200
|>>>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
|>>>> CC: help-gnu-emacs@gnu.org
|>>>>
|>>>> If you look carefully at the output you can see that what is not
|>>>> handled is the parameters to "ls". If you try "ls -1" it will work.
|>>> What "parameters to ls"? "ls" was invoked without any parameters.
|>> If you from a shell do
|>>
|>> ls | grep
|>>
|>> then normally ls implicitly gets the -1 parameter
|>
|> No, it doesn't. Please try and see for yourself (I just did).
|
|
| We are miscommunicating. Exactly what are you saying?
|
| I am saying that if I from a shell outside of Emacs do
|
| ls
|
| than I get several files listed on each row while the output from
|
| ls | grep some-file
|
| implies that ls got the implicit argument -1 when used in the pipe.
Lennart,
You're correct: ls followed by a pipe puts each file on a line by
itself... easily demonstrated by "ls|less", "ls|more", "ls|wc -l",
"ls|grep -E $", and others.
Weird, but true.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFIoeBa8CeNiFrQkecRAu3UAKCONy17ZkSqEpx9Y+mswYDBTmJhSwCfdJgT
ePFlKRA1jfkvRy1/xgSoO8c=
=vgsE
-----END PGP SIGNATURE-----
- Re: Optimal emacs shell for coding, (continued)
- Re: Optimal emacs shell for coding, Eli Zaretskii, 2008/08/12
- Re: Optimal emacs shell for coding, Lennart Borgman (gmail), 2008/08/12
- Re: Optimal emacs shell for coding, Eli Zaretskii, 2008/08/12
- Re: Optimal emacs shell for coding, Lennart Borgman (gmail), 2008/08/12
- Re: Optimal emacs shell for coding, Eli Zaretskii, 2008/08/12
- Message not available
- Re: Optimal emacs shell for coding, Chris F.A. Johnson, 2008/08/12
- Message not available
- Re: Optimal emacs shell for coding, Tim X, 2008/08/13
- Re: Optimal emacs shell for coding, Thierry Volpiatto, 2008/08/13
- eshell pipelines (Was: Re: Optimal emacs shell for coding), David Hansen, 2008/08/13
- Re: eshell pipelines, Thierry Volpiatto, 2008/08/13
- Re: Optimal emacs shell for coding,
ken <=
- Re: Optimal emacs shell for coding, Lennart Borgman (gmail), 2008/08/12
- Re: Optimal emacs shell for coding, Eli Zaretskii, 2008/08/12
- Re: Optimal emacs shell for coding, David Hansen, 2008/08/12
- Message not available
- Re: Optimal emacs shell for coding, Rupert Swarbrick, 2008/08/12
Re: Optimal emacs shell for coding, Eli Zaretskii, 2008/08/11
Re: Optimal emacs shell for coding, Tim X, 2008/08/12
Re: Optimal emacs shell for coding, Mike Treseler, 2008/08/11