From: "Jesús Guerrero" <i92guboj@terra.es>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: FIXED 3D
Date: Fri, 09 Oct 2009 04:56:11 +0200 [thread overview]
Message-ID: <94f285f6225706805dc272f7b21709d4@localhost> (raw)
In-Reply-To: <4ACE9E4D.9080006@gentoo.org>
On Thu, 08 Oct 2009 22:22:05 -0400, Jonathan Callen <abcd@gentoo.org>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Neil Bothwick wrote:
>> Note you can also nest commands when using $(), which you can't do with
>> backticks.
>
> You can nest commands with ``, it's just less intuitive; each of the
> following are equivalent:
Thank for calling my attention on that.
Yes, I know how it works. I rather meant that you can't nest the backticks
in a vanilla fashion, like with $(). Escaping the ticks you can do whatever
you want, it's just a matter of making sure the right thing reaches the
correct depth in a nested chain of shells, since each time that this kind
of substitution it happens in a new subshell.
$ pgrep bash | wc -l
6
$ echo $(pgrep bash | wc -l)
7
$ echo $(echo $(pgrep bash | wc -l))
8
I'll admit I didn't express it in the clearest way. However, this doesn't
solve the fact of the accents being dead keys in a lost (most?) languages
with a Latin alphabet, but English, nor the problem about the clarity
(though that's less an issue when you are working in command line, most
times anyway). I have no idea if the accent is a standard character in
every keyboard layout, so I am not sure that that is a valid argument on
any sane keyboard. I just checked and that accent is even part of the 7 bit
ascii table (dec 96), which is as minimal as you can get nowadays unless we
are speaking about some exotic embedded stuff or ancient device of the
caverns, and in that case, probably the same could apply to $, and even ()
:P
--
Jesús Guerrero
next prev parent reply other threads:[~2009-10-09 2:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 16:49 [gentoo-user] Broken 3D James
2009-10-07 19:26 ` [gentoo-user] " walt
2009-10-07 19:30 ` [gentoo-user] " James Ausmus
2009-10-07 21:22 ` Volker Armin Hemmann
2009-10-08 3:38 ` Jesús Guerrero
2009-10-08 15:28 ` [gentoo-user] Re: FIXED 3D James
2009-10-08 15:35 ` Jesús Guerrero
2009-10-08 15:53 ` James
2009-10-08 15:54 ` Nikos Chantziaras
2009-10-08 18:33 ` Neil Bothwick
2009-10-08 19:14 ` Alan McKinnon
2009-10-08 19:19 ` James Ausmus
2009-10-08 19:27 ` Nikos Chantziaras
2009-10-08 20:02 ` Alan McKinnon
2009-10-08 20:09 ` Nikos Chantziaras
2009-10-09 16:12 ` Alex Schuster
2009-10-08 19:34 ` Nikos Chantziaras
2009-10-08 21:21 ` Neil Bothwick
2009-10-08 22:43 ` Jesús Guerrero
2009-10-09 2:22 ` Jonathan Callen
2009-10-09 2:56 ` Jesús Guerrero [this message]
2009-10-09 8:13 ` Neil Bothwick
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=94f285f6225706805dc272f7b21709d4@localhost \
--to=i92guboj@terra.es \
--cc=gentoo-user@lists.gentoo.org \
/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