summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobin H. Johnson <robbat2@gentoo.org>2015-08-08 13:49:04 -0700
committerRobin H. Johnson <robbat2@gentoo.org>2015-08-08 17:38:18 -0700
commit56bd759df1d0c750a065b8c845e93d5dfa6b549d (patch)
tree3f91093cdb475e565ae857f1c5a7fd339e2d781e /x11-wm/stumpwm/files
downloadgentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.gz
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.bz2
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.zip
proj/gentoo: Initial commit
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
Diffstat (limited to 'x11-wm/stumpwm/files')
-rw-r--r--x11-wm/stumpwm/files/70stumpwm-gentoo.el2
-rw-r--r--x11-wm/stumpwm/files/README.Gentoo56
2 files changed, 58 insertions, 0 deletions
diff --git a/x11-wm/stumpwm/files/70stumpwm-gentoo.el b/x11-wm/stumpwm/files/70stumpwm-gentoo.el
new file mode 100644
index 000000000000..c07bdf2de499
--- /dev/null
+++ b/x11-wm/stumpwm/files/70stumpwm-gentoo.el
@@ -0,0 +1,2 @@
+(add-to-list 'load-path "@SITELISP@")
+(autoload 'stumpwm-mode "stumpwm-mode" nil t)
diff --git a/x11-wm/stumpwm/files/README.Gentoo b/x11-wm/stumpwm/files/README.Gentoo
new file mode 100644
index 000000000000..7277305dcda1
--- /dev/null
+++ b/x11-wm/stumpwm/files/README.Gentoo
@@ -0,0 +1,56 @@
+
+This file is installed in /usr/share/doc/stumpwm-cvs-*/README.Gentoo.gz
+
+Stumpwm notes for Gentoo
+------------------------
+
+As always with CVS ebuilds, DO NOT report problems to upstream.
+Always report problems to the Gentoo Bugzilla at
+http://bugs.gentoo.org/.
+
+This is a live CVS port of Stumpwm therefore every time you emerge
+x11-wm/stumpwm-cvs you will be installing the most recent Stumpwm.
+You may not always get a working Stumpwm. The ebuild supports setting
+ECVS_BRANCH from outside the ebuild so you can select Stumpwm CVS
+source from the past.
+
+Starting Stumpwm
+----------------
+
+For the moment, actually starting Stumpwm is left as an exercise for
+the user. Some users may prefer to load SLIME (via SWANK) support
+into the image with Stumpwm and some users may prefer not to.
+Deciding on SLIME TCP port numbers is also a user decision. Users may
+wish to experiment with Stumpwm in different Common Lisp
+implementations or just use a particular implementation.
+
+Here are some hints to get you started:
+
+ (asdf:oos 'asdf:load-op :stumpwm)
+
+Start a SLIME listener:
+
+ (asdf:oos 'asdf:load-op :swank)
+ (swank:create-swank-server 4005 :spawn)
+
+Then you can connect your Emacs to the Stumpwm image later using the
+following from Emacs:
+
+ M-x slime-connect RET 127.0.0.1 RET 4005 RET
+
+Isn't SLIME wonderful?. You might consider app-misc/detachtty or
+app-misc/screen for recovering the REPL if not using SLIME.
+
+Start Stumpwm:
+
+ (stumpwm:stumpwm ":0")
+
+You might also consider dev-lisp/cl-launch which is an excellent way
+to wrap up Common Lisp systems into a single, portable shell script.
+For example, the following creates a ~/bin/mystumpwm script which will
+try to load the stumpwm system definition into SBCL. If that fails,
+it will try CLISP:
+
+ cl-launch --output ~/bin/mystumpwm --lisp "sbcl clisp" \
+ --system stumpwm --init '(stumpwm:stumpwm ":0")'
+