Commit | Line | Data |
---|---|---|
572a0c97 | 1 | \input texinfo @c -*-texinfo-*- |
177c0ea7 | 2 | @c "@(#)$Name: $:$Id: eshell.texi,v 1.17 2002/12/10 13:16:31 pj Exp $" |
572a0c97 JW |
3 | @c %**start of header |
4 | @setfilename ../info/eshell | |
5 | @settitle Eshell: The Emacs Shell | |
18f952d5 | 6 | @synindex vr fn |
572a0c97 JW |
7 | @c %**end of header |
8 | ||
18f952d5 KB |
9 | @copying |
10 | This manual is for Eshell, the Emacs shell. | |
b409f09b | 11 | |
18f952d5 KB |
12 | Copyright @copyright{} 1999, 2000, 2001, 2002 Free Software Foundation, Inc. |
13 | ||
14 | @quotation | |
b409f09b GM |
15 | Permission is granted to copy, distribute and/or modify this document |
16 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
17 | any later version published by the Free Software Foundation; with no | |
18 | Invariant Sections, with the Front-Cover texts being ``A GNU | |
19 | Manual'', and with the Back-Cover Texts as in (a) below. A copy of the | |
20 | license is included in the section entitled ``GNU Free Documentation | |
21 | License'' in the Emacs manual. | |
22 | ||
23 | (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify | |
24 | this GNU Manual, like GNU software. Copies published by the Free | |
25 | Software Foundation raise funds for GNU development.'' | |
26 | ||
27 | This document is part of a collection distributed under the GNU Free | |
28 | Documentation License. If you want to distribute this document | |
29 | separately from the collection, you can do so by adding a copy of the | |
30 | license to the document, as described in section 6 of the license. | |
18f952d5 KB |
31 | @end quotation |
32 | @end copying | |
33 | ||
34 | @dircategory Emacs | |
35 | @direntry | |
36 | * Eshell: (eshell). A command shell implemented in Emacs Lisp. | |
37 | @end direntry | |
38 | ||
39 | @setchapternewpage on | |
572a0c97 | 40 | |
572a0c97 JW |
41 | @titlepage |
42 | @sp 4 | |
43 | @c The title is printed in a large font. | |
44 | @center @titlefont{User's Guide} | |
45 | @sp | |
46 | @center @titlefont{to} | |
47 | @sp | |
48 | @center @titlefont{Eshell: The Emacs Shell} | |
49 | @ignore | |
50 | @sp 2 | |
dace60cf | 51 | @center release 2.4 |
572a0c97 JW |
52 | @c -release- |
53 | @end ignore | |
54 | @sp 3 | |
55 | @center John Wiegley | |
56 | @c -date- | |
57 | ||
572a0c97 JW |
58 | @page |
59 | @vskip 0pt plus 1filll | |
18f952d5 | 60 | @insertcopying |
572a0c97 JW |
61 | @end titlepage |
62 | ||
997c7f71 EZ |
63 | @contents |
64 | ||
572a0c97 JW |
65 | @c ================================================================ |
66 | @c The real text starts here | |
67 | @c ================================================================ | |
68 | ||
18f952d5 | 69 | @ifnottex |
7d97fbf4 | 70 | @node Top, What is Eshell?, (dir), (dir) |
572a0c97 JW |
71 | @top Eshell |
72 | ||
73 | This manual documents Eshell, a shell-like command interpretor | |
dace60cf JW |
74 | implemented in Emacs Lisp. It invokes no external processes except for |
75 | those requested by the user. It is intended to be a functional | |
572a0c97 | 76 | replacement for command shells such as @command{bash}, @command{zsh}, |
dace60cf JW |
77 | @command{rc}, or @command{4dos}; since Emacs itself is capable of |
78 | handling the sort of tasks accomplished by those tools. | |
79 | @c This manual is updated to release 2.4 of Eshell. | |
18f952d5 | 80 | @end ifnottex |
572a0c97 JW |
81 | |
82 | @menu | |
219227ea JW |
83 | * What is Eshell?:: A brief introduction to the Emacs Shell. |
84 | * Installation:: For users of Emacs 20 and XEmacs. | |
177c0ea7 JB |
85 | * Command basics:: The basics of command usage. |
86 | * Commands:: | |
87 | * Arguments:: | |
88 | * Input/Output:: | |
89 | * Process control:: | |
90 | * Extension modules:: | |
91 | * Extras and Goodies:: | |
219227ea | 92 | * Bugs and ideas:: Known problems, and future ideas. |
177c0ea7 JB |
93 | * Concept Index:: |
94 | * Function and Variable Index:: | |
95 | * Key Index:: | |
572a0c97 JW |
96 | @end menu |
97 | ||
7d97fbf4 | 98 | @node What is Eshell? |
572a0c97 | 99 | @chapter What is Eshell? |
997c7f71 EZ |
100 | @cindex what is Eshell? |
101 | @cindex Eshell, what it is | |
572a0c97 | 102 | |
dace60cf | 103 | Eshell is a @dfn{command shell} written in Emacs Lisp. Everything it |
219227ea | 104 | does, it uses Emacs' facilities to do. This means that Eshell is as |
dace60cf JW |
105 | portable as Emacs itself. It also means that cooperation with Lisp code |
106 | is natural and seamless. | |
572a0c97 | 107 | |
dace60cf | 108 | What is a command shell? To properly understand the role of a shell, |
572a0c97 JW |
109 | it's necessary to visualize what a computer does for you. Basically, a |
110 | computer is a tool; in order to use that tool, you must tell it what to | |
304724c2 | 111 | do---or give it ``commands.'' These commands take many forms, such as |
572a0c97 JW |
112 | clicking with a mouse on certain parts of the screen. But that is only |
113 | one form of command input. | |
114 | ||
115 | By far the most versatile way to express what you want the computer to | |
304724c2 RS |
116 | do is by using an abbreviated language called @dfn{script}. In |
117 | script, instead of telling the computer, ``list my files, please'', | |
118 | one writes a standard abbreviated command word---@samp{ls}. Typing | |
119 | @samp{ls} in a command shell is a script way of telling the computer | |
120 | to list your files.@footnote{This is comparable to viewing the | |
121 | contents of a folder using a graphical display.} | |
dace60cf JW |
122 | |
123 | The real flexibility of this approach is apparent only when you realize | |
124 | that there are many, many different ways to list files. Perhaps you | |
125 | want them sorted by name, sorted by date, in reverse order, or grouped | |
126 | by type. Most graphical browsers have simple ways to express this. But | |
127 | what about showing only a few files, or only files that meet a certain | |
128 | criteria? In very complex and specific situations, the request becomes | |
129 | too difficult to express using a mouse or pointing device. It is just | |
130 | these kinds of requests that are easily solved using a command shell. | |
572a0c97 JW |
131 | |
132 | For example, what if you want to list every Word file on your hard | |
133 | drive, larger than 100 kilobytes in size, and which hasn't been looked | |
134 | at in over six months? That is a good candidate list for deletion, when | |
135 | you go to clean up your hard drive. But have you ever tried asking your | |
136 | computer for such a list? There is no way to do it! At least, not | |
137 | without using a command shell. | |
138 | ||
dace60cf JW |
139 | The role of a command shell is to give you more control over what your |
140 | computer does for you. Not everyone needs this amount of control, and | |
141 | it does come at a cost: Learning the necessary script commands to | |
572a0c97 JW |
142 | express what you want done. A complicated query, such as the example |
143 | above, takes time to learn. But if you find yourself using your | |
144 | computer frequently enough, it is more than worthwhile in the long run. | |
dace60cf | 145 | Any tool you use often deserves the time spent learning to master it. |
572a0c97 JW |
146 | @footnote{For the understandably curious, here is what that command |
147 | looks like: But don't let it fool you; once you know what's going on, | |
148 | it's easier than it looks: @code{ls -lt **/*.doc(Lk+50aM+5)}.} | |
149 | ||
150 | As of Emacs 21, Eshell is part of the standard Emacs distribution. | |
151 | ||
152 | @menu | |
dace60cf | 153 | * Contributors to Eshell:: People who have helped out! |
572a0c97 JW |
154 | @end menu |
155 | ||
7d97fbf4 | 156 | @node Contributors to Eshell |
572a0c97 | 157 | @section Contributors to Eshell |
997c7f71 EZ |
158 | @cindex contributors |
159 | @cindex authors | |
572a0c97 JW |
160 | |
161 | Contributions to Eshell are welcome. I have limited time to work on | |
162 | this project, but I will gladly add any code you contribute to me to | |
163 | this package. | |
164 | ||
165 | The following persons have made contributions to Eshell. | |
166 | ||
167 | @itemize @bullet | |
168 | @item | |
169 | Eli Zaretskii made it possible for Eshell to run without requiring | |
170 | asynchronous subprocess support. This is important for MS-DOS, which | |
171 | does not have such support.@refill | |
172 | ||
173 | @item | |
174 | Miles Bader contributed many fixes during the port to Emacs 21.@refill | |
175 | ||
176 | @item | |
177 | Stefan Monnier fixed the things which bothered him, which of course made | |
178 | things better for all.@refill | |
179 | ||
180 | @item | |
181 | Gerd Moellmann also helped to contribute bug fixes during the initial | |
182 | integration with Emacs 21.@refill | |
183 | ||
184 | @item | |
185 | Alex Schroeder contributed code for interactively querying the user | |
186 | before overwriting files.@refill | |
187 | ||
188 | @item | |
189 | Sudish Joseph helped with some XEmacs compatibility issues.@refill | |
572a0c97 JW |
190 | @end itemize |
191 | ||
192 | Apart from these, a lot of people have sent suggestions, ideas, | |
193 | requests, bug reports and encouragement. Thanks a lot! Without you | |
194 | there would be no new releases of Eshell. | |
195 | ||
7d97fbf4 | 196 | @node Installation |
997c7f71 EZ |
197 | @chapter Installation |
198 | @cindex installation | |
572a0c97 | 199 | |
dace60cf | 200 | As mentioned above, Eshell comes preinstalled as of Emacs 21. If you're |
572a0c97 JW |
201 | using Emacs 20.4 or later, or XEmacs 21, you can download the most |
202 | recent version of Eshell from | |
4711065a | 203 | @url{http://www.gci-net.com/users/j/johnw/Emacs/packages/eshell.tar.gz}. |
572a0c97 | 204 | |
dace60cf | 205 | However, if you are using Emacs 21, you may skip this section. |
572a0c97 | 206 | |
997c7f71 | 207 | @section Short Form |
572a0c97 JW |
208 | |
209 | Here's exactly what to do, with no explanation why: | |
210 | ||
211 | @enumerate | |
997c7f71 EZ |
212 | @item |
213 | @samp{M-x load-file RET eshell-auto.el RET}. | |
214 | ||
215 | @item | |
216 | @samp{ESC : (add-to-list 'load-path "<path where Eshell resides>") RET}. | |
217 | ||
218 | @item | |
219 | @samp{ESC : (add-to-list 'load-path "<path where Pcomplete resides>") RET}. | |
220 | ||
221 | @item | |
222 | @samp{M-x eshell RET}. | |
572a0c97 JW |
223 | |
224 | You should see a version banner displayed. | |
225 | ||
997c7f71 EZ |
226 | @item |
227 | @samp{ls RET}. | |
572a0c97 JW |
228 | |
229 | Confirm that you see a file listing. | |
230 | ||
997c7f71 EZ |
231 | @item |
232 | @samp{eshell-test RET}. | |
572a0c97 | 233 | |
997c7f71 | 234 | Confirm that everything runs correctly. Use @kbd{M-x eshell-report-bug} if |
572a0c97 JW |
235 | not. |
236 | ||
997c7f71 EZ |
237 | @item |
238 | @samp{cd $@{dirname (locate-library "eshell-auto")@} RET}. | |
239 | ||
240 | @item | |
241 | @samp{find-file Makefile RET}. | |
242 | ||
243 | @item | |
244 | Edit the Makefile to reflect your site. | |
245 | ||
246 | @item | |
247 | @samp{M-x eshell RET}. | |
248 | ||
249 | @item | |
250 | @samp{make install RET}. | |
251 | ||
252 | @item | |
253 | @samp{find-file $user-init-file RET}. | |
254 | ||
255 | @item | |
256 | Add the following lines to your @file{.emacs} file: | |
572a0c97 JW |
257 | |
258 | @example | |
259 | (add-to-list 'load-path "<directory where you install Eshell>") | |
260 | (load "eshell-auto") | |
261 | @end example | |
262 | ||
997c7f71 EZ |
263 | @item |
264 | @samp{M-x eshell RET}. | |
265 | ||
266 | @item | |
267 | @samp{customize-option #'eshell-modules-list RET}. | |
268 | ||
269 | @item | |
270 | Select the extension modules you prefer. | |
271 | ||
272 | @item | |
273 | Restart Emacs! | |
274 | ||
275 | @item | |
276 | @samp{M-x info RET m Eshell RET}. | |
572a0c97 JW |
277 | |
278 | Read the manual and enjoy! | |
279 | @end enumerate | |
280 | ||
997c7f71 | 281 | @section Long Form |
572a0c97 JW |
282 | |
283 | @enumerate | |
284 | @item | |
285 | Before building and installing Eshell, it is important to test that it | |
997c7f71 | 286 | will work properly on your system. To do this, first load the file |
572a0c97 JW |
287 | @file{eshell-auto}, which will define certain autoloads required to run |
288 | Eshell. This can be done using the command @kbd{M-x load-file}, and | |
289 | then selecting the file @file{eshell-auto.el}. | |
290 | ||
291 | @item | |
292 | In order for Emacs to find Eshell's files, the Eshell directory must be | |
293 | added to the @code{load-path} variable. This can be done within Emacs by | |
294 | typing: | |
295 | ||
296 | @example | |
297 | ESC : (add-to-list 'load-path "<path where Eshell resides>") RET | |
298 | ESC : (add-to-list 'load-path "<path where Pcomplete resides>") RET | |
299 | @end example | |
300 | ||
301 | @item | |
302 | Start Eshell from the distributed sources, using default settings, by | |
303 | typing @kbd{M-x eshell}. | |
304 | ||
305 | @item | |
306 | Verify that Eshell is functional by typing @command{ls} followed by | |
997c7f71 | 307 | @key{RET}. You should have already seen a version banner announcing the |
572a0c97 JW |
308 | version number of this release, followed by a prompt. |
309 | ||
310 | @item | |
997c7f71 | 311 | Run the test suite by typing @command{eshell-test} followed by @key{RET} |
572a0c97 JW |
312 | in the Eshell buffer. It is important that Emacs be left alone while |
313 | the tests are running, since extraneous command input may cause some of | |
314 | the tests to fail (they were never intended to run in the background). | |
315 | If all of the tests pass, Eshell should work just fine on your system. | |
316 | If any of the tests fail, please send e-mail to the Eshell maintainer | |
317 | using the command @kbd{M-x eshell-report-bug}. | |
318 | ||
319 | @item | |
320 | Edit the file @file{Makefile} in the directory containing the Eshell | |
219227ea | 321 | sources to reflect the location of certain Emacs directories at your |
572a0c97 JW |
322 | site. The only things you really have to change are the definitions of |
323 | @code{lispdir} and @code{infodir}. The elisp files will be copied to | |
324 | @code{lispdir}, and the info file to @code{infodir}. | |
325 | ||
326 | @item | |
997c7f71 EZ |
327 | Type @kbd{make install} in the directory containing the Eshell sources. |
328 | This will byte-compile all of the @file{*.el} files and copy both the | |
572a0c97 JW |
329 | source and compiled versions to the directories specified in the |
330 | previous step. It will also copy the info file, and add a corresponding | |
997c7f71 EZ |
331 | entry to your @file{dir} file----if the program @code{install-info} can |
332 | be found on your system. | |
572a0c97 JW |
333 | |
334 | If you only want to create the compiled elisp files, but don't want to | |
997c7f71 | 335 | install them, you can type just @kbd{make} instead. |
572a0c97 JW |
336 | |
337 | @item | |
338 | Add the directory into which Eshell was installed to your | |
339 | @code{load-path} variable. This can be done by adding the following | |
340 | line to your @file{.emacs} file: | |
341 | ||
342 | @example | |
343 | (add-to-list 'load-path "/usr/local/share/emacs/site-lisp/eshell") | |
344 | @end example | |
345 | ||
346 | The actual directory on your system may differ. | |
347 | ||
348 | @item | |
349 | To install Eshell privately, edit your @file{.emacs} file; to install | |
350 | Eshell site-wide, edit the file @file{site-start.el} in your | |
351 | @file{site-lisp} directory (usually | |
352 | @file{/usr/local/share/emacs/site-lisp} or something similar). In | |
353 | either case enter the following line into the appropriate file: | |
354 | ||
355 | @example | |
356 | (load "eshell-auto") | |
357 | @end example | |
358 | ||
359 | @item | |
360 | Restart Emacs. After restarting, customize the variable | |
361 | @code{eshell-modules-list}. This variable selects which Eshell | |
362 | extension modules you want to use. You will find documentation on each | |
363 | of those modules in the Info manual. | |
572a0c97 JW |
364 | @end enumerate |
365 | ||
997c7f71 EZ |
366 | @cindex documentation, printed version |
367 | @cindex printed version of documentation | |
572a0c97 JW |
368 | If you have @TeX{} installed at your site, you can make a typeset manual |
369 | from @file{eshell.texi}. | |
370 | ||
371 | @enumerate | |
372 | @item | |
997c7f71 EZ |
373 | Run @TeX{} by typing @kbd{texi2dvi eshell.texi}. (With Emacs 21.1 or |
374 | later, typing @kbd{make eshell.dvi} in the @file{man/} subdirectory of | |
375 | the Emacs source distribution will do that.) | |
376 | ||
572a0c97 JW |
377 | @item |
378 | Convert the resulting device independent file @file{eshell.dvi} to a | |
379 | form which your printer can output and print it. If you have a | |
997c7f71 | 380 | postscript printer, there is a program, @code{dvi2ps}, which does that; there |
572a0c97 | 381 | is also a program which comes together with @TeX{}, @code{dvips}, which |
997c7f71 EZ |
382 | you can use. For other printers, use a suitable DVI driver, |
383 | e.g., @code{dvilj4} for LaserJet-compatible printers. | |
572a0c97 JW |
384 | @end enumerate |
385 | ||
7d97fbf4 | 386 | @node Command basics |
219227ea | 387 | @chapter Basic overview |
572a0c97 | 388 | |
219227ea JW |
389 | A command shell is a means of entering verbally-formed commands. This |
390 | is really all that it does, and every feature described in this manual | |
391 | is a means to that end. Therefore, it's important to take firm hold on | |
392 | exactly what a command is, and how it fits in the overall picture of | |
393 | things. | |
572a0c97 | 394 | |
dace60cf JW |
395 | @menu |
396 | * Commands verbs:: Commands always begin with a verb. | |
397 | * Command arguments:: Some verbs require arguments. | |
398 | @end menu | |
399 | ||
7d97fbf4 | 400 | @node Commands verbs |
dace60cf | 401 | @section Commands verbs |
572a0c97 | 402 | |
dace60cf | 403 | Commands are expressed using @dfn{script}, a special shorthand language |
219227ea JW |
404 | computers can understand with no trouble. Script is an extremely simple |
405 | language; oddly enough, this is what makes it look so complicated! | |
406 | Whereas normal languages use a variety of embellishments, the form of a | |
407 | script command is always: | |
572a0c97 | 408 | |
dace60cf | 409 | @example |
304724c2 | 410 | @var{verb} [@var{arguments}] |
dace60cf | 411 | @end example |
572a0c97 | 412 | |
dace60cf JW |
413 | The verb expresses what you want your computer to do. There are a fixed |
414 | number of verbs, although this number is usually quite large. On the | |
415 | author's computer, it reaches almost 1400 in number. But of course, | |
416 | only a handful of these are really necessary. | |
572a0c97 | 417 | |
dace60cf | 418 | Sometimes, the verb is all that's written. A verb is always a single |
219227ea | 419 | word, usually related to the task it performs. @command{reboot} is a |
304724c2 RS |
420 | good example. Entering that on GNU/Linux will reboot the |
421 | computer---assuming you have sufficient privileges. | |
219227ea JW |
422 | |
423 | Other verbs require more information. These are usually very capable | |
424 | verbs, and must be told specifically what to do. The extra information | |
425 | is given in the form of @dfn{arguments}. For example, the | |
426 | @command{echo} verb prints back whatever arguments you type. It | |
427 | requires these arguments to know what to echo. A proper use of | |
dace60cf | 428 | @command{echo} looks like this: |
572a0c97 | 429 | |
dace60cf | 430 | @example |
304724c2 | 431 | echo This is an example of using echo! |
dace60cf | 432 | @end example |
572a0c97 | 433 | |
219227ea | 434 | This script command causes the computer to echo back: ``This is an |
304724c2 | 435 | example of using echo!'' |
572a0c97 | 436 | |
219227ea JW |
437 | Although command verbs are always simple words, like @command{reboot} or |
438 | @command{echo}, arguments may have a wide variety of forms. There are | |
439 | textual arguments, numerical arguments---even Lisp arguments. | |
440 | Distinguishing these different types of arguments requires special | |
441 | typing, for the computer to know exactly what you mean. | |
572a0c97 | 442 | |
7d97fbf4 | 443 | @node Command arguments |
dace60cf | 444 | @section Command arguments |
572a0c97 | 445 | |
219227ea JW |
446 | Eshell recognizes several different kinds of command arguments: |
447 | ||
448 | @enumerate | |
449 | @item Strings (also called textual arguments) | |
450 | @item Numbers (floating point or integer) | |
451 | @item Lisp lists | |
452 | @item Lisp symbols | |
453 | @item Emacs buffers | |
454 | @item Emacs process handles | |
455 | @end enumerate | |
456 | ||
1fc0f361 | 457 | Most users need to worry only about the first two. The third, Lisp lists, |
219227ea JW |
458 | occur very frequently, but almost always behind the scenes. |
459 | ||
460 | Strings are the most common type of argument, and consist of nearly any | |
461 | character. Special characters---those used by Eshell | |
1fc0f361 EZ |
462 | specifically---must be preceded by a backslash (@samp{\}). When in doubt, it |
463 | is safe to add backslashes anywhere and everywhere. | |
219227ea JW |
464 | |
465 | Here is a more complicated @command{echo} example: | |
466 | ||
467 | @example | |
304724c2 | 468 | echo A\ Multi-word\ Argument\ With\ A\ \$\ dollar |
219227ea JW |
469 | @end example |
470 | ||
471 | Beyond this, things get a bit more complicated. While not beyond the | |
472 | reach of someone wishing to learn, it is definitely beyond the scope of | |
473 | this manual to present it all in a simplistic manner. Get comfortable | |
474 | with Eshell as a basic command invocation tool, and learn more about the | |
475 | commands on your system; then come back when it all sits more familiarly | |
476 | on your mind. Have fun! | |
477 | ||
7d97fbf4 | 478 | @node Commands |
219227ea JW |
479 | @chapter Commands |
480 | ||
481 | @menu | |
177c0ea7 JB |
482 | * Invocation:: |
483 | * Completion:: | |
484 | * Aliases:: | |
485 | * History:: | |
486 | * Scripts:: | |
7d97fbf4 | 487 | * Built-ins:: |
219227ea JW |
488 | @end menu |
489 | ||
248ac71c JW |
490 | Essentially, a command shell is all about invoking commands---and |
491 | everything that entails. So understanding how Eshell invokes commands | |
492 | is the key to comprehending how it all works. | |
493 | ||
7d97fbf4 | 494 | @node Invocation |
219227ea JW |
495 | @section Invocation |
496 | ||
248ac71c JW |
497 | Unlike regular system shells, Eshell never invokes kernel functions |
498 | directly, such as @code{exec(3)}. Instead, it uses the Lisp functions | |
499 | available in the Emacs Lisp library. It does this by transforming the | |
500 | command you specify into a callable Lisp form.@footnote{To see the Lisp | |
501 | form that will be invoked, type: @samp{eshell-parse-command "echo | |
502 | hello"}} | |
503 | ||
504 | This transformation, from the string of text typed at the command | |
505 | prompt, to the ultimate invocation of either a Lisp function or external | |
506 | command, follows these steps: | |
507 | ||
508 | @enumerate | |
509 | @item Parse the command string into separate arguments. | |
177c0ea7 | 510 | @item |
248ac71c JW |
511 | @end enumerate |
512 | ||
7d97fbf4 | 513 | @node Completion |
219227ea JW |
514 | @section Completion |
515 | ||
7d97fbf4 | 516 | @node Aliases |
219227ea JW |
517 | @section Aliases |
518 | ||
7d97fbf4 | 519 | @node History |
219227ea JW |
520 | @section History |
521 | ||
7d97fbf4 KG |
522 | Eshell knows a few built-in variables: |
523 | ||
524 | @table @code | |
525 | ||
526 | @item $+ | |
527 | @vindex $+ | |
528 | This variable always contains the current working directory. | |
529 | ||
530 | @item $- | |
531 | @vindex $- | |
532 | This variable always contains the previous working directory (the | |
533 | current working directory from before the last @code{cd} command). | |
534 | ||
535 | @end table | |
536 | ||
537 | @node Scripts | |
219227ea JW |
538 | @section Scripts |
539 | ||
540 | ||
7d97fbf4 KG |
541 | @node Built-ins |
542 | @section Built-in commands | |
543 | ||
544 | Here is a list of built-in commands that Eshell knows about: | |
545 | ||
546 | @table @code | |
547 | ||
548 | @item cd | |
549 | @findex cd | |
550 | This command changes the current working directory. Usually, it is | |
551 | invoked as @samp{cd foo} where @file{foo} is the new working | |
552 | directory. But @code{cd} knows about a few special arguments: | |
553 | ||
554 | When it receives no argument at all, it changes to the home directory. | |
555 | ||
556 | Giving the command @samp{cd -} changes back to the previous working | |
557 | directory (this is the same as @samp{cd $-}). | |
558 | ||
1ecfdc69 KG |
559 | The command @samp{cd =} shows the directory stack. Each line is |
560 | numbered. | |
7d97fbf4 KG |
561 | |
562 | With @samp{cd =foo}, Eshell searches the directory stack for a | |
563 | directory matching the regular expression @samp{foo} and changes to | |
564 | that directory. | |
565 | ||
1ecfdc69 KG |
566 | With @samp{cd -42}, you can access the directory stack by number. |
567 | ||
7d97fbf4 KG |
568 | @end table |
569 | ||
570 | ||
571 | @node Arguments | |
219227ea JW |
572 | @chapter Arguments |
573 | ||
574 | @menu | |
177c0ea7 JB |
575 | * The Parser:: |
576 | * Variables:: | |
577 | * Substitution:: | |
578 | * Globbing:: | |
579 | * Predicates:: | |
219227ea JW |
580 | @end menu |
581 | ||
7d97fbf4 | 582 | @node The Parser |
219227ea JW |
583 | @section The Parser |
584 | ||
7d97fbf4 | 585 | @node Variables |
219227ea JW |
586 | @section Variables |
587 | ||
7d97fbf4 | 588 | @node Substitution |
219227ea JW |
589 | @section Substitution |
590 | ||
7d97fbf4 | 591 | @node Globbing |
219227ea JW |
592 | @section Globbing |
593 | ||
7d97fbf4 | 594 | @node Predicates |
219227ea JW |
595 | @section Predicates |
596 | ||
597 | ||
7d97fbf4 | 598 | @node Input/Output |
219227ea JW |
599 | @chapter Input/Output |
600 | ||
7d97fbf4 | 601 | @node Process control |
219227ea JW |
602 | @chapter Process control |
603 | ||
604 | ||
7d97fbf4 | 605 | @node Extension modules |
219227ea JW |
606 | @chapter Extension modules |
607 | ||
608 | @menu | |
177c0ea7 JB |
609 | * Writing a module:: |
610 | * Module testing:: | |
611 | * Directory handling:: | |
612 | * Key rebinding:: | |
613 | * Smart scrolling:: | |
614 | * Terminal emulation:: | |
615 | * Built-in UNIX commands:: | |
219227ea JW |
616 | @end menu |
617 | ||
7d97fbf4 | 618 | @node Writing a module |
219227ea JW |
619 | @section Writing a module |
620 | ||
7d97fbf4 | 621 | @node Module testing |
219227ea JW |
622 | @section Module testing |
623 | ||
7d97fbf4 | 624 | @node Directory handling |
219227ea JW |
625 | @section Directory handling |
626 | ||
7d97fbf4 | 627 | @node Key rebinding |
219227ea JW |
628 | @section Key rebinding |
629 | ||
7d97fbf4 | 630 | @node Smart scrolling |
219227ea JW |
631 | @section Smart scrolling |
632 | ||
7d97fbf4 | 633 | @node Terminal emulation |
219227ea JW |
634 | @section Terminal emulation |
635 | ||
7d97fbf4 | 636 | @node Built-in UNIX commands |
219227ea JW |
637 | @section Built-in UNIX commands |
638 | ||
639 | ||
7d97fbf4 | 640 | @node Extras and Goodies |
219227ea JW |
641 | @chapter Extras and Goodies |
642 | ||
7d97fbf4 | 643 | @node Bugs and ideas |
572a0c97 | 644 | @chapter Bugs and ideas |
997c7f71 EZ |
645 | @cindex reporting bugs and ideas |
646 | @cindex bugs, how to report them | |
647 | @cindex author, how to reach | |
648 | @cindex email to the author | |
572a0c97 | 649 | @cindex FAQ |
997c7f71 | 650 | @cindex problems, list of common |
572a0c97 JW |
651 | |
652 | If you find a bug or misfeature, don't hesitate to let me know! Send | |
997c7f71 | 653 | email to @email{johnw@@gnu.org}. Feature requests should also be sent |
572a0c97 JW |
654 | there. I prefer discussing one thing at a time. If you find several |
655 | unrelated bugs, please report them separately. | |
656 | ||
657 | If you have ideas for improvements, or if you have written some | |
658 | extensions to this package, I would like to hear from you. I hope you | |
659 | find this package useful! | |
660 | ||
661 | @menu | |
177c0ea7 | 662 | * Known problems:: |
572a0c97 JW |
663 | @end menu |
664 | ||
7d97fbf4 | 665 | @node Known problems |
572a0c97 | 666 | @section Known problems |
997c7f71 EZ |
667 | @cindex known bugs |
668 | @cindex bugs, known | |
572a0c97 | 669 | |
219227ea JW |
670 | Below is complete list of known problems with Eshell version 2.4.1, |
671 | which is the version included with Emacs 21.1. | |
572a0c97 JW |
672 | |
673 | @table @asis | |
dace60cf JW |
674 | @item Differentiate between aliases and functions |
675 | ||
676 | Allow for a bash-compatible syntax, such as: | |
677 | ||
678 | @example | |
679 | alias arg=blah | |
dbdc47a3 | 680 | function arg () @{ blah $* @} |
dace60cf JW |
681 | @end example |
682 | ||
683 | @item @samp{for i in 1 2 3 @{ grep -q a b && *echo has it @} | wc -l} outputs result after prompt | |
572a0c97 JW |
684 | |
685 | In fact, piping to a process from a looping construct doesn't work in | |
686 | general. If I change the call to @code{eshell-copy-handles} in | |
687 | @code{eshell-rewrite-for-command} to use @code{eshell-protect}, it seems | |
688 | to work, but the output occurs after the prompt is displayed. The whole | |
689 | structured command thing is too complicated at present. | |
690 | ||
691 | @item Error with @command{bc} in @code{eshell-test} | |
692 | ||
693 | On some XEmacs system, the subprocess interaction test fails | |
997c7f71 | 694 | inexplicably, although @command{bc} works fine at the command prompt. |
572a0c97 | 695 | |
572a0c97 JW |
696 | @item Eshell does not delete @file{*Help*} buffers in XEmacs 21.1.8+ |
697 | ||
698 | In XEmacs 21.1.8, the @file{*Help*} buffer has been renamed such that | |
699 | multiple instances of the @file{*Help*} buffer can exist. | |
700 | ||
701 | @item Pcomplete sometimes gets stuck | |
702 | ||
997c7f71 EZ |
703 | You press @key{TAB}, but no completions appear, even though the |
704 | directory has matching files. This behavior is rare. | |
572a0c97 JW |
705 | |
706 | @item @samp{grep python $<rpm -qa>} doesn't work, but using @samp{*grep} does | |
707 | ||
708 | This happens because the @code{grep} Lisp function returns immediately, | |
709 | and then the asynchronous @command{grep} process expects to examine the | |
710 | temporary file, which has since been deleted. | |
711 | ||
712 | @item Problem with C-r repeating text | |
713 | ||
714 | If the text @emph{before point} reads "./run", and you type @kbd{C-r r u | |
715 | n}, it will repeat the line for every character typed. | |
716 | ||
717 | @item Backspace doesn't scroll back after continuing (in smart mode) | |
718 | ||
719 | Hitting space during a process invocation, such as @command{make}, will | |
720 | cause it to track the bottom of the output; but backspace no longer | |
721 | scrolls back. | |
722 | ||
723 | @item It's not possible to fully @code{unload-feature} Eshell | |
724 | ||
725 | @item Menu support was removed, but never put back | |
726 | ||
727 | @item Using C-p and C-n with rebind gets into a locked state | |
728 | ||
28665d46 | 729 | This happened a few times in Emacs 21, but has been unreproducible |
572a0c97 JW |
730 | since. |
731 | ||
732 | @item If an interactive process is currently running, @kbd{M-!} doesn't work | |
733 | ||
734 | @item Use a timer instead of @code{sleep-for} when killing child processes | |
735 | ||
736 | @item Piping to a Lisp function is not supported | |
737 | ||
738 | Make it so that the Lisp command on the right of the pipe is repeatedly | |
739 | called with the input strings as arguments. This will require changing | |
dace60cf | 740 | @code{eshell-do-pipeline} to handle non-process targets. |
572a0c97 JW |
741 | |
742 | @item Input redirection is not supported | |
743 | ||
dace60cf JW |
744 | See the above entry. |
745 | ||
219227ea | 746 | @item Problem running @command{less} without arguments on Windows |
dace60cf JW |
747 | |
748 | The result in the Eshell buffer is: | |
749 | ||
750 | @example | |
751 | Spawning child process: invalid argument | |
752 | @end example | |
753 | ||
754 | Also a new @command{less} buffer was created with nothing in it@dots{} | |
755 | (presumably this holds the output of @command{less}). | |
756 | ||
757 | If @command{less.exe} is invoked from the Eshell command line, the | |
758 | expected output is written to the buffer. | |
759 | ||
bbd9b8db EZ |
760 | Note that this happens on NT-Emacs 20.6.1 on Windows 2000. The term.el |
761 | package and the supplied shell both use the @command{cmdproxy} program | |
762 | for running shells. | |
dace60cf JW |
763 | |
764 | @item Implement @samp{-r}, @samp{-n} and @samp{-s} switches for @command{cp} | |
765 | ||
766 | @item Make @kbd{M-5 M-x eshell} switch to ``*eshell<5>*'', creating if need be | |
767 | ||
bbd9b8db | 768 | @item @samp{mv @var{dir} @var{file}.tar} does not remove directories |
dace60cf JW |
769 | |
770 | This is because the tar option --remove-files doesn't do so. Should it | |
771 | be Eshell's job? | |
772 | ||
773 | @item Bind @code{standard-output} and @code{standard-error} | |
774 | ||
775 | This would be so that if a Lisp function calls @code{print}, everything | |
776 | will happen as it should (albeit slowly). | |
777 | ||
778 | @item When an extension module fails to load, @samp{cd /} gives a Lisp error | |
779 | ||
780 | @item If a globbing pattern returns one match, should it be a list? | |
781 | ||
782 | @item Make sure syntax table is correct in Eshell mode | |
783 | ||
784 | So that @kbd{M-DEL} acts in a predictable manner, etc. | |
785 | ||
786 | @item Allow all Eshell buffers to share the same history and list-dir | |
787 | ||
788 | @item There is a problem with script commands that output to @file{/dev/null} | |
789 | ||
790 | If a script file, somewhere in the middle, uses @samp{> /dev/null}, | |
791 | output from all subsequent commands is swallowed. | |
792 | ||
793 | @item Split up parsing of text after @samp{$} in @file{esh-var.el} | |
794 | ||
795 | Make it similar to the way that @file{esh-arg.el} is structured. | |
796 | Then add parsing of @samp{$[?\n]}. | |
797 | ||
798 | @item After pressing @kbd{M-RET}, redisplay before running the next command | |
799 | ||
800 | @item Argument predicates and modifiers should work anywhere in a path | |
801 | ||
802 | @example | |
803 | /usr/local/src/editors/vim $ vi **/CVS(/)/Root(.) | |
804 | Invalid regexp: "Unmatched ( or \\(" | |
805 | @end example | |
806 | ||
807 | With @command{zsh}, the glob above expands to all files named | |
808 | @file{Root} in directories named @file{CVS}. | |
809 | ||
dbdc47a3 | 810 | @item Typing @samp{echo $@{locate locate@}/bin<TAB>} results in a Lisp error |
dace60cf JW |
811 | |
812 | Perhaps it should interpolate all permutations, and make that the | |
813 | globbing result, since otherwise hitting return here will result in | |
814 | ``(list of filenames)/bin'', which is never valuable. Thus, one could | |
dbdc47a3 | 815 | @command{cat} only C backup files by using @samp{ls $@{identity *.c@}~}. |
dace60cf JW |
816 | In that case, having an alias command name @command{glob} for |
817 | @command{identity} would be useful. | |
818 | ||
dace60cf JW |
819 | @item Once symbolic mode is supported for @command{umask}, implement @command{chmod} in Lisp |
820 | ||
821 | @item Create @code{eshell-expand-file-name} | |
822 | ||
823 | This would use a data table to transform things such as @samp{~+}, | |
824 | @samp{...}, etc. | |
825 | ||
826 | @item Abstract @file{em-smart.el} into @file{smart-scroll.el} | |
827 | ||
828 | It only really needs: to be hooked onto the output filter and the | |
829 | pre-command hook, and to have the input-end and input-start markers. | |
304724c2 | 830 | And to know whether the last output group was ``successful.'' |
dace60cf JW |
831 | |
832 | @item Allow for fully persisting the state of Eshell | |
833 | ||
834 | This would include: variables, history, buffer, input, dir stack, etc. | |
835 | ||
836 | @item Implement D as an argument predicate | |
837 | ||
838 | It means that files beginning with a dot should be included in the | |
839 | glob match. | |
840 | ||
841 | @item A comma in a predicate list should mean OR | |
842 | ||
843 | At the moment, this is not supported. | |
844 | ||
845 | @item Error if a glob doesn't expand due to a predicate | |
846 | ||
847 | An error should be generated only if @code{eshell-error-if-no-glob} is | |
848 | non-nil. | |
849 | ||
850 | @item @samp{(+ RET SPC TAB} does not cause @code{indent-according-to-mode} to occur | |
851 | ||
852 | @item Create @code{eshell-auto-accumulate-list} | |
853 | ||
854 | This is a list of commands for which, if the user presses @kbd{RET}, the | |
855 | text is staged as the next Eshell command, rather than being sent to the | |
856 | current interactive process. | |
857 | ||
858 | @item Display file and line number if an error occurs in a script | |
859 | ||
860 | @item @command{wait} doesn't work with process ids at the moment | |
861 | ||
862 | @item Enable the direct-to-process input code in @file{em-term.el} | |
863 | ||
864 | @item Problem with repeating @samp{echo $@{find /tmp@}} | |
865 | ||
866 | With smart display active, if @kbd{RET} is held down, after a while it | |
867 | can't keep up anymore and starts outputting blank lines. It only | |
868 | happens if an asynchronous process is involved@dots{} | |
869 | ||
870 | I think the problem is that @code{eshell-send-input} is resetting the | |
871 | input target location, so that if the asynchronous process is not done | |
872 | by the time the next @kbd{RET} is received, the input processor thinks | |
873 | that the input is meant for the process; which, when smart display is | |
874 | enabled, will be the text of the last command line! That is a bug in | |
875 | itself. | |
876 | ||
877 | In holding down @kbd{RET} while an asynchronous process is running, | |
878 | there will be a point in between termination of the process, and the | |
879 | running of @code{eshell-post-command-hook}, which would cause | |
880 | @code{eshell-send-input} to call @code{eshell-copy-old-input}, and then | |
881 | process that text as a command to be run after the process. Perhaps | |
882 | there should be a way of killing pending input between the death of the | |
883 | process, and the @code{post-command-hook}. | |
884 | ||
885 | @item Allow for a more aggressive smart display mode | |
886 | ||
887 | Perhaps toggled by a command, that makes each output block a smart | |
888 | display block. | |
889 | ||
890 | @item Create more meta variables | |
891 | ||
892 | @table @samp | |
893 | @item $! | |
894 | The reason for the failure of the last disk command, or the text of the | |
895 | last Lisp error. | |
896 | ||
897 | @item $= | |
898 | A special associate array, which can take references of the form | |
899 | @samp{$=[REGEXP]}. It indexes into the directory ring. | |
900 | @end table | |
901 | ||
902 | @item Eshell scripts can't execute in the background | |
903 | ||
bbd9b8db | 904 | @item Support zsh's ``Parameter Expansion'' syntax, i.e. @samp{$@{@var{name}:-@var{val}@}} |
dace60cf JW |
905 | |
906 | @item Write an @command{info} alias that can take arguments | |
907 | ||
908 | So that the user can enter @samp{info chmod}, for example. | |
909 | ||
910 | @item Create a mode @code{eshell-browse} | |
911 | ||
912 | It would treat the Eshell buffer as a outline. Collapsing the outline | |
913 | hides all of the output text. Collapsing again would show only the | |
914 | first command run in each directory | |
915 | ||
916 | @item Allow other revisions of a file to be referenced using @samp{file@{rev@}} | |
917 | ||
918 | This would be expanded by @code{eshell-expand-file-name} (see above). | |
919 | ||
920 | @item Print ``You have new mail'' when the ``Mail'' icon is turned on | |
921 | ||
922 | @item Implement @kbd{M-|} for Eshell | |
923 | ||
924 | @item Implement input redirection | |
925 | ||
926 | If it's a Lisp function, input redirection implies @command{xargs} (in a | |
927 | way@dots{}). If input redirection is added, also update the | |
928 | @code{file-name-quote-list}, and the delimiter list. | |
929 | ||
bbd9b8db | 930 | @item Allow @samp{#<@var{word} @var{arg}>} as a generic syntax |
dace60cf JW |
931 | |
932 | With the handling of @emph{word} specified by an | |
933 | @code{eshell-special-alist}. | |
934 | ||
219227ea | 935 | @item In @code{eshell-veal-using-options}, allow a @code{:complete} tag |
dace60cf JW |
936 | |
937 | It would be used to provide completion rules for that command. Then the | |
938 | macro will automagically define the completion function. | |
939 | ||
940 | @item For @code{eshell-command-on-region}, apply redirections to the result | |
941 | ||
942 | So that @samp{+ > 'blah} would cause the result of the @code{+} (using | |
943 | input from the current region) to be inserting into the symbol | |
944 | @code{blah}. | |
945 | ||
946 | If an external command is being invoked, the input is sent as standard | |
947 | input, as if a @samp{cat <region> |} had been invoked. | |
948 | ||
949 | If a Lisp command, or an alias, is invoked, then if the line has no | |
950 | newline characters, it is divided by whitespace and passed as arguments | |
951 | to the Lisp function. Otherwise, it is divided at the newline | |
952 | characters. Thus, invoking @code{+} on a series of numbers will add | |
953 | them; @code{min} would display the smallest figure, etc. | |
954 | ||
955 | @item Write @code{eshell-script-mode} as a minor mode | |
956 | ||
957 | It would provide syntax, abbrev, highlighting and indenting support like | |
958 | @code{emacs-lisp-mode} and @code{shell-mode}. | |
959 | ||
960 | @item In the history mechanism, finish the @command{bash}-style support | |
961 | ||
962 | This means @samp{!n}, @samp{!#}, @samp{!:%}, and @samp{!:1-} as separate | |
963 | from @samp{!:1*}. | |
964 | ||
965 | @item Support the -n command line option for @command{history} | |
966 | ||
967 | @item Implement @command{fc} in Lisp | |
968 | ||
969 | @item Specifying a frame as a redirection target should imply the currently active window's buffer | |
970 | ||
bbd9b8db | 971 | @item Implement @samp{>@var{func-or-func-list}} |
dace60cf JW |
972 | |
973 | This would allow for an ``output translators'', that take a function to | |
974 | modify output with, and a target. Devise a syntax that works well with | |
28665d46 | 975 | pipes, and can accommodate multiple functions (i.e., @samp{>'(upcase |
dace60cf JW |
976 | regexp-quote)} or @samp{>'upcase}). |
977 | ||
978 | @item Allow Eshell to read/write to/from standard input and output | |
979 | ||
980 | This would be optional, rather than always using the Eshell buffer. | |
981 | This would allow it to be run from the command line (perhaps). | |
982 | ||
983 | @item Write a @command{help} command | |
984 | ||
bbd9b8db EZ |
985 | It would call subcommands with @option{--help}, or @option{-h} or |
986 | @option{/?}, as appropriate. | |
dace60cf JW |
987 | |
988 | @item Implement @command{stty} in Lisp | |
989 | ||
bbd9b8db | 990 | @item Support @command{rc}'s matching operator, e.g. @samp{~ (@var{list}) @var{regexp}} |
dace60cf JW |
991 | |
992 | @item Implement @command{bg} and @command{fg} as editors of @code{eshell-process-list} | |
993 | ||
994 | Using @command{bg} on a process that is already in the background does | |
995 | nothing. Specifying redirection targets replaces (or adds) to the list | |
996 | current being used. | |
997 | ||
998 | @item Have @command{jobs} print only the processes for the current shell | |
999 | ||
1000 | @item How can Eshell learn if a background process has requested input? | |
1001 | ||
1002 | @item Support @samp{2>&1} and @samp{>&} and @samp{2>} and @samp{|&} | |
1003 | ||
1004 | The syntax table for parsing these should be customizable, such that the | |
1005 | user could change it to use rc syntax: @samp{>[2=1]}. | |
1006 | ||
1007 | @item Allow @samp{$_[-1]}, which would indicate the last element of the array | |
1008 | ||
1009 | @item Make @samp{$x[*]} equal to listing out the full contents of @samp{x} | |
1010 | ||
1011 | Return them as a list, so that @samp{$_[*]} is all the arguments of the | |
1012 | last command. | |
1013 | ||
1014 | @item Copy ANSI code handling from @file{term.el} into @file{em-term.el} | |
1015 | ||
1016 | Make it possible for the user to send char-by-char to the underlying | |
1017 | process. Ultimately, I should be able to move away from using term.el | |
1018 | altogether, since everything but the ANSI code handling is already part | |
bbd9b8db EZ |
1019 | of Eshell. Then, things would work correctly on MS-Windows as well |
1020 | (which doesn't have @file{/bin/sh}, although @file{term.el} tries to use | |
1021 | it). | |
dace60cf JW |
1022 | |
1023 | @item Make the shell spawning commands be visual | |
1024 | ||
1025 | That is, make (@command{su}, @command{bash}, @command{telnet}, | |
1026 | @command{rlogin}, @command{rsh}, etc.) be part of | |
1027 | @code{eshell-visual-commands}. The only exception is if the shell is | |
1028 | being used to invoke a single command. Then, the behavior should be | |
1029 | based on what that command is. | |
1030 | ||
bbd9b8db | 1031 | @item Create a smart viewing command named @command{open} |
dace60cf JW |
1032 | |
1033 | This would search for some way to open its argument (similar to opening | |
1034 | a file in the Windows Explorer). | |
1035 | ||
1036 | @item Alias @command{read} to be the same as @command{open}, only read-only | |
1037 | ||
1038 | @item Write a @command{tail} command which uses @code{view-file} | |
1039 | ||
1040 | It would move point to the end of the buffer, and then turns on | |
1041 | auto-revert mode in that buffer at frequent intervals---and a | |
1042 | @command{head} alias which assums an upper limit of | |
1043 | @code{eshell-maximum-line-length} characters per line. | |
1044 | ||
1045 | @item Make @command{dgrep} load @code{dired}, mark everything, then invoke @code{dired-do-search} | |
1046 | ||
219227ea | 1047 | @item Write mesh.c |
dace60cf JW |
1048 | |
1049 | This would run Emacs with the appropriate arguments to invoke Eshell | |
1050 | only. That way, it could be listed as a login shell. | |
1051 | ||
1052 | @item Use an intangible @code{PS2} string for multi-line input prompts | |
1053 | ||
1054 | @item Auto-detect when a command is visual, by checking @code{TERMCAP} usage | |
1055 | ||
1056 | @item The first keypress after @kbd{M-x watson} triggers `eshell-send-input' | |
1057 | ||
1058 | @item Make @kbd{/} electric | |
1059 | ||
1060 | So that it automatically expands and corrects pathnames. Or make | |
1061 | pathname completion for Pcomplete auto-expand @samp{/u/i/std<TAB>} to | |
1062 | @samp{/usr/include/std<TAB>}. | |
1063 | ||
1064 | @item Write the @command{pushd} stack to disk along with @code{last-dir-ring} | |
1065 | ||
1066 | @item Add options to @code{eshell/cat} which would allow it to sort and uniq | |
1067 | ||
1068 | @item Implement @command{wc} in Lisp | |
1069 | ||
1070 | Add support for counting sentences, paragraphs, pages, etc. | |
1071 | ||
1072 | @item Once piping is added, implement @command{sort} and @command{uniq} in Lisp | |
1073 | ||
1074 | @item Implement @command{touch} in Lisp | |
1075 | ||
1076 | @item Implement @command{comm} in Lisp | |
1077 | ||
1078 | @item Implement an @command{epatch} command in Lisp | |
1079 | ||
1080 | This would call @code{ediff-patch-file}, or @code{ediff-patch-buffer}, | |
1081 | depending on its argument. | |
1082 | ||
1083 | @item Have an option such that @samp{ls -l} generates a dired buffer | |
1084 | ||
1085 | @item Write a version of @command{xargs} based on command rewriting | |
1086 | ||
1087 | That is, @samp{find X | xargs Y} would be indicated using @samp{Y | |
1088 | $@{find X@}}. Maybe @code{eshell-do-pipelines} could be changed to | |
1089 | perform this on-thy-fly rewriting. | |
1090 | ||
1091 | @item Write an alias for @command{less} that brings up a @code{view-mode} buffer | |
1092 | ||
bbd9b8db | 1093 | Such that the user can press @key{SPC} and @key{DEL}, and then @key{q} |
177c0ea7 | 1094 | to return to Eshell. It would be equivalent to: |
dace60cf JW |
1095 | @samp{X > #<buffer Y>; view-buffer #<buffer Y>}. |
1096 | ||
1097 | @item Make @code{eshell-mode} as much a full citizen as @code{shell-mode} | |
1098 | ||
1099 | Everywhere in Emacs where @code{shell-mode} is specially noticed, add | |
1100 | @code{eshell-mode} there. | |
1101 | ||
1102 | @item Permit the umask to be selectively set on a @command{cp} target | |
1103 | ||
1104 | @item Problem using @kbd{M-x eshell} after using @code{eshell-command} | |
1105 | ||
1106 | If the first thing that I do after entering Emacs is to run | |
1107 | @code{eshell-command} and invoke @command{ls}, and then use @kbd{M-x | |
1108 | eshell}, it doesn't display anything. | |
1109 | ||
1110 | @item @kbd{M-RET} during a long command (using smart display) doesn't work | |
1111 | ||
1112 | Since it keeps the cursor up where the command was invoked. | |
1113 | ||
572a0c97 JW |
1114 | @end table |
1115 | ||
7d97fbf4 | 1116 | @node Concept Index |
572a0c97 JW |
1117 | @unnumbered Concept Index |
1118 | ||
1119 | @printindex cp | |
1120 | ||
7d97fbf4 | 1121 | @node Function and Variable Index |
997c7f71 EZ |
1122 | @unnumbered Function and Variable Index |
1123 | ||
1124 | @printindex fn | |
1125 | ||
7d97fbf4 | 1126 | @node Key Index |
572a0c97 JW |
1127 | @unnumbered Key Index |
1128 | ||
1129 | @printindex ky | |
572a0c97 | 1130 | @bye |