aboutsummaryrefslogtreecommitdiffhomepage
path: root/doc_src
diff options
context:
space:
mode:
authorGravatar axel <axel@liljencrantz.se>2006-10-26 20:22:53 +1000
committerGravatar axel <axel@liljencrantz.se>2006-10-26 20:22:53 +1000
commite98a604a2126b23468db50d64874b4d130cdbd4a (patch)
treebac46b4db461429d223be81bcc17a0bc337cb12c /doc_src
parent3341fc888c9b008b6b83603406755610b83f2c94 (diff)
Minor edits, remove unneeded code, add a few commants, correct spelling, tweak the todo list, etc.
darcs-hash:20061026102253-ac50b-eb42fdab9a9211d68386a563134856a96b870d90.gz
Diffstat (limited to 'doc_src')
-rw-r--r--doc_src/doc.hdr5
-rw-r--r--doc_src/function.txt1
-rw-r--r--doc_src/isatty.txt2
3 files changed, 4 insertions, 4 deletions
diff --git a/doc_src/doc.hdr b/doc_src/doc.hdr
index e18e22f6..ca5cf1a9 100644
--- a/doc_src/doc.hdr
+++ b/doc_src/doc.hdr
@@ -1314,14 +1314,14 @@ g++, javac, java, gcj, lpr, doxygen, whois, find)
- Autoreload inputrc-file on updates
- Right-side prompt
- Selectable completions in the pager
-- Access to the whole history in $history
-- Saving of the history in intervals to not loose to much on crashes
- Per process output redirection
- Reduce the space of the pager by one line to allow the commandline to remain visible.
- down-arrow could be used to save the current command to the history. Or give the next command in-sequnce. Or both.
- A pretty-printer.
- Help messages for builtin should not be compiled into fish, they should be kept in a separate directory
- Shellscript functions should be able to show help on the commandline instead of launching a browser
+- Drop support for inputrc-files. Use shellscripts and the bind builtin. Also, redo the syntax for the bind builtin to something more sane.
+- History could reload itself when the file is updated. This would need to be done in a clever way to avoid chain reactions
\subsection bugs Known bugs
@@ -1329,6 +1329,7 @@ g++, javac, java, gcj, lpr, doxygen, whois, find)
- Suspending and then resuming pipelines containing a builtin is broken. How should this be handled?
- screen handling code can't handle tabs in input
+
If you think you have found a bug not described here, please send a
report to <a href="mailto:axel@liljencrantz.se"> axel@liljencrantz.se
</a>.
diff --git a/doc_src/function.txt b/doc_src/function.txt
index 75bf9e88..7bf7ced2 100644
--- a/doc_src/function.txt
+++ b/doc_src/function.txt
@@ -5,7 +5,6 @@
\subsection function-description Description
-- \c -b or \c --key-binding specifies that the function is a key biding. Key binding functions work exactly like regular functions except that they can not be tab-completed.
- <code>-d DESCRIPTION</code> or \c --description=DESCRIPTION is a description of what the function does, suitable as a completion description
- <code>-j PID</code> or <code> --on-job-exit PID</code> tells fish to run this function when the job with group id PID exits. Instead of PID, the string 'caller' can be specified. This is only legal when in a command substitution, and will result in the handler being triggered by the exit of the job which created this command substitution.
- <code>-p PID</code> or <code> --on-process-exit PID</code> tells fish to run this function when the fish child process with process id PID exits
diff --git a/doc_src/isatty.txt b/doc_src/isatty.txt
index 5654c5a2..4ec855e9 100644
--- a/doc_src/isatty.txt
+++ b/doc_src/isatty.txt
@@ -6,7 +6,7 @@
where FILE DESCRIPTOR may be either the number of a file descriptor, or one
of the strings stdin, stdout and stderr.
-If he specified file descriptor is a tty, the exit status of the
+If the specified file descriptor is a tty, the exit status of the
command is zero, otherwise, it is non-zero.