[email protected] wrote: |Michael Convey <[email protected]> wrote: |> .. |> Is there a command that can be entered at the '&' prompt to compose a new |> message? Or, do you have to exit mailx and start over? ? | |The usual way would be "m <recipient(s)>" which will prompt for a Subject |line then let you start typing in a message. Most people like to compose |their messages in an editor, and usually their default editor is defined |in the EDITOR and/or VISUAL shell environmental variables. Assuming you |have a default editor defined, you can envoke it with "~e" on a new line |("~v" also works unless you're in a ssh session in which it may toggle |ssh into "verbose" which is a bit annoying). Once in your default editor
You can change the tilde ~ character to something else by setting the *escape* variable -- a circumstance that already caused 3BSD from 1980 to name the term "tilde escape" a "misnomer". |you can compose your message and exit, returning you to the '&' prompt; |then enter a "." on a new line and you'll be prompted for a few standard With the *dot* variable set the message considered to start its long and winding way with the dot, though. |email headers and probably paths to any attachments you want to attach. |If you want to further edit the To: or Reply To: headers use "~h"; to edit |the From: field use "~H"; to re-enter your default editor use "~e"; to |print to screen message in current state use "~p" or "~P" (all headers |displayed). | |You might read through the manpage and/or some standard Unix mailx User |Guides[1,2] for other examples and possibilities. |[1] http://docs.oracle.com/cd/E19683-01/806-7612/mail-1/index.html |[2] http://engineering.purdue.edu/ECN/Support/KB/Docs/MailXTutorial Well ok but i really don't think these are good pointers. I think Gunnar's manual is better than these, and, really sorry, but i have to point to the documentation of my S-nail, which is fully cross-referenced in addition[1] (it's even better on the terminal if you have mdocmx(7) due to referenceability of referenced manual pages, but noone has groff(1) and less(1) patched up yet). Or the ArchLinux Wiki[2]. Of course the latter are S-nail with all its extensions, but the Oracle doc for example is professional industry after loss assessment. [1] http://sdaoden.users.sourceforge.net/code-nail.html [2] https://wiki.archlinux.org/index.php/S-nail --steffen ------------------------------------------------------------------------------ _______________________________________________ nail-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nail-devel
