+By default, there are seven colors you may use in the terminal: red, green, yellow, blue, magenta, cyan, and white. In order to use color in Zephyr, you can use the following notation: {{{@(@color(red)This is some red text))}}}
+
+Colors may vary from machine to machine, as different terminal profiles may have different shades of the seven colors.
+
+=== Filters ===
+
+Some people like to customize their Barnowl by color-coding classes. This makes it easier to tell different classes apart (and minimize mixing). Barnowl has some already existing filters, for example, {{{personal}}} (for incoming personals), {{{out}}} (for outgoing personals), and {{{ping}}} (for pings). To assign a color to a filter, add the following to your startup file:
+
+{{{
+filter personal -c green
+}}}
+
+What if you want to color-code your class, or a friends class? You can create and color filters with:
+
+{{{
+filter johndoe class johndoe
+filter johndoe -c blue
+}}}
+
+You can update your settings and filters without restarting your Barnowl session by:
+
+{{{
+:source ~/path/to/config/file
+}}}
+
+You can see all the filters by using {{{:show filters}}}, and narrow to a particular filter with, e.g., {{{:view personal}}}. You can use {{{:view all}}} or the keyboard shortcut {{{V}}} to see all messages again.
+
+For more detailed information on filters, visit https://barnowl.scripts.mit.edu:444/wiki/Filters.
+
+== Running Barnowl in Screen ==
+
+It can be very annoying to have to close Barnowl when you turn off your computer. During the time your computer is off, you're missing many (possibly important) zephyrs. It can be aggravating to be using zephyr via an unreliable network connection. It can also be frustrating if you leave your computer on with Zephyr up, but go to a different computer and want to check your zephyrs - how do you do this? These problems can be solved with the magic of screen.
+
+A more detailed and extensive explanation of this can be found at http://web.mit.edu/kchen/bin/owl-screen.txt.
+
+=== Screen ===
+
+You should find a computer or server on which to run your screen session(s) that is up all the time, for example, linerva.mit.edu. Screen allows you to run programs inside of it on one computer, and to access those same programs from other computers via ssh.
+
+=== Quickstart ===
+
+1. Pick a machine to host your screen session on. If you don't know of any options, linux.mit.edu (Linerva) is a good choice.
+2. ssh to that machine.
+3. Run "add kchen". You may want to add this to your {{{~/.environment}}} file.
+4. Run "owl-screen"
+
+Your screen session is now ready. Once you start the screen session, you'll need to get renewable Kerberos tickets in order to run it for any extended period of time. Press C-a C-c to open a new screen window, and run
+
+{{{
+kinit -l7d -54
+}}}
+
+(length 7 days, both Kerberos 5 and Kerberos 4). Press C-a 0 to return back to your Barnowl window.
+
+When you're ready to log out, press C-a d to "detach" your screen, and then type {{{exit}}} or {{{logout}}} to log out. Later, when you want to "reattach" your screen, ssh to the machine again, and run {{{screen -r}}}.
+
+=== Kerberos Tickets and AFS Tokens ===
+
+In order to keep your screen session authenticated, you'll need to keep your Kerberos tickets and AFS tokens up-to-date. There is a script that will do this for you, located in the {{{kchen}}} locker. After you ssh into the machine that hosts your screen sessions, run the following commands:
+
+{{{
+add kchen
+owl-screen
+C-a C-c
+kinit -l1d -r7d -54
+}}}
+
+=== Attaching and Detaching Sessions ===
+
+To detach a screen session (for example, if you want to log out), press C-a d (Control-A, then D). Screen continues to run, but is no longer active.
+
+To reattach a screen session, possibly detaching from wherever it's currently attached, run:
+
+{{{
+screen -dr
+}}}
+
+{{{screen}}} can do a whole lot more. To find out about it, see UsingScreen.
\ No newline at end of file
sipb-www / wiki.git / blobdiff