e reply.tt
reply.tt: No such file or directory
?
a
you can be cool! All you have to do is
use ed!
.
.
use ed!
,
use ed!
,p
you can be cool! All you have to do is
use ed!
w reply.tt
47
q
Name:
Anonymous2011-08-02 16:51
Try gedit with Snippets enabled and you can do shit like this.
FILES
ed.hup The file to which ed attempts to write the buffer if the ter‐
minal hangs up.
SEE ALSO vi(1), sed(1), regex(3), sh(1).
USD:12-13
B. W. Kernighan and P. J. Plauger, SoftwareToolsinPascal, Addison-
Wesley, 1981.
LIMITATIONS ed processes file arguments for backslash escapes, i.e., in a file‐
name, any character preceded by a backslash (\) is interpreted liter‐
ally.
If a text (non-binary) file is not terminated by a newline character,
then ed appends one on reading/writing it. In the case of a binary
file, ed does not append a newline on reading/writing.
Per line overhead: 2 pointers, 1 long int, and 1 int.
DIAGNOSTICS
When an error occurs, if ed's input is from a regular file or here doc‐
ument, then it exits, otherwise it prints a `?' and returns to command
mode. An explanation of the last error can be printed with the `h'
(help) command.
Attempting to quit ed or edit another file before writing a modified
buffer results in an error. If the command is entered a second time,
it succeeds, but any changes to the buffer are lost.
ed exits with 0 if no errors occurred; otherwise >0.
REGULAR EXPRESSIONS
Regular expressions are patterns used in selecting text. For example,
the ed command
g/string/
prints all lines containing string. Regular expressions are also used
by the `s' command for selecting old text to be replaced with new.
In addition to a specifying string literals, regular expressions can
represent classes of strings. Strings thus represented are said to be
matched by the corresponding regular expression. If it is possible for
a regular expression to match several strings in a line, then the left-
most longest match is the one selected.
The following symbols are used in constructing regular expressions:
c Any character c not listed below, including `{', '}', `(', `)',
`<' and `>', matches itself.
\c A backslash-escaped character c other than `{', '}', `(', `)',
`<', `>', `b', 'B', `w', `W', `+', and `?' matches itself.
. Matches any single character.
[char-class]
Matches any single character in char-class. To include a `]'
in char-class, it must be the first character. A range of
characters may be specified by separating the end characters of
the range with a `-', e.g., `a-z' specifies the lower case
characters. The following literal expressions can also be used
in char-class to specify sets of characters:
If `-' appears as the first or last character of char-class,
then it matches itself. All other characters in char-class
match themselves.
Patterns in char-class of the form:
[.col-elm.] or, [=[u]col-elm[/u]=]
where col-elm is a collating element are interpreted according
to locale(5) (not currently supported). See regex(3) for an
explanation of these constructs.
[^char-class]
Matches any single character, other than newline, not in char- class. char-class is defined as above.
^ If `^' is the first character of a regular expression, then it
anchors the regular expression to the beginning of a line.
Otherwise, it matches itself.
$ If `$' is the last character of a regular expression, it
anchors the regular expression to the end of a line. Other‐
wise, it matches itself.
\(re\) Defines a (possibly null) subexpression re. Subexpressions may
be nested. A subsequent backreference of the form `\n', where n is a number in the range [1,9], expands to the text matched
by the nth subexpression. For example, the regular expression
`\(a.c\)\1' matches the string `abcabc', but not `abcadc'.
Subexpressions are ordered relative to their left delimiter.
* Matches the single character regular expression or subexpres‐
sion immediately preceding it zero or more times. If '*' is
the first character of a regular expression or subexpression,
then it matches itself. The `*' operator sometimes yields
unexpected results. For example, the regular expression `b*'
matches the beginning of the string `abbb', as opposed to the
substring `bbb', since a null match is the only left-most
match.
\{n,m\}
\{n,\}
\{n\} Matches the single character regular expression or subexpres‐
sion immediately preceding it at least n and at most m times.
If m is omitted, then it matches at least n times. If the
comma is also omitted, then it matches exactly n times. If
any of these forms occurs first in a regular expression or sub‐
expression, then it is interpreted literally (i.e., the regular
expression `\{2\}' matches the string `{2}', and so on).
\<
\> Anchors the single character regular expression or subexpres‐
sion immediately following it to the beginning (\<) or ending
(\>) of a word, i.e., in ASCII, a maximal string of alphanu‐
meric characters, including the underscore (_).
The following extended operators are preceded by a backslash (\) to
distinguish them from traditional ed syntax.
\`
\' Unconditionally matches the beginning (\`) or ending (\') of a
line.
\? Optionally matches the single character regular expression or
subexpression immediately preceding it. For example, the regu‐
lar expression `a[bd]\?c' matches the strings `abc', `adc' and
`ac'. If \? occurs at the beginning of a regular expressions
or subexpression, then it matches a literal `?'.
\+ Matches the single character regular expression or subexpres‐
sion immediately preceding it one or more times. So the regu‐
lar expression `a\+' is shorthand for `aa*'. If \+ occurs at
the beginning of a regular expression or subexpression, then it
matches a literal `+'.
\b Matches the beginning or ending (null string) of a word. Thus
the regular expression `\bhello\b' is equivalent to
`\<hello\>'. However, `\b\b' is a valid regular expression
whereas `\<\>' is not.
COMMANDS
All ed commands are single characters, though some require additional
parameters. If a command's parameters extend over several lines, then
each line except for the last must be terminated with a backslash (\).
In general, at most one command is allowed per line. However, most
commands accept a print suffix, which is any of `p' (print), `l' (list)
, or `n' (enumerate), to print the last line affected by the command.
An interrupt (typically ^C) has the effect of aborting the current com‐
mand and returning the editor to command mode.
ed recognizes the following commands. The commands are shown together
with the default address or address range supplied if none is specified
(in parenthesis).
(.)a Appends text to the buffer after the addressed line, which may
be the address 0 (zero). Text is entered in input mode. The
current address is set to last line entered.
(.,.)c Changes lines in the buffer. The addressed lines are deleted
from the buffer, and text is appended in their place. Text is
entered in input mode. The current address is set to last line
entered.
(.,.)d Deletes the addressed lines from the buffer. If there is a
line after the deleted range, then the current address is set
to this line. Otherwise the current address is set to the line
before the deleted range.
e file Edits file, and sets the default filename. If file is not
specified, then the default filename is used. Any lines in
the buffer are deleted before the new file is read. The cur‐
rent address is set to the last line read.
e !command
Edits the standard output of `!command', (see !command below).
The default filename is unchanged. Any lines in the buffer are
deleted before the output of command is read. The current
address is set to the last line read.
E file Edits file unconditionally. This is similar to the e command,
except that unwritten changes are discarded without warning.
The current address is set to the last line read.
f file Sets the default filename to file. If file is not specified,
then the default unescaped filename is printed.
(1,$)g/re/command-list
Applies command-list to each of the addressed lines matching a
regular expression re. The current address is set to the line
currently matched before command-list is executed. At the end
of the `g' command, the current address is set to the last line
affected by command-list.
Each command in command-list must be on a separate line, and
every line except for the last must be terminated by a back‐
slash (\). Any commands are allowed, except for `g', `G', `v',
and `V'. A newline alone in command-list is equivalent to a `p' command.
(1,$)G/re/
Interactively edits the addressed lines matching a regular
expression re. For each matching line, the line is printed,
the current address is set, and the user is prompted to enter a command-list. At the end of the `G' command, the current
address is set to the last line affected by (the last) command- list.
The format of command-list is the same as that of the `g' com‐
mand. A newline alone acts as a null command list. A single
`&' repeats the last non-null command list.
H Toggles the printing of error explanations. By default, expla‐
nations are not printed. It is recommended that ed scripts
begin with this command to aid in debugging.
h Prints an explanation of the last error.
(.)i Inserts text in the buffer before the current line. Text is
entered in input mode. The current address is set to the last
line entered.
(.,.+1)j
Joins the addressed lines. The addressed lines are deleted
from the buffer and replaced by a single line containing their
joined text. The current address is set to the resultant line.
(.)klc Marks a line with a lower case letter lc. The line can then
be addressed as 'lc (i.e., a single quote followed by lc ) in
subsequent commands. The mark is not cleared until the line is
deleted or otherwise modified.
(.,.)l Prints the addressed lines unambiguously. If invoked from a
terminal, ed pauses at the end of each page until a newline is
entered. The current address is set to the last line printed.
(.,.)m(.)
Moves lines in the buffer. The addressed lines are moved to
after the right-hand destination address, which may be the
address 0 (zero). The current address is set to the new
address of the last line moved.
(.,.)n Prints the addressed lines along with their line numbers. The
current address is set to the last line printed.
(.,.)p Prints the addressed lines. If invoked from a terminal, ed
pauses at the end of each page until a newline is entered. The
current address is set to the last line printed.
P Toggles the command prompt on and off. Unless a prompt was
specified by with command-line option -pstring, the command
prompt is by default turned off.
q Quits ed.
Q Quits ed unconditionally. This is similar to the q command,
except that unwritten changes are discarded without warning.
($)r file
Reads file to after the addressed line. If file is not speci‐
fied, then the default filename is used. If there was no
default filename prior to the command, then the default file‐
name is set to file. Otherwise, the default filename is
unchanged. The current address is set to the last line read.
($)r !command
Reads to after the addressed line the standard output of `!com‐ mand', (see the !command below). The default filename is
unchanged. The current address is set to the last line read.
(.,.)s/re/replacement/
(.,.)s/re/replacement/g
(.,.)s/re/replacement/n
Replaces text in the addressed lines matching a regular expres‐
sion re with replacement. By default, only the first match in
each line is replaced. If the `g' (global) suffix is given,
then every match to be replaced. The `n' suffix, where n is a
positive number, causes only the nth match to be replaced. It
is an error if no substitutions are performed on any of the
addressed lines. The current address is set to the last line
affected.
re and replacement may be delimited by any character other than
space, newline and the characters used by the form of the `s'
command shown below. If one or two of the last delimiters is
omitted, then the last line affected is printed as though the
print suffix `p' were specified.
An unescaped `&' in replacement is replaced by the currently
matched text. The character sequence `\m', where m is a number
in the range [1,9], is replaced by the mth backreference
expression of the matched text. If replacement consists of a
single `%', then replacement from the last substitution is
used. Newlines may be embedded in replacement if they are
escaped with a backslash (\).
(.,.)s Repeats the last substitution. This form of the `s' command
accepts a count suffix `n', and any combination of the charac‐
ters `r', `g', and `p'. If a count suffix `n' is given, then
only the nth match is replaced. The `r' suffix causes the reg‐
ular expression of the last search to be used instead of the
that of the last substitution. The `g' suffix toggles the
global suffix of the last substitution. The `p' suffix toggles
the print suffix of the last substitution. The current address
is set to the last line affected.
(.,.)t(.)
Copies (i.e., transfers) the addressed lines to after the
right-hand destination address, which may be the address 0
(zero). The current address is set to the last line copied.
u Undoes the last command and restores the current address to
what it was before the command. The global commands `g', `G', `v', and `V'. are treated as a single command by undo. `u' is
its own inverse.
(1,$)v/re/command-list
Applies command-list to each of the addressed lines not match‐
ing a regular expression re. This is similar to the `g' com‐
mand.
(1,$)V/re/
Interactively edits the addressed lines not matching a regular
expression re. This is similar to the `G' command.
(1,$)w file
Writes the addressed lines to file. Any previous contents of file is lost without warning. If there is no default filename,
then the default filename is set to file, otherwise it is
unchanged. If no filename is specified, then the default file‐
name is used. The current address is unchanged.
(1,$)wq file
Writes the addressed lines to file, and then executes a `q'
command.
(1,$)w !command
Writes the addressed lines to the standard input of `!command',
(see the !command below). The default filename and current
address are unchanged.
(1,$)W file
Appends the addressed lines to the end of file. This is simi‐
lar to the `w' command, expect that the previous contents of
file is not clobbered. The current address is unchanged.
(.)x Copies (puts) the contents of the cut buffer to after the
addressed line. The current address is set to the last line
copied.
(.,.)y Copies (yanks) the addressed lines to the cut buffer. The cut
buffer is overwritten by subsequent `y', `s', `j', `d', or `c'
commands. The current address is unchanged.
(.+1)zn Scrolls n lines at a time starting at addressed line. If n is
not specified, then the current window size is used. The cur‐
rent address is set to the last line printed.
!command
Executes command via sh(1). If the first character of command
is `!', then it is replaced by text of the previous `!command'.
ed does not process command for backslash (\) escapes. How‐
ever, an unescaped `%' is replaced by the default filename.
When the shell returns from execution, a `!' is printed to the
standard output. The current line is unchanged.
(.,.)# Begins a comment; the rest of the line, up to a newline, is
ignored. If a line address followed by a semicolon is given,
then the current address is set to that address. Otherwise,
the current address is unchanged.
($)= Prints the line number of the addressed line.
(.+1)newline
Prints the addressed line, and sets the current address to that
line.
FILES
ed.hup The file to which ed attempts to write the buffer if the ter‐
minal hangs up.
SEE ALSO vi(1), sed(1), regex(3), sh(1).
USD:12-13
B. W. Kernighan and P. J. Plauger, SoftwareToolsinPascal, Addison-
Wesley, 1981.
LIMITATIONS ed processes file arguments for backslash escapes, i.e., in a file‐
name, any character preceded by a backslash (\) is interpreted liter‐
ally.
If a text (non-binary) file is not terminated by a newline character,
then ed appends one on reading/writing it. In the case of a binary
file, ed does not append a newline on reading/writing.
Per line overhead: 2 pointers, 1 long int, and 1 int.
DIAGNOSTICS
When an error occurs, if ed's input is from a regular file or here doc‐
ument, then it exits, otherwise it prints a `?' and returns to command
mode. An explanation of the last error can be printed with the `h'
(help) command.
Attempting to quit ed or edit another file before writing a modified
buffer results in an error. If the command is entered a second time,
it succeeds, but any changes to the buffer are lost.
ed exits with 0 if no errors occurred; otherwise >0.
Fuck, I copied the last part first. Please disregard me.
Name:
Anonymous2011-08-02 20:31
free HTML Editor
Does "free" mean "comes bundled with the OS"? Then, under Windows (from the company that brought you EDLIN), there's Notepad.
Otherwise, in text mode, there's my personal favourite: Midnight Commander's internal editor mcedit. Or (decidedly not my personal favourites) vi(m), ed, emacs, etc.
In graphics mode, there's gedit.
I've never needed anything with real-time WYSIWYG or somesuch, tho, so dunno about those...
Name:
ack2011-08-02 23:04
For Windows, nothing beats Notepad++ for text editing. Google it.
This thread reminded me I wanted to write my own browser.
Several years ago I looked at HTML 4.01 and it wasn't exactly trivial, but today I glanced at HTML5 and... HOLY FUCKING SHIT WHAT THE BLOAT DID THEY DO?!
The same with CSS3 vs CSS2.1, it seems they just want to pack as much useless trivial flashy distracting shit in there as they can.
>>28
I wouldn't say that. From what I've read about the standard, each addition to HTML5 is well reasoned by the virtue that these elements describe some data sensibly and will be used widely as a general standard ought to be.
Name:
Anonymous2011-08-03 5:21
>>29
each addition to COBOL is well reasoned by the virtue that these elements describe some data sensibly and will be used widely as a general standard ought to be.
each addition to BDSM is well reasoned by the virtue that these elements describe some data sensibly and will be used widely as a general standard ought to be.
each addition to HASKELL is well reasoned by the virtue that these elements describe some data sensibly and will be used widely as a general standard ought to be.