Karl Dahlke karl@eklhad.net 248-524-1004 (during regular business hours)
At first, reinventing ed seems a complete waste of time, until you realize that this program also acts as a browser -- a browser embedded inside ed. You can edit a URL as easily as a local file, and activate browse mode to render the html tags in a manner that is appropriate for a command-response program such as this. In other words, we discard most of the formatting information and retain the links and fill-out forms. This allows blind users to access the Internet via an application that is entirely compatible with the linear nature of speech or braille.
I find this approach superior to the "quick fix" of pasting an adaptor onto a preexisting screen browser (lynx) or graphical browser (Netscape). Of course that's just my opinion. To be fair, many blind users, even totally blind users, are satisfied with their auditory screen scrapers. I'm glad it works for them, but this approach frustrates the hell out of me. If you also prefer linear applications, give this browser a try.
This documentation assumes you are familiar with ed. In fact it helps if you are fluent in ed. Experience with internet browsers and the associated terminology is also valuable.
Great! You've read the perlre man page, and you're back. Here are a few changes that I've made to perl regular expressions. I have found that ( and ) are almost always meant to be literal, as in searching for myFunction(), so I reverse the sense of escaped parentheses in perl. That is, ( and ) now match the literal characters, and \( and \) are used to demark substrings of the matched text. These substrings are then referenced, in the replacement string, by $1 through $9. Similarly, | means a literal |, and \| is alternation. I also change the sense of &, on the right hand side, to mean what it means in ed. I leave ^ $ . [ ] + * ? and {n} alone, to be interpreted by perl, as described in the perlre man page. My changes to regexp, to look more like ed, may be confusing if you are a perl expert. Sorry about that, but I think these changes make this editor much easier to use, for everyone, especially the experienced ed users. Below are some additional differences between this program and /bin/ed.
Unlike bash, edbrowse does not retrace your steps back through symbolic links. Thus .. is always the physical parent directory.
environment variables are expanded before the cd command is applied, including the leading ~. Thuse cd ~/work takes you to the work directory under your home directory.
This command does not change any filenames that may be active. You can edit foo, cd .., and write, and foo will be copied to the parent directory. That's probably not what you want, so be careful.
Shell metta characters are also expanded, provided the result is one file name. You can read or write a file by typing a minimal portion of its name. Neither $variables nor stars are expanded for files on the command line, as this expansion is already done by the shell. Of course, if you're on DOS or Windows, that expansion is not performed, so this program performs the expansion for you. This is an attempt to remain portable. You should be able to edit *.c in any operating system and get all the C source files in the current directory.
However, I realize most people still use screen readers, where trailing whitespace is indistinguishable from the blank screen, and a wrapped fragment is sometimes mistaken for a second line. Therefore, you can use the command `el' to place end markers around listed lines. Listed lines begin with ^ and end with $. Enter `ep' to place end markers around all printed lines. Use `eo' to turn end markers off.
Subsequent sections describe new and interesting features, completely foreign to ed. These include the simultaneous edit of multiple files similar to emacs and vi, and the ability to browse an html file and "edit" its fill-out form. That's why I wrote the program in the first place.
if(x == 3 &&
y == 7) {
printf("hello\n");
} else {
printf("world\n");
exit(1);
}
The capital B command, on either the second or the last line, moves to the middle line "} else {", because that balances the open brace. On the first line, B moves to the second line, which balances the open parenthesis. The second line balances {, rather than ), because braces have precedence over parentheses, which have precedence over brackets. You can force a parenthesis match by typing B), which moves from line 2 back to line 1.
The B command on the else line is ambiguous - I don't know whether to look backwards or forwards. You must type B{ or B}.
You can explicitly balance <>, as in multiline html tags, or `', used in some preprocessors such as m4.
Comments or literal strings that contain balancing punctuation marks will definitely throw edbrowse off the track. If you are the author of the source, you might want to avoid braces in comments, or use comments to keep braces in balance.
static char openstring[] = "{block"; /* closing } is found elsewhere */
If you quit a session you are moved to the next valid editing session, wrapping around to session 1 if necessary. The program exits when the last session quits.
Warning, the program contains a bug regarding the undo command. If you switch to another session, then switch back, you cannot undo your last edit. You'd think this would be easy to fix, but it is trickier than it seems, so I haven't gotten rround to it. I just wanted you to know. Make sure everything is copasetic before you switch to another session.
Let's run through a cut&paste example. You are editing file foo in session 1, and you realize that a paragraph from file bar would fit perfectly right here. Here is how it might look. Lines beginning with < are the user's input, and lines beginning with > form the program's responses. The # sign delimits my injected comments.
< e2 # switch to session 2 > new session # Unlike ed, the r command does not establish a file name, even if the # buffer is empty. # Thus "r bar" is safer than "e bar". # The text is not linked to the file bar, # and we cannot accidentally corrupt this file. # After all, we don't want to change bar, we just want to steal from it. < r bar > 28719 < /start/ > This is the start of the cool paragraph that you want to copy. < 1,-d # don't need the stuff before it < /end/ > This is the end of the cool paragraph that you want to copy. < +,$d # don't need the stuff after it < e1 > foo < r2 > 3279 # size of text read from session 2 < q2 # clean house, get rid of session 2 < w # write foo, with the new paragraph included > 62121
The following moves the data from one file to another.
< e2 > new session < e bar # this time I'm going to change bar > 28719 < /start/ > This is the start of the cool paragraph that you want to move. < ka # mark the paragraph < /end/ > This is the end of the cool paragraph that you want to copy. < kb < 'a,'bw3 > 3279 < 'a,'bd < w # write bar, withouth the cool paragraph > 25440 < q > no file # now in session 3 < e1 > foo # back to session 1 < r3 > 3279 < q3 # quit session 3 remotely, while still in session 1 < w # write foo, with the new paragraph included > 62121
An e command, by itself, tells you the current session, in case you've forgotten. This is similar to f, by itself, which tells you the current file.
The arguments are the files to edit. Edbrowse reads these files into corresponding sessions and starts you off in session 1. If there are no arguments, you start in session 1, but there is no text and no associated file.
If you like this program, and you want it to be your primary editor, you can set the following alias.
alias e="perl -w /usr/local/bin/edbrowse"
Hello~07 ~x is ~bd of y
And then listed, you will see the very same text, but there is a bell and a 1/2 character inside. The ~x is not encoded into anything, because x is not a hex digit. If you want to force a ~, even though there are hex digits following, use two tildes, ~~.
When you are entering a regular expression, you have the choice, hex or octal. My program converts ~xx, as a hex value, and the perl regexp machinery converts \nnn, as octal. Thus any of the following will undos a file. The first is translated via my software, the second and third by perl regexp.
,s/~0d$// ,s/\15$// ,s/\r$//
Embedded escape characters are always displayed in hex, whether the line is listed or not. Most terminals and terminal emulaters, including the Linux console and my speech adapter, interpret various escape sequences as control commands. Thus an errant escape sequence from a binary file could send your terminal or your speech adapter into an unexpected state, making recovery difficult. It seems prudent to render escapes as visible characters all the time. If you have no idea where that ~1b came from, it's probably a literal escape character.
Returns and nulls are also converted into hex all the time. Thus an embedded return will not make one line look like two lines. You will usually see this when importing a dos text file. Every line ends in ~0d. Issue one of the three commands shown above to undos the file.
When binary data is first read into the buffer, you will see the words "binary data". After that the buffer remains "binary", even if you delete all the data and read in ascii text. You must use the `e' command to get a fresh, ascii buffer.
For the most part it doesn't really matter if the data is considered binary or ascii. Either way you can display and edit the data, and write it to a file.
This program tries to "do the right thing" under DOS/Windows. That is, it converts crlf to and from newline if it believes the file is text; otherwise it leaves the file alone.
Note that this is not browsing, we are simply retrieving text from another machine and editing it locally. The text need not be html, it could be (for instance) a plain ascii document. Many people, myself included, put various types of files, even executables, on their web sites for retrieval. Of course you wouldn't want to edit a binary file, but you can still use this editor to retrieve the file and save it locally, thus implementing an http download.
While inside the editor, you can type `e URL' to leave the current buffer and retrieve text from a remote machine. Or you can type `r URL' to retrieve remote text and add it to the current buffer. There is no `w URL' command, because the http protocol does not allow you to "write" html source onto a remote machine.
As a convenience, any filename with two or more embedded dots and a standard suffix (such as .com or .net) is treated as a URL. You can usually omit the http:// prefix. Try invoking `e www.whitehouse.gov' to view the home page of the capitol of the United States. But again, you are looking at html source, which probably isn't what you want. Browsing will be discussed later.
Whenever you retrieve data from a URL, the editor, directed by the http protocol, might change the filename out from under you. This is because the resource has moved, and the original computer was kind enough to give you the new address. If debugging is set to 1 or higher, you will see a series of three or four different URLs as the editor is redirected across the internet. Finally it retrieves your document, and the current file name holds the correct URL. You might want to update your bookmark file accordingly. Then again, you might not. Sometimes the initial url is the "public" location of the web page, and subsequent redirections occur inside the company. In this case you'll want to retain the public url, which will always work, even if the company relocates its web server. Use youre best judgment.
When the browse conversion is executed, the system checks for common syntax errors, such as a numbered list that is never closed. If the file name is a URL, these syntax errors are not reported. After all, it's not your web page, and there's nothing you can do about it. However, if the web page is yours, as indicated by a local filename, the first syntax error is displayed, whence you can return to the html source and fix it. Type `ub' to undo the browse conversion. This takes you back to the raw html text under its original filename. Now you can coorect the error and try the `b' command again. For your convenience, the label 'e is set to the line containing the error. Repeat this process until `b' runs without errors.
If you try to quit, and the editor says "expecting `w'", remember that you should be back in raw html before you issue the write command. You could write the browsable text into file.browse, and that will satisfy the "write" criteria, but this isn't really what you want. You've corrected errors in the html source, and that's what you need to save, so remember to undo the browse reformatting before you write the file.
Note that you can issue the unbrowse command even if there were no errors. If, for instance, you are looking at a well-constructed page on some other web site, and you'd like to read or save the raw html, just type ub. As an exercise, invoke `e www.whitehouse.gov', and use the `b' and `ub' commands to switch between the raw html and the browsable text.
The browse reformatting is relatively simple, because a blind person doesn't want complexity. We don't care about fonts and italics etc, and if we do, the best way to obtain this information is by reading the raw html. So most tags are discarded, except those related to headers, paragraphs, and lists. I don't indent subsections or list items. The visual effect is lost on us, and sometimes the extra spaces really get in the way.
Because the physical line is, for us, the unit of thought, i.e. the atomic construct that is modified or moved or copied, lines are cut at approximately 80 characters, give or take a few, usually at a sentence or phrase boundary. Thus reading line by line often reveals a sequence of sentences, or at least self-contained phrases within a larger sentence. I consider this the optimal way to view or edit a document -- any document. If you read these words raw, without doing the browse on the file, you'll see what I mean.
The layout of a preformatted section, <pre>, is honored, although sequences of blank lines are compressed down to one blank line, and whitespace at the end of lines is stripped. This preserves the structure of street addresses, and other preformatted blocks.
Tables are formatted like an ascii unload from a spreadsheet or sql database. Pipes separate the fields on each row. There is no whitespace around the pipes, and the fields of a given row probably won't line up with the fields from the previous row. It isn't pretty, but a blind user can't really trace down a column in any case, especially when using a line editor such as this. Better to write the table to a local file and use cut, sort, join, etc. Here is a sample table.
part number|quantity|price 2635|2|$34.80 1398|1|$67.50 8118|5|$125.00
Empty fields at the end of a row are dropped. These are almost always images -- sometimes an entire row of images -- sometimes an entire table of images. The blind user doesn't need to read the zero-content pipes.
Note that the browsable text is readonly. After all, it's not the "source" -- why should you edit it? There are ways to enter and edit the input fields of an on-line form, but this will be discussed later. For now, you can think of the text as readonly. Issue a move or copy or insert or substitute command, and you'll get an error.
If you do want to edit the text, as text, enter the `et' command (edit as text). You will not be able to return to the html that produced this page. Nor can you follow a hyperlink or submit a fill-out form. The browsable text has become plain text, with no internet semantics.
The command `b file.html' is shorthand for `e file.html', followed by `b'. Remember that the ub command reverses the browse conversion, and reproduces the original html text, as though you had entered `e file.html'.
If a url is opened from the command line, as in "edbrowse www.google.com", it is automatically browsed. Type `ub' to revert back to the raw html.
A subscript, as indicated by html tags, is enclosed in brackets. Thus x<sub>n</sub> becomes x[n]. This transformation is not done if the subscript is a one or two digit number. Thus x subscript 1 is rendered x1, just like your professor would say it. This is not ambiguous, as you might first think; only programmers use x1 as a variable name, not mathematicians. If you see x1 in a formula, it means x subscript 1. Even 17a3b3 is not ambiguous; it is a translation of 17 times a[3] times b[3].
Superscripts are enclosed in parentheses, with a preceeding arrow. The parentheses are omited if the superscript is a number or letter. Thus x cubed looks like x^3, while x to the n-1 power looks like x^(n-1).
There are, sad to say, three different ways to encode mathematical symbols in html. At present edbrowse only supports one of them, though it is the most common, and the most portable among all browsers. This is the symbolic font face, where the Greek letter theta is specified as <font face=symbol>q</font>. Explorer turns this expression into q, one character on the screen, while edbrowse turns it into the word theta. It also puts spaces around the word if its neighbors are also words. This is illustrated by the circumfrence of a circle, which is 2 times pi times r. These three tokens are usually squashed together, and there is no confusion in the sighted world, where pi is a separate Greek letter. But if pi is spelled out, and the tokens are left together, the result is 2pir. Now pir looks like a three letter word. To avoid this, edbrowse inserts spaces, giving 2 pi r. Other symbols, such as degrees, one half, times, etc, are also expanded into words, with the same whitespace considerations.
These translations are designed to work with the pages of the on-line math project, an archive of advanced mathematics that atemps to be both sighted and blind friendly at the same time. This may be impossible, but I'm giving it a shot.
Note that `ft' prints the title of the web page, whereas `f t' renames the current file to "t".
{Recent reports} suggest a connection between ADHD and food additives.
Behind the scenes, "recent reports" is linked to www.feingold.org/research.shtml, but you don't see that unless you activate the link or view the raw html.
Of course the browsable text might also contain words inside braces, especially if the web page is technical in nature. Hence there is some ambiguity. However, I believe it is clear from context. {More information} is probably a link, whereas ${HOME}/.profile is probably not.
Some web pages present a series of icons that are actually links to other pages. That is, you click on an icon, rather than a phrase, to go somewhere else. These icons are suppose to be intuitive. Sometimes they are -- sometimes they're not. In any case, they aren't much use to the blind. Sometimes the web designer is kind enough to supply a text phrase that roughly describes the image. In this case the phrase is used as the link. It appears in braces, as though there were no image at all. If there is no alternate phrase, the filename of the hyperlink reference is used. This name can be surprisingly helpful, or it can be utterly useless, as in "index.html". If this name canot be determined, the generic link {image} is used.
To follow a link, enter the `g' (go) command. Yes, `g' also initiates a global command, such as a global substitute, but only when it is followed by a regular expression. By itself, g follows the link on the current line, 4g follows the link on line 4, and g2 follows the second link on the current line. If a link spreads across multiple lines, you must be on the first of these lines, the line containing the left brace.
The g command can also follow a link that is written in raw text, as long as it "looks" like a valid url. If your friend sends you an interesting url via email, and you save it to a text file, you can "go" to that link, even though the file is not html and you've never issued a browse command.
The g command follows an internal link or an external link. Either way you find yourself in a different place. However, if the link is internal, you are still browsing the same file. In fact, the only thing that has changed is the current line number. The new line is displayed, and should correspond to the link you activated. Often the words are the same. Activate {Appendix I}, and you'll probably see the section heading "Appendix I". Enter z10 to read the first few lines of the appendix.
This feature seems rather silly if you're just editing files, but it makes sense when surfing the net. Often we descend through two or three links, only to find ourselves at a dead end. "I didn't want to go here." So we hit the back key again and again, until we reach familiar territory. We can now proceed in a new direction. The command ^3 or ^^^ backs up through three pages. Don't use this iterative feature unless you know exactly how many times you need to back up.
Note that the entire state of an editing session is saved and reproduced, including the file name, the last change (for undo), the last search/replace strings for substitutions, etc. The only bit that is cleared is the "write pending" bit. After all, the program asked you if you wanted to save the changes when you first edited the new file. Apparently you didn't (having issued the edit command again), so we may as well clear that bit. You can still pop the stack and save the prior changes to disk, but you don't have to.
Unlike lynx, I don't keep a running history of every web page visited. I never really saw a need for this feature. 99% of the time I simply want to back up one or two pages, and that's it. Unfortunately this high-runner operation requires two somersaults and a back flip under lynx. It is a one key command in my browser.
The stack should not be confused with parallel edits, as described in an earlier section. In fact each editing session, e1 e2 e3 ..., has its own internal stack. Parallel sessions are appropriate when you need to move back and forth between two files, or cut&paste between them. However, one session, with its internal stack, is usually sufficient to surf the net.
If a browse command fails completely, giving you a rather uninteresting empty buffer, the stack is popped automatically, taking you back to the previous web page. Now you can retry the link by typing `g' again, or follow a different link on the page. Note that a browse command can fail, and still give you text explaining why it failed, if the remote server is well-designed. In this case you may see the error message "file not found", yet you will be viewing a new web page, which explains the problem. After you've read the explanation, type ^ to back up and try again.
If you are presented with a number, even 0, the stack has been pushed, and you are in a new file or url. Use the ^ command to get back. If there is no number, merely an error message, then edbrowse did not create a new buffer. (It didn't get that far.) Typing . will produce the same line you saw before.
Following an internal link to another section in the current document does not push anything onto the stack. In other words, ^ will not take you back to where you were. In fact, it will take you up to the previous web page, which is not what you want. If you want to take a glance at Appendix I, and then return, mark the current position with `kr'. After you've visited the appendix, use the label 'r to return to your original location in the file.
If you want to follow several web pages in parallel, you can save each one to another session using the w command. The tags and links are transferred along with the rendered text. For example, suppose a web page presents
{planes}
{trains}
{automobiles}
If you are curious about all three topics, issue these commands in this order.
1g w2 ^ 2g w3 ^ 3g w4 ^
Now sessions 2 3 and 4 are the subpages about plains trains and automobiels respectively. You can fill out forms or follow hyperlinks in any of them, or stay in session 1 and do something else.
Keywords: <> Advanced parsing: <-> Language: <en> Search now: <GO> Cleaar form: <RESET>
The first line in this sample form is a simple text field, which is initially empty. You supply the keywords to search for. Entering and editing input fields is discussed later.
The second line is a checkbox. This field tells the search engine to use advanced boolean features, such as this keyword and that, or this, but not that, etc. The feature is disabled, indicated by -. (Most people don't know how to use advanced search anyways.) A + means the checkbox is on.
The third line determines the language of the keywords, English by default. This isn't a free text field, you can't just type in anything you want. We'll describe how to view the options later.
The fourth line is the submit button, which sends the form to the search engine and retrieves the results. This "field" cannot be edited; it is merely a button to push.
The fifth line is also a button to push. It clears all the data you have entered, so you can start over. Default values will be restored. Thus the third line goes back to <en>, rather than <>.
If there is only one input field on the current line, i? displays information about that input field. If the line contains multiple input fields, you will need to use a number, as in i3? for the third field. The type of input field is displayed, then its size, then the current value, then the field name. If the input field is drawn from a set of options, the option list is displayed as well, with menu numbers prepended. When you want to select an option, you can either type in a substring that determines that option uniquely, such as mich for Michigan, or you can type in its menu number. Needless to say, the latter is often easier. Recall the sample form in the previous section. If you type i? at the third field, you might see the following.
select[7] <english> [language] 1: english 2: french 3: german 4: italian 5: spanish
If a select list contains hundreds of options, type i?string to see only those options that contain the specified string. Type I?mi in a state field and get Michigan, Mississippi, Missouri, and Minnesota. Then select the option you want by name or by number.
Now let's do some data entry. Type i=xyz to place xyz in the input field. Remember, you will need to type i3=xyz to put information into the third input field on the current line. If you get an error, it is probably because the field has a fixed set of options, and you didn't pick one of those options. You can either type in one of the options or its menu number. You can also type in a fragment of the option you want, and edbrowse will fill in the rest. This is done whenever one and only one option contains a copy (case insensitive) of the string you entered. Thus you could enter tali above and get Italian, as that is the only language with those four letters. This is useful when you are entering your address, and they ask for the state. Type in a few letters of your state name, enough to be unique, and you'll probably glom onto the correct option in the list. Note the paradigm here: blind people don't want to wade through a menu unless they absolutely have to!
You can use i<7 to pull the contents of session 7 into the current input field. Session 7 must have one line of text. Similarly, i<filename reads the contents of the file into the current input field. Again, the file should contain one line of text. The filename is expanded in the usual way. This includes wildcard expansion, as long as the expansion leads to one and only one file. Put enough characters around the * to designate a single file.
Now suppose you are entering your credit card number, all 16 digits, into a free text field. If you've made a typo, you don't really want to enter the entire string again. No problem -- use the substitute command. You can write this as I/x/y/ or i/x/y/ or s/x/y/ -- whatever you prefer. Remember, you may need to specify a field, as in s3/x/y/. The usual substitution syntax is honored.
If the submit button is the third field on the current line, you can press it via i3*. However, i* is sufficient when there is only one button on the line. Similarly, you can establish a text field by entering i=kangaroo, rather than i1=kangaroo, if the second field on the current line is a submit button. You only need specify a field number when there are multiple input fields, or multiple buttons, on the current line.
The lynx implementation of the text area is particularly hideous. This is not surprising, since lynx is not an editor. You can correct small typos on the current line, but you can't actually "edit" the text you are working on. Once you hit return, that line is done, and you're on to the next line. You can't move lines around or insert lines etc. Nor can you prepare your comments ahead of time and read them into the text area from a file.
In this program, the text area is managed from another editing session. This allows you to use the full power of the editor. You can move text, make global substitutions, or read comments in from a prepared file. The editing session is chosen for you, and appears in the input field. Consider the following form.
Enter your email address: <> Enter your comments: <buffer 2>
In this example session 2 was not active when browsing began. The browser allocated session to specifically for this input field. Type e2 to move to session 2, prepare your comments, and type e1 to return to the input form. On most web pages the text area starts out blank, whence buffer 2 will be empty, but this is not always the case. Be sure to check for pre-existing text before you start typing your thoughts. A particularly arrogant site might preload the text area with: "I love your web site because". When you finally submit the form, as discussed in the next section, text buffer 2, associated with the second editing session, will replace the words "bufffer 2" in the input field. Thus your carefully crafted comments are on their way. (This doesn't mean anybody is going to listen to them.)
The submit button sends the form to the remote server and waits for a response. This is similar to following an internet link, but in this case you are sending some data along with the request. Type "kangaroo" into a search engine and you'll soon be reading a web page about kangaroos. As with any other link, you can use the ^ key to go back. In this case you will return to the on-line form. You can change the data and submit the form again, asking about another animal.
I have implemented the "get" and "post" methods, the most common http protocols, and they seem to work on most sites.
Once you have submitted your form, and you are viewing the results, you may notice some strange characters at the end of the filename. (This only happens under the "get" method.) If you have retrieved information on kangaroos, the filename might look like: www.search-engine.com?keywords=kangaroo. The text after the question mark is an encoded version of the data you entered into the form. It becomes part of the virtual URL. This is actually a feature, as we shall see in the next section.
< b this.that.com/whatever # browse a web page
> 16834 # size of the raw html
> 7855 # size of the browsable text
< /kangaroo/i # looking for kangaroo on the page
> Click here for {more information about kangaroos}, or {send us mail}.
< A # capture the URLs
> 144 # size of the URLs
< ,p # let's see them
> <A HREF=www.kangaroo-info.com>
> more information about kangaroos
> </A>
> send us mail:info@kangaroo.org
< 4d # don't need the email address
< w+ $bookmarks # append this url to the bookmark file
> 336
< ^ # back to browsing
> Click here for {more information about kangaroos}, or {send us mail}.
I suppose I could interrogate the environment variable $bookmarks and append the URL to that file automatically, but as this example shows, you might not want all the links. In fact the email link makes no sense in a bookmark file. Also, you may want to change the description of the link, though in this example the description is pretty reasonable.
Alternatively, you might discard the url and retain the email address, appending it to your address book. Again, you will want to change the generic phrase "send us mail" to a brief string that is meaningful to you, such as kangaroo-mail. This becomes the alias, which you can use to send mail to that recipient. Subsequent sections describe the use of this program as a mail client.
If there are no links on the current line, or you are not in browse mode, the current filename is used. If the filename looks like a URL, it will be enclosed in <A> </A> tags, as though it were a link. This is useful when you want to bookmark the current page, rather than some other page pointed to by a link.
If the current page is the result of a form submition, the filename may include your input fields after the question mark. If it does, that's a feature, not a bug. This exact URL, with the data at the end, can be stored as a bookmark and activated again and again, as though you had filled out the form each time. Every week you can call up this virtual URL to see if there is any new information on kangaroos. A more practical example might be a canned query that retrieves the weather for a certain city or the stock prices for the companies in your portfolio. You can also write concise shell scripts that "fill in" the virtual form, simply by modifying the information after the question mark. This provides a simple command to retrieve the weather from any major city or the current price of any stock.
Not all forms support this type of in-URL encoding. If the A command produces www.search-engine.com, with no ?data at the end, you're out of luck. You will have to fill out the form interactively every time you want to run this query. Fortunately most on-line forms allow you to encode the input fields within the URL. If you are a web designer, do your clients a favor and use the "get" method in your forms whenever possible. This will allow others to create and resubmit canned queries with specific input parameters, or develop shell scripts that query your web site automatically.
Note that only Netscape-style cookies are supported. However, this is the most common flavor of cooky. It will probably meet your needs.
Persistent cookies are stored in a file, $HOME/.cookies, and are thus available for subsequent edbrowse sessions. These cookies are used to store long-term information about you, such as your login and password into amazon.com. Hence your .cookies file should be mode 0600. In fact the file is created mode 0600, for your own protection.
You probably won't need to view your .cookies file, but it is text based, and can be edited directly if you wish. The file format is consistent with lynx, if your version of lynx supports persistent cookies. Thus lynx and edbrowse are interoperable. You can receive cookies from a web site using one browser, switch to the other browser, and pass the appropriate cookies back as expected.
Some pdf files (not all) can be converted into html, though the conversion is rather crude. Still, it is sufficient to read the text and follow the hyperlinks. Several third parties provide conversion utilities, but I believe the best utility, now and in the future, is at access.adobe.com. After all, who knows more about pdf than its creater, adobe.com? I doubt anyone else will do a better job converting to and from pdf, especially as pdf evolves and grows in complexity.
If you retrieve a pdf file from the Internet, edbrowse automatically routes it through access.adobe.com, thus converting it into html. Then the text is rendered in the usual way. Note that the file name is the name of the pdf document, but the request actually went to another url. You might be fetching this.that.com/foobar.pdf, and see the error "cannot connect to access.adobe.com". This seems incongruous until you remember that a separate web server, access.adobe.com, is performing the translation. If you can't get to both web sites, e.g. because of an internet problem, you won't be able to retrieve the data.
You can toggle pdf to html conversion by entering the `ph', pdf to html, command. When conversion is disabled, all pdf files will be downloaded as binary files, and you can do whatever you like with them.
While the control connection is made from the client to the server, the data connection is usually made from the server to the client. This is called active mode ftp. The problem is that this "active mode" doesn't work well if you happen to be behind a firewall.
The solution is passive mode ftp. The data connection is made from the client to the server. Edbrowse uses passive mode by default. But this may not work if the server is behind a firewall. So you have a choice; use the `pm'command to toggle between passive mode and active mode.
Most frames have names - hopefully these names are helpful. If a page uses frames you might see something like this.
Frame top: Stuff about the company, and how to get back to the home page etc. Frame bottom: The stuff you actually asked for, your order, etc.
You can disable frame fetching via the `ff' command, if you know your web sites well, and you want to activate particular frames manually. When frameFetch is disabled, frames look like hyperlinks: frame{top}. Access each one in turn, as if it were just another web page.
There may be web sites out there that won't work unless all the frames are fetched, in order. Suppose the first frame sends your browser a cooky, which it must return when fetching the second frame. I don't know of any web sites like this, but I wouldn't be surprised if there are some out there, so you might want to leave fetchFrames enabled.
Sometimes a hyperlink uses javascript only to open a new window, which brings up the referenced web page. Obviously the notion of a new window is meaningless in edbrowse; every web page is already in its own window. So this program tries to bypass the javascript and replace it with a simple hyperlink. It isn't openNewWindow ("foobar.html") any more, it's just foobar.html. It will look and act just like any other hyperlink.
Keep in mind, I'm using a simple heuristic, encoded in a regular expression. I'm sure there are openWindow() calls that I don't recognize as such, and no doubt there are other javascript calls that I will mistake for a subwindow hyperlink. If you find either a false negative or a false positive, send it along and I'll try to update my heuristics.
Another common javascript function is the validate&submit function. This function checks your entries - have you filled in all the riquired fields - is there an @ sign in your email address - etc. Then, if there are no errors, it submits the form. I can't emulate the javascript, but I can assume you have entered the data correctly and submit the form. The javascript call is replaced with a simple submit button. The same text is used, but the letters js are appended, to remind you that javascript is being bypassed. Thus the last line on a registration form might look like:
<Register now js>
In some cases the javascript function, which I am neatly bypassing, reformats your data. If it does, you're screwed.
The web strip feature, `ws', attempts to delete the redundent text at the start and end of a web page, leaving only the new information. After all, that's why you activated the link in the first place. You can resurrect the deleted text via the unstrip, `us', command.
This feature is called experimental because it isn't very smart. It's more like a cmp than a diff. The slightest change in a line, or insertion of a blank line, will cause web strip to stop in its tracks. Often there is more text that should be deleted, but I don't have time to turn this into a Ph.D. thesis. If anybody wants to beef up this routine, I'd be grateful.
The @ command initiates a web express query. The identifier that follows the @ sign is the name of the query. It is often cryptic, just a couple of letters. For instance, @gg is shorthand for a google search. Type the following to look up information on african elephants.
@gg african elephant
When the page is retrieved, specific post-processing code strips out the extraneous information, and leaves only the results of your search. This is a web strip feature that really works! It works because somebody has tailored it to this particular page. There are no heuristics - no guesses. The down side is the constant maintenance. If google changes its format, we will have to modify the post-processing commands accordingly.
As described earlier, `us' (unstrip) is the opposite of web strip. You can enter the us command to get the entire google page back again. Then you can jump to other places in google, click through the sponsored links, etc.
The web strip feature supports inheritance. If the first page doesn't have the information you are looking for, aned you call up the second page by clicking on the {more results} button, you can use the ws command to strip the second page of results, using the same google-specific commands that were applied to the first page.
Many shortcuts are available - too many to document here. For instance, @yf jnj gets the current stock quote for Johnson and Johnson from yahoo financial, and @mw elephant looks up the word elephant in the on-line Merriam Webster dictionary. And so on. Type @ by itself to get a list of available shortcuts.
Actually, none of these shortcuts are included in the edbrowse program. They are all defined in your .ebrc config file for maximum flexibility. You can modify existing shortcuts or add your own, reflecting your particular interests. See the sample config file for the definitions of various web express commands.
cmdlist = ud < ,s/\r$//
The leading < symbol tells edbrowse that the line contains an edbrowse command. The commands bundled together under the name "foo" are invoked by typing <foo. The same list of commands can be folded into other lists of commands, or into the post-processing directives associated with web express shortcuts. The command list named "init" is run at startup.
If the name of the macro has a + before it in the .ebrc file, execution stops when an error occurs. Without the + sign edbrowse runs all the commands in the set. Note that all the commands are run, no matter what, after a web express shortcut.
Like ls -F, a subdirectory is indicated by a trailing slash. This slash is not part of the filename. Similarly, named pipe is indicated by |, symbolic link by @, block special by *, character special by <, and socket by ^. If a regular file ends in one of these characters, it may confuse you, but it won't confuse this program. Edbrowse knows whether that trailing | is part of the filename or a pipe indicator. Since each file is represented by a single line of text, files with newlines embedded in their names cannot be accessed.
If you read a directory into a preexisting file it is just text. You can't visit any of the underlying files, because they are just words. You must edit a directory in its own session or read a directory into an empty session if you want to access the underlying files. Note that you can write the buffer to another editting session, and in that session the words are just words. This distinction is important as we start to edit the text.
By default, directories are readonly. If you try to delete a line, and hence the associated file, it will tell you that you are still in directory read mode. I'm trying to save you from yourself! Type dw to enable directory writes, and dr to make directories readonly again.
When directory writes are enabled, you can remove files using the d command. For instance, g/\.o$/d removes all the object files. Since these edits have implications outside the scope of this program, there is no undo capability. When you make a change it is made. With this in mind, I borrowed a good idea from Microsoft. The deleted file isn't actually deleted; it is moved to your recycle bin, located in $HOME/.recycle. So if you accidentally type ,d and remove all your files, you can recover them from your recycle bin. You may want to set up a cron job that removes all the files from your recycle bin once a week. This directory is created mode 700, so nobody else can look at your deleted files. If you create this directory yourself, please make if 700.
Because this operation is a move, rather than a true delete, there are a few restrictions based on your operating system. If your OS can move directories, this program will be able to delete a subdirectory as easily as a file. The entire subtree is moved to your recycle bin. Make sure your cleanup cron job is capable of removing directory trees, not just files.
Depending on your OS, you may not be able to move files across file systems. From /disk2 to /disk1, or from the D drive to the C drive. In this case you might want to issue the dx command, which makes directories writable, like dw, but actually deletes the files. You'll need this if you're trying to free up space on the disk. Note that symbolic links are always deleted; there isn't much point in moving a link to the recycle bin.
"What's the point of all this?" you may ask. "What's wrong with the shell?"
Nothing, as long as the file names are small and familiar. But sometimes the file names are long and cumbersome, and it is nearly impossible to type those names into the shell, character for character, upper and lower case, with no mistakes. Meta characters such as the * can help, but only when the file you want has a name radically different from the other files in the directory. This isn't always the case. Suppose an application generates log files as follows.
ProgramFooBar.-04-04-1998.06:31:59.log ProgramFooBar.-04-11-1998.11:37:14.log ProgramFooBar.-04-18-1998.16:22:51.log
How do you delete the old ones and keep the most recent, or rename them to something more manageable? Stars are a bit risky; you can access multiple files without realizing it. And we're not even talking about those pesky files with spaces or invisible control characters in their names. Our sighted friend calls up his file manager and simply clicks on the file he wants to view or edit or remove. Sometimes I want/need that kind of power.
When the substitute command changes text, it renames the underlying file. This won't move the file on top of another existing file, so you can't lose any data this way.
The search and substitute commands ignore the trailing filetype characters. If you want to rename a directory from foo/ to foobar/, you can type s/$/bar/. The bar will be placed at the end of the word foo, because the trailing / isn't really there.
Now suppose you want to run an arbitrary program on some of these files. This could be a print utility,a compiler, whatever. Sometimes you can rename the files for your convenience, then work in the shell. But sometimes you don't own the files, and sometimes they must retain their original names. This happens when several html documents reference each other through hyperlinks, using the aforementioned filenames. So you can't rename the files, yet you still want to run your program on one or two of them.
You can run any program on any file without retyping that filename via the shell escape. Use kx to assign the label x to the file you are interested in. (This is standard ed syntax.) Then run !program 'x to invoke your program on the file in the line labeled x. This sounds involved, but it is merely text substitution, implemented in a few lines of perl. If 'x is present in a shell escape, and is not next to any letters or digits, we replace it with the text on the line labeled x. Thus if your filename contains spaces, you'd better run !program "'x", to make sure the entire file name is one argument to the running program.
The token '. is replaced with the text on the current line, and the token '_ is replaced with the current filename. If you try to write a file, and remember that you left it readonly, you can make it writable via !chmod +w '_, and then write the text to the file.
You can expand multiple tokens in one shell command. Use kx and ky to mark two files that you want to compare, then run !diff 'x 'y.
This feature is not limited to directory scans. You may be editing a simple file, but you can still paste the contents of a line into your shell command. Off hand I don't know why you'd want to do this, but you can.
If a web page is updated every minute, e.g. with the latest stock prices for your favorite companies, you can type rf to fetch the latest copy of this web page. This assumes the url is a direct html reference, or a dynamic fetch using the get method. This will not work with the post method. It also assumes the intervening internet servers are not caching the web page and handing you the same out-of-date copy over and over again.
On your local machine, you can use this feature to read the latest version of a dynamic file, such as a log file. Or you can reread a directory, to incorporate any new files that have been placed in that directory. For example, you might use the shell escape to execute `cat x y >z', yet z will not appear in your directory scan, until you type rf.
All well and good, but some websites have no respect for edbrowse, or lynx for that matter. They won't even let you in the door unless you look like Explorere or Netscape. Clickbank.com, a major credit card processor, is one example.
So what do we do? We lie!
You can specify different agents in your .ebrc file, and activate them with the `ua' (user agent) command. If the following lines are in your .ebrc file, you can type ua1 to pretend to bee lynx, and ua2 to pretend to be Mozilla. Type ua0 to resurrect the standard edbrowse identification. Let's hope there aren't too many asinine websites out there, like Clickbank, that force us to lie.
agent = Lynx/2.8.4rel.1 libwww-FM/2.14
agent = Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90)
This is especially useful in a directory scan. The last thing a blind person wants to worry about is whether some of the letters in a file name are upper case. If directory write mode is enabled, type ,lc to convert all the file names to lower case.
If you want to convert a particular word, type s/word/uc/. This converts the word to upper case. All the other substitution suffixes apply. To change foo, Foo, FOo, and FOO to FOO, everywhere, type ,s/\bfoo\b/uc/ig.
I use this feature in two different ways. If I am familiar with the document, (I probably wrote it), I may use the bl command on a line of text that seems rather long. I typed it in quickly, as an uninterrupted thought, and now I want to break it up. But I don't want to count punctuation marks and say, "I think we need a break after the third comma and the period following that and then at the next comma", issuing the s punctuation commands along the way. Oh I like the s commands well enough - they put you in complete contrl - but it's easier to type bl - and bl usually does the right thing. Also, bl compresses accidental double spaces, a typo that I will never hear if I simply read the line as a whole.
When the document comes in from the outside, usually from another word processor such as MS-Word, bl serves a completely different function. Paragraphs are often stored on a single physical line. Sometimes the entire document is on a single line, with return characters, \r, separating paragraphs. Wysiwyg word processors don't worry about separating sentences and phrases - that's what word wrap is for. Well - bl is our version of word wrap. It doesn't try to conform to any screen; it merely cuts the text into manageable chunks, each piece a separate semantic unit. When bl is issued, physical lines will contain sentences or phrases, as delimited by punctuation, or by the newline/return characters embedded in the original document.
If one of the original lines, delimited by newline or return, is long, i.e. more than 120 characters, it is assumed to be a self-contained paragraph, and a blank line is added before and after. Thus a disassembled paragraph containing 20 sentences does not simply flow into the next disassembled paragraph containing 18 more sentences. An empty line separates the two paragraphs. This is only applicable if bl is applied to a range of lines, or the entire document, as might occur when making an outside document readable.
Don't apply the bl command to a preformatted section, such as a table or ascii art. If you're not sure what to expect, i.e. you didn't write the file, scan through it first, and apply bl to the range of lines that actually represents text. Often this is the entire document (,bl). The following commands do a pretty good job of cleaning up a typical Microsoft Word document.
e whatever.doc or whatever.wps
f _ # don't accidently overwrite the microsoft document
,s/[~80-~ff~00-~0c~0e-~1f]//g; # strip out non ascii control/formatting codes
g/^\s*$/d # these blank lines use to contain non ascii codes
,bl # split lines and paragraphs
1,20p # first couple lines are often garbage, but then the text begins.
Note that this function uses the same software as the browse command. Both commands format the text in the same way. If you change the constant $optimalLine = 80 in the ebrowse source, that affects both the break line and the browse translations.
The recipients, attachments, and subject must appear at the top of your send file. The sm command is picky, so observe the following syntax carefully.
To: fred.flintstone@bedrock.us To: barney.rubble@bedrock.us account: 0 attach: hollyrock-brochure.pdf Subject: Hollyrock Vacation Come visit Hollyrock. Brochure attached. Sincerely, Rock studios incorporated.
The account line is optional. It tells edbrowse to use the first mail account specified in your .ebrc config file. If you don't include an account: line, edbrowse uses the default account, indicated by * in your .ebrc file. That's usually the one you want anyways.
Typing sm5 causes edbrowse to use account number 5 (i.e. the sixth account) in your config file. This overrides the account: line in your file, if there is one. It is often easier to type sm5 than to insert an account:5 line.
Use the attach: lines to add attachments to your email. Each line should specify a file to attach. If the filename is simply a number, the corresponding edbrowse session is used instead. Return to the earlier example, where we are trying to attach a Hollyrock brochure. Another way to do this is to switch to session 2 and edit the pdf file. This is a binary file, but that doesn't matter. Don't do anything with it, just hold it in session 2. Then switch back to session 1 and use the line attach:2.
If you use attach:2, instead of attach:hollyrock-brochure.pdf, Fred will notice one difference. The attachment is not prenamed for him. If he wants to save the attachment, he'll have to come up with a filename himself. Other than that, the email looks the same.
The alt: directive is almost the same as the attach: directive. If you use alt:, the attachment is not treated as an adjunct file. Instead, it is an alternate representation of the same email. The mail client will use the alternate representation if it can. This is usually used to send multimedia email, with hyperlinks and pictures etc. The primary email is in plain text, but the alternate attachment is in html or rich text. Unless something is amiss, the user sees the alternate presentation, complete with graphics and hyperlinks.
Like attachments, the alt: line can refer to a file or an edbrowse session.
As you may have guessed, the to: lines establish the recipients. Please don't specify more than a few recipients. I paste them together into one line, and if that line gets too long, the server might complain. Beyond this, some servers, my mail server included, set a hard limit on the number of recipients. If you exceed this number, usually ten, the remaining recipients simply don't get their mail. Best to limit your "to:" lines to 8 or less.
When specifying recipients, you can use aliases instead of full email addresses. Aliases are checked against your address book, a text file that is specified in your .ebrc file. If your address book contains the line
fred:fred.flintstone@bedrock.us:226 cobblestone way:5553827
then you can simply write "To:fred" at the top of your file. Only the first two fields in the address book are significant as far as edbrowse is concerned. Other fields might hold phone/fax numbers, street address, etc. Note that "Reply to fred" is an alternate syntax for "to: fred".
Some web pages include sendmail links. They look just like other hyperlinks, but they send email to the appropriate person. Click here for more details.
If you activate a sendmail link, you will be placed in a new editing session with the "to" and "subject" lines preloaded. If the url did not specify a subject, the subject is simply "Comments". You will probably want to replace this with a better subject line. Write your mail message and type `sm' to send it on its way. Then type ^ to return to the web page you were looking at. Other aspects of sendmail links are not supported by edbrowse, as they are rarely used.
You can include attachments by placing "attach:" lines at the top of the file, assuming the recipient can handle these attachments. This might make sense when the sendmail link is asking for {bug reports} - you might attach a program and/or its output. Yet this is somewhat unusual. Most sendmail links expect a few sentences of feedback, and nothing more.
Some web forms are submitted via email, rather than a direct http transmission. Edbrowse handles this properly. It shows you the destination email address, sends the mail through smtp, and tells you to watch for a reply. This reply could be an email response, or even a phone call if you provided your phone number in the form. But remember, nothing happens immediately. You are still on the same web page, still looking at the same submit button. Don't push the button again! The mail has been sent, and you'll be hearing from the company in the next few days.
perl edbrowse -m0 fred barney hollyrock-notice +hollyrock-brochure.pdf
Files with the leading + are assumed to be attachments. If they are binary they will be encoded properly, according to the mime standard. A leading - indicates an alternate format, like this.
perl edbrowse -m0 fred barney hollyrock-notice -hollyrock-graphical.html
Remember, you can specify several mail accounts in your .ebrc file. The first account is indicated by index 0, as in -m0. The account with the * (in the config file) is always used as the outgoing smtp server. The -m option does not change this. However, -m3 will set the from and reply address according to account 3, whether that has the * or not. You always use the same smtp server to send your mail, but you can make it look like it came from other places, and direct the replies back to those places.
Suppose you've brought some work home, for instance, and are on your home computer. You want to send mail to your colleagues, but you want it to look like it came from your work account, and more important, you want their replies to go back to your work account so you will see them next morning. Specify the work account via the -m option. Your local server, associated with your home ISP, is still used to send the mail, because that's the only server you can use. Other servers, not associated with your ISP, rarely allow outsiders to send mail. Remember, the smtp protocol has no password. So you always want to use your trusted local mail server to send, even when another account is specified.
All right, that was all very complicated. don't worry about it, edbrowse does the right thing. You can make your life a lot easier with some aliases in your .bashrc file.
# My mail, home account alias mymail="perl /usr/local/bin/edbrowse -m0" # My wife's account; sometimes she doesn't check it for a week. alias wifemail="perl /usr/local/bin/edbrowse -m1" # My work account. alias workmail="perl /usr/local/bin/edbrowse -m2" # mail is obsolete alias mail="echo use mymail, wifemail, or workmail"
? summary of key commands. q quit the program. x abort the program, deleted mail is not really deleted. space display more text. n read the next message. A add the sender to your address book. d delete this message. J junk this subject, and delete any future mail with this subject. w write this message to a file and delete it. k keep this message in a file, but don't delete it. u write this message unformatted to a file and delete it.
The capital A command appends name:address to your address book, where name is the modified name of the sender and address is his email address. Name is converted to lower case, and spaces are turned into dots. Thus it can be typed from the shell, as an email alias, without worrying about upper case letters or quotes. In reality, you're probably going to edit the address file, replace the full name with a simpler alias, and move the line to the section where it belongs. Thus fred.flintstone might simply become fred, as you move the line to the section of cartoon characters.
The last three commands, k w and u, require a filename, which you enter. The reserved filename "x" is essentially /dev/null, hence the mail message, or subordinate attachment, is not saved. You can save the mail message to x (discard) and still save the attachments. If the file is anything other than x, and the program cannot write to the specified file, it dies, rather ungracefully, and you have to reestablish the email session. Yes, I'll make it more fault tolerant in the future.
Mail headers and mime section headers are detected, and most of this header information is discarded. Each header is consolodated down to: subject, from, reply-path, and send-date. That's all you really want to read anyways.
The body of the mail message, or mime section, is then decoded, if it was encoded using quoted-printable or base64 mime standard. Sections encoded via base64 are assumed to be binary attachments. They are never displayed, but you can save them to files if you wish. The interactive program prompts you for this.
Sometimes a mail message is replicated, in plain text and in html. You'll see both versions, separated by a dashed line. The second version has the braces and angle brackets associated with browsable text, but you can't really activate any of the links. You're not in the editor after all. If you plan to browse this email, and fill out the form or follow some of the links therein, save it unformatted to a file. When the mail session is complete, edit that file and browse it. You now have the full power of html at your disposal. This is perhaps not as fuly integrated as Netscape, but it's the best I can do.
If the mail is plain text, we can perform some additional processing for readability. Leading > signs, which indicate nested text, are stripped away, and the words "indent n" are placed at the top of the paragraph, to indicate the number of times the paragraph was > indented. This software is much harder than it first seems, because email servers sometimes break lines longer than 80 characters, and the dangling fragments will not have the leading > characters. The fragment must be inferred from context -- > lines before and after it. Then, a user might prepend > to the entire mess, and send the mail again, whence a server might break some of the lines, which are now longer than 80 characters, thanks to the new > signs. At other times a user might deliberately inject a short comment (which looks like a broken fragment) into a block of someone else's indented text. As you can see, decisions are made by heuristics, and the algorithm is not 100% accurate. It's barely 80% accurate, but it's better than nothing.
A trailing paragraph that begins "to unsubscribe", and is not too long, is removed, because this is usually listmaintenance that you don't need to read again and again. This paragraph may appear at the end of the mail message, or an internal mime section.
This is a multi-part message in MIME format. Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com Do You Yahoo!?
Email lines that match the lines in this file, exactly, are culled, so you don't have to read them. You maintain this file yourself, manually. If a mail message has commercials that you don't want to hear again, save it somewhere, and edit it, leaving only the commercials. Then add these commercials to your growing annoy file. You'll never see them again.
The lines in the annoy file are hashed, so you can include hundreds of lines of text (if you wish) without degrading performance.
qt: quit the program now, whether you've written your files or not db: debug level [0-7] cd: change directory lc: convert line to lower case uc: convert line to upper case mc: convert line to mixed case bl: break line into sentences and phrases sg: substitution strings are global across sessions sl: substitution strings are local to their sessions ci: searches and substitutions are case insensitive cs: searches and substitutions are case sensitive dr: directory is readonly dw: directory is writable, and d moves files to your recycle bin dx: directory is writable, and d deletes files dp: delete-print, print line after each delete (toggle) eo: end markers off el: show end markers ^$ when a line is listed ep: show end markers when a line is listed or printed ub: unbrowse a file f/: retain only the lass component of the filename w/: write to the lass component of the filename w+: append to a file ft: show the title of the current web page fd: show the description of the current web page fk: show the keywords of the current web page ph: auto-convert pdf files to html (toggle) rh: redirect html (toggle) ff: fetch frames automatically (toggle) vs: verify secure connections (toggle) tn: send dos-style newlines on lines in textareas (toggle) ac: accept cookies from web servers (toggle) sr: send refering web page (toggle) pm: run ftp in passive mode (toggle) rf: refresh the web page or directory listing et: edit this web page as pure text ws: strip this web page relative to its parent us: unstrip this web page, inverse of ws sm: send mail [account number]