[hackers] [sites] Linkyfi more stuff. || uriel

changeset: 85:725e1900a3b4
user: uriel_AT_localhost.localdomain
date: Sun May 03 23:23:06 2009 +0200
files: libs.suckless.org/libixp.md www.suckless.org/common/dynamic_window_management.md www.suckless.org/common/project_ideas.md
description:
Linkyfi more stuff.

diff -r 4265684bceac -r 725e1900a3b4 libs.suckless.org/libixp.md
--- a/libs.suckless.org/libixp.md Sun May 03 23:17:05 2009 +0200
+++ b/libs.suckless.org/libixp.md Sun May 03 23:23:06 2009 +0200
@@ -2,7 +2,7 @@
 ======
 `libixp` is a stand-alone client/server [9P](http://9p.cat-v.org/) library including `ixpc` client. It consists of less than 2000 lines of code (including `ixpc`).
 
-`libixp`'s server API is based heavily on that of [Plan 9](http://cm.bell-labs.com/plan9)'s `lib9p`, and the two libraries export virtually identical data structures. There are a few notable differences between the two, however:
+`libixp`'s server API is based heavily on that of [Plan 9](http://cm.bell-labs.com/plan9)'s `[lib9p](http://man.cat-v.org/plan_9/2/9p)`, and the two libraries export virtually identical data structures. There are a few notable differences between the two, however:
 
 * `libixp` multiplexes connections internally, while on `Plan 9`, the kernel performs this task, and in [plan9port](http://plan9.us/), a separate process is spawned to do so. Despite this divergence, the user of the library will not notice any difference in behavior, except that there may be duplicate `tag` and `fid` numbers between different connections. This issue is of little relevance, however, as the library handles the task of mapping `fid`s and `tag`s to arbitrary pointers and `P9Req` structs.
 
diff -r 4265684bceac -r 725e1900a3b4 www.suckless.org/common/dynamic_window_management.md
--- a/www.suckless.org/common/dynamic_window_management.md Sun May 03 23:17:05 2009 +0200
+++ b/www.suckless.org/common/dynamic_window_management.md Sun May 03 23:23:06 2009 +0200
@@ -2,12 +2,13 @@
 =========================
 
 We think that static window management as seen in Ion or wmi-10 is a far too
-rigid and inflexible working environment. In acme, larswm, and oberon, dynamic
-window management frees the user from these limitations. The user can start as
-many applications and windows as he likes, and easily arrange them in a useful
-way, helped by the window manager - the working environment changes with the
-tasks the user is performing. The experience is very fluid and natural.
-Similar concepts have been introduced in wmii and dwm.
+rigid and inflexible working environment. In [acme](http://acme.cat-v.org),
+larswm, and oberon, dynamic window management frees the user from these
+limitations. The user can start as many applications and windows as he likes,
+and easily arrange them in a useful way, helped by the window manager - the
+working environment changes with the tasks the user is performing. The
+experience is very fluid and natural. Similar concepts have been introduced in
+wmii and dwm.
 
 Dynamic window management states that it is the window manager's job to manage
 windows - and not the user's job to have to set up some specialized layout that
diff -r 4265684bceac -r 725e1900a3b4 www.suckless.org/common/project_ideas.md
--- a/www.suckless.org/common/project_ideas.md Sun May 03 23:17:05 2009 +0200
+++ b/www.suckless.org/common/project_ideas.md Sun May 03 23:23:06 2009 +0200
@@ -120,7 +120,7 @@
 ### Yet another less sucking editor
 
 Although vi(m) does its job, it has become a monster over the years. We
-believe there is a gap between ed, sam, acme and vim which must be filled with
+believe there is a gap between [ed](http://man.cat-v.org/plan_9/1/ed), [sam](http://sam.cat-v.org), [acme](http://acme.cat-v.org) and vim which must be filled with
 a completely new, less-sucking editor.
 
 ***Requirements:*** Good C knowledge and knowledge of I/O APIs is essential.
Received on Sun Aug 16 2009 - 10:54:03 UTC