Skip to content

Is this supposed to be a '>', as the goal is to pipe the "Please install GPG" message to stderr? I don't understand why we would want to pipe stderr into the echo command #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ericwan1 wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Is this supposed to be a '>', as the goal is to pipe the "Please install GPG" message to stderr? I don't understand why we would want to pipe stderr into the echo command #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion commands.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -269,7 +269,7 @@ <h2>The basic grammar of a bash command</h2>
<var>name</var> <strong>()</strong> <var>compound-command</var> [ <var>redirection</var> ]

<samp>exists() { [[ -x $(type -P "$1" 2&gt;/dev/null) ]]; }
exists gpg || echo "Please install GPG." &lt;&amp;2</samp>
exists gpg || echo "Please install GPG." &gt;&amp;2</samp>
</pre>

<p>You begin by specifying a <code>name</code> for your function. This is the name of your new command, you'll be able to run it later on by writing a simple command with that name.</p>
Expand Down