[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] trunk r115831: * eshell.text (Command Basics): Removed `Co
From: |
Aidan Gauland |
Subject: |
[Emacs-diffs] trunk r115831: * eshell.text (Command Basics): Removed `Command basics' chapter. |
Date: |
Thu, 02 Jan 2014 09:33:11 +0000 |
User-agent: |
Bazaar (2.6b2) |
------------------------------------------------------------
revno: 115831
revision-id: address@hidden
parent: address@hidden
committer: Aidan Gauland <address@hidden>
branch nick: trunk
timestamp: Thu 2014-01-02 22:32:20 +1300
message:
* eshell.text (Command Basics): Removed `Command basics' chapter.
modified:
doc/misc/ChangeLog changelog-20091113204419-o5vbwnq5f7feedwu-6331
doc/misc/eshell.texi
eshell.texi-20091113204419-o5vbwnq5f7feedwu-6299
=== modified file 'doc/misc/ChangeLog'
--- a/doc/misc/ChangeLog 2014-01-02 09:27:46 +0000
+++ b/doc/misc/ChangeLog 2014-01-02 09:32:20 +0000
@@ -1,5 +1,9 @@
2014-01-02 Aidan Gauland <address@hidden>
+ * eshell.text (Command Basics): Removed `Command basics' chapter.
+
+2014-01-02 Aidan Gauland <address@hidden>
+
* eshell.text (What is Eshell?): Add section about what not to use
Eshell for.
=== modified file 'doc/misc/eshell.texi'
--- a/doc/misc/eshell.texi 2014-01-02 09:27:46 +0000
+++ b/doc/misc/eshell.texi 2014-01-02 09:32:20 +0000
@@ -74,7 +74,6 @@
@menu
* Introduction:: A brief introduction to the Emacs Shell.
-* Command basics:: The basics of command usage.
* Commands::
* Expansion::
* Input/Output::
@@ -202,98 +201,6 @@
requests, bug reports and encouragement. Thanks a lot! Without you
there would be no new releases of Eshell.
address@hidden Command basics
address@hidden Basic overview
-
-A command shell is a means of entering verbally-formed commands. This
-is really all that it does, and every feature described in this manual
-is a means to that end. Therefore, it's important to take firm hold on
-exactly what a command is, and how it fits in the overall picture of
-things.
-
address@hidden
-* Commands verbs:: Commands always begin with a verb.
-* Command arguments:: Some verbs require arguments.
address@hidden menu
-
address@hidden Commands verbs
address@hidden Commands verbs
-
-Commands are expressed using @dfn{script}, a special shorthand language
-computers can understand with no trouble. Script is an extremely simple
-language; oddly enough, this is what makes it look so complicated!
-Whereas normal languages use a variety of embellishments, the form of a
-script command is always:
-
address@hidden
address@hidden address@hidden
address@hidden example
-
-The verb expresses what you want your computer to do. There are a fixed
-number of verbs, although this number is usually quite large. On the
-author's computer, it reaches almost 1400 in number. But of course,
-only a handful of these are really necessary.
-
-Sometimes, the verb is all that's written. A verb is always a single
-word, usually related to the task it performs. @command{reboot} is a
-good example. Entering that on GNU/Linux will reboot the
-computer---assuming you have sufficient privileges.
-
-Other verbs require more information. These are usually very capable
-verbs, and must be told specifically what to do. The extra information
-is given in the form of @dfn{arguments}. For example, the
address@hidden verb prints back whatever arguments you type. It
-requires these arguments to know what to echo. A proper use of
address@hidden looks like this:
-
address@hidden
-echo This is an example of using echo!
address@hidden example
-
-This script command causes the computer to echo back: ``This is an
-example of using echo!''
-
-Although command verbs are always simple words, like @command{reboot} or
address@hidden, arguments may have a wide variety of forms. There are
-textual arguments, numerical arguments---even Lisp arguments.
-Distinguishing these different types of arguments requires special
-typing, for the computer to know exactly what you mean.
-
address@hidden Command arguments
address@hidden Command arguments
-
-Eshell recognizes several different kinds of command arguments:
-
address@hidden
address@hidden Strings (also called textual arguments)
address@hidden Numbers (floating point or integer)
address@hidden Lisp lists
address@hidden Lisp symbols
address@hidden Emacs buffers
address@hidden Emacs process handles
address@hidden enumerate
-
-Most users need to worry only about the first two. The third, Lisp lists,
-occur very frequently, but almost always behind the scenes.
-
-Strings are the most common type of argument, and consist of nearly any
-character. Special characters---those used by Eshell
-specifically---must be preceded by a backslash (@samp{\}). When in doubt, it
-is safe to add backslashes anywhere and everywhere.
-
-Here is a more complicated @command{echo} example:
-
address@hidden
-echo A\ Multi-word\ Argument\ With\ A\ \$\ dollar
address@hidden example
-
-Beyond this, things get a bit more complicated. While not beyond the
-reach of someone wishing to learn, it is definitely beyond the scope of
-this manual to present it all in a simplistic manner. Get comfortable
-with Eshell as a basic command invocation tool, and learn more about the
-commands on your system; then come back when it all sits more familiarly
-on your mind. Have fun!
-
@node Commands
@chapter Commands
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] trunk r115831: * eshell.text (Command Basics): Removed `Command basics' chapter.,
Aidan Gauland <=