widgets - aerc - mirror of ~rjarry's aerc fork

Mode	Name	Size
-rw-r--r--	account-wizard.go	20379	log stats plain blame
-rw-r--r--	account.go	6935	log stats plain blame
-rw-r--r--	aerc.go	14117	log stats plain blame
-rw-r--r--	common.go	408	log stats plain blame
-rw-r--r--	compose.go	19707	log stats plain blame
-rw-r--r--	dirlist.go	11736	log stats plain blame
-rw-r--r--	exline.go	2467	log stats plain blame
-rw-r--r--	getpasswd.go	1662	log stats plain blame
-rw-r--r--	headerlayout.go	1270	log stats plain blame
-rw-r--r--	msglist.go	7938	log stats plain blame
-rw-r--r--	msgviewer.go	18080	log stats plain blame
-rw-r--r--	pgpinfo.go	2388	log stats plain blame
-rw-r--r--	providesmessage.go	607	log stats plain blame
-rw-r--r--	selector.go	2176	log stats plain blame
-rw-r--r--	spinner.go	1435	log stats plain blame
-rw-r--r--	status.go	2710	log stats plain blame
-rw-r--r--	tabhost.go	320	log stats plain blame
-rw-r--r--	terminal.go	11164	log stats plain blame

file containing all the //: code for the project, and then feed the source file to the compiler. //: (It'll drop these comments starting with a '//:' prefix that only make //: sense before tangling.) //: //: Directives free up the programmer to order code for others to read rather //: than as forced by the computer or compiler. Each individual feature can be //: organized in a self-contained 'layer' that adds code to many different data //: structures and functions all over the program. The right decomposition into //: layers will let each layer make sense in isolation. //: //: "If I look at any small part of it, I can see what is going on -- I don't //: need to refer to other parts to understand what something is doing. //: //: If I look at any large part in overview, I can see what is going on -- I //: don't need to know all the details to get it. //: //: Every level of detail is as locally coherent and as well thought-out as //: any other level." //: //: -- Richard Gabriel, "The Quality Without A Name" //: (http://dreamsongs.com/Files/PatternsOfSoftware.pdf, page 42) //: //: Directives are powerful; they permit inserting or modifying any point in //: the program. Using them tastefully requires mapping out specific lines as //: waypoints for future layers to hook into. Often such waypoints will be in //: comments, capitalized to hint that other layers rely on their presence. //: //: A single waypoint might have many different code fragments hooking into //: it from all over the codebase. Use 'before' directives to insert //: code at a location in order, top to bottom, and 'after' directives to //: insert code in reverse order. By convention waypoints intended for insertion //: before begin with 'End'. Notice below how the layers line up above the "End //: Foo" waypoint. //: //: File 001 File 002 File 003 //: ============ =================== =================== //: // Foo //: ------------ //: <---- :(before "End Foo") //: .... //: ... //: ------------ //: <---------------------------- :(before "End Foo") //: .... //: ... //: // End Foo //: ============ //: //: Here's part of a layer in color: http://i.imgur.com/0eONnyX.png. Directives //: are shaded dark. //: //: Layers do more than just shuffle code around. In a well-organized codebase //: it should be possible to stop loading after any file/layer, build and run //: the program, and pass all tests for loaded features. (Relevant is //: http://youtube.com/watch?v=c8N72t7aScY, a scene from "2001: A Space //: Odyssey".) Get into the habit of running the included script called //: 'test_layers' before you commit any changes. //: //: This 'subsetting guarantee' ensures that this directory contains a //: cleaned-up narrative of the evolution of this codebase. Organizing //: autobiographically allows newcomers to rapidly orient themselves, reading //: the first few files to understand a simple gestalt of a program's core //: purpose and features, and later gradually working their way through other //: features as the need arises. //: //: Programmers shouldn't need to understand everything about a program to //: hack on it. But they shouldn't be prevented from a thorough understanding //: of each aspect either. The goal of layers is to reward curiosity. // Includes // End Includes // Types // End Types // Function prototypes are auto-generated in the 'build' script; define your // functions in any order. Just be sure to declare each function header all on // one line, ending with the '{'. Our auto-generation scripts are too minimal // and simple-minded to handle anything else. #include "function_list" // by convention, files ending with '_list' are auto-generated // Globals // // All statements in this section should always define a single variable on a // single line. The 'build' script will simple-mindedly auto-generate extern // declarations for them. Remember to define (not just declare) constants with // extern linkage in this section, since C++ global constants have internal // linkage by default. // // End Globals int main(int argc, char* argv[]) { atexit(reset); // we require a 32-bit little-endian system assert(sizeof(int) == 4); assert(sizeof(float) == 4); assert_little_endian(); // End One-time Setup // Commandline Parsing // End Commandline Parsing // End Main return 0; } // Unit Tests // End Unit Tests //: our first directive; insert the following headers at the start of the program :(before "End Includes") #include <assert.h> #include <stdlib.h> //: Without directives or with the :(code) directive, lines get added at the //: end. //: //: Regardless of where functions are defined, we can call them anywhere we //: like as long as we format the function header in a specific way: put it //: all on a single line without indent, end the line with ') {' and no //: trailing whitespace. As long as functions uniformly start this way, our //: 'build' script contains a little command to automatically generate //: declarations for them. :(code) void reset() { // End Reset } void assert_little_endian() { const int x = 1; const char* y = reinterpret_cast<const char*>(&x); if (*y != 1) { cerr << "SubX requires a little-endian processor. Do you have Intel (or AMD or Atom) inside?\n"; exit(1); } } :(before "End Includes") #include<iostream> using std::cerr;