Explore projects
-
Updated
-
Hugo Hörnquist / muppet-strings
GNU Affero General Public License v3.0Updated -
-
Updated
-
Updated
-
Per Cederqvist / mcwm
BSD Zero Clause LicenseMy fork of mcwm, containing bugfixes and personal configuration changes. See http://hack.org/mc/projects/mcwm/ for the original project.
Updated -
Lysator / LYSrdiff
GNU General Public License v2.0 or laterUpdated -
-
Per Cederqvist / lyskom-server-ceder-1616-generations-topgit
GNU General Public License v2.0 or laterAn attempt to solve bug 1616 of the lyskom-server, storing the code using TopGit.
Updated -
The main repository of the LysKOM client written in Emacs Lisp.
Updated -
The main repository of the LysKOM client written in Emacs Lisp.
Updated -
The main repository of the LysKOM client written in Emacs Lisp.
Updated -
The main repository of the LysKOM client written in Emacs Lisp.
Updated -
-
Föreningen för Föreningsaktiva / logo-byggare
GNU Affero General Public License v3.0Updated -
Presentation templates for the LaTeX system, using the Beamer document class.
Updated -
-
Magnus Holmgren / liboop
GNU Lesser General Public License v2.1 onlyLiboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the “select() loop” and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application.
Initially developed by Dan Egnor, liboop is now maintained by Niels Möller and Per Cederqvist.
Updated -
liboop / liboop
GNU Lesser General Public License v2.1 onlyLiboop is a low-level event loop management library for POSIX-based operating systems. It supports the development of modular, multiplexed applications which may respond to events from several sources. It replaces the “select() loop” and allows the registration of event handlers for file and network I/O, timers and signals. Since processes use these mechanisms for almost all external communication, liboop can be used as the basis for almost any application.
Initially developed by Dan Egnor, liboop is now maintained by Niels Möller and Per Cederqvist.
Updated