ryuslash/orgweb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update and add project pages

Browse source 
I've once again thought up a different common structure for website
pages, I hope this one sticks longer than the ones before, but this
limits duplication of data somewhat and keeps maintenance costs of
these pages fairly low.
This commit is contained in:
Tom Willemsen 2013-01-19 02:48:40 +01:00
parent a3a3f0cf54
commit eb9348bf34
11 changed files with 327 additions and 311 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

59
site/projects/baps1.org Normal file
View file

@ -0,0 +1,59 @@
#+TITLE: baps1
#+LINK: src http://code.ryuslash.org/cgit.cgi/baps1/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/baps1/snapshot/baps1-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/baps1/snapshot/baps1-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/baps1/about/
#+LINK: manual http://ryuslash.org/projects/baps1/manual/
#+STARTUP: showall
#+begin_html
<script src="/keyjs.js" type="text/javascript"></script>
<script type="text/javascript">
keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
"h": [ "keyjs_goto", "http://ryuslash.org" ] });
</script>
#+end_html
#+INCLUDE: "dlmenu.inc"
* What does it do?
baps1 offers a, hopefully, efficient and easy way to add certain
data to your PS1 (prompt).
| Language | C |
| License | GPLv3 |
* Why was it written?
A friend of mine wanted a better way to get some functionality into
his PS1 that he was using a PHP script for, I knew how to do that
in C and thought it would be a fun project and good learning
experience, so here we are.
* Who is it for?
Anyone who likes to have the data this project provides in their
PS1.
* Data
| Version | 0 (development only) |
| Language | C |
| License | |
** Features
- Show the PTY or TTY you are using.
- How long ago the last call to baps1 was on that terminal, which
should also indicate how long ago your PS1 was printed last.
** Dependencies
Apart from the usual build tools (make, gcc) I know of none,
though I do have a preference for GNU programs/libraries, so there
might be some GNU-only code in there.
* More...
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].

95
site/projects/dispass.el.org
View file

@ -2,6 +2,8 @@
#+LINK: src http://code.ryuslash.org/cgit.cgi/emacs/dispass.el/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/emacs/dispass.el/snapshot/dispass.el-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/emacs/dispass.el/snapshot/dispass.el-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/emacs/dispass.el/about/
#+LINK: manual http://ryuslash.org/projects/dispass.el/manual/
#+LINK: dispass http://dispass.babab.nl
#+STARTUP: showall
@ -15,91 +17,48 @@
#+INCLUDE: "dlmenu.inc"
* About
* What does it do?
[[dispass][DisPass]] is a passphrase generator. ~dispass.el~ is an [[emacs][Emacs]] wrapper
[[dispass][DisPass]] is a passphrase generator. ~dispass.el~ is an [[emacs][Emacs]] wrapper
for [[dispass][DisPass]].
| Status | Active |
| Language | Emacs Lisp |
| License | ISC |
* Why?
* Why was it written?
[[dispass][DisPass]] is written by a [[http://babab.nl][friend]] of mine and I really liked the idea
of it. But the interface he had for it was not to my liking, it
was not Emacs.
of it. But the interface he had for it was not to my liking, it was
not Emacs.
** Why the license?
Since [[dispass][DisPass]] uses the ISC license, I thought it would be polite
to use the same license.
* Features
* Who is it for?
- Copy passwords directly to the clipboard, no need for manual
selection and copying.
- Specify the length of the passphrase by using a numeric prefix
argument.
- Input completion for labels.
- Some label management (adding, removing).
Anyone who prefers to use emacs as a universal interface and also
likes to use [[dispass][DisPass]].
* Dependencies
* Data
- [[emacs][Emacs]] :: Probably version 24+, since that is what it's being
developed on.
- [[dispass][DisPass]] :: At least v0.1a8, best is a recent git version.
| Version | 0 (development only) |
| Language | Emacs Lisp |
| License | ISC |
* Download
** Features
There are download links for a ~tar.gz~ and a ~zip~ file of the latest
development version at the top of this page.
- Copy passwords directly to the clipboard, no need for manual
selection and copying.
- Specify the length of the passphrase by using a numeric prefix
argument.
- Input completion for labels.
- Some label management (adding, removing).
~dispass.el~ is both in the [[http://marmalade-repo.org/][Marmalade]] and the [[http://melpa.milkbox.net/][MELPA]] repo. The MELPA
version is a direct checkout of the latest development version and
the Marmalade version is an older, possibly more stable, version.
** Dependencies
* Install
- [[emacs][Emacs]] :: Probably version 24+, since that is what it's being
developed on.
- [[dispass][DisPass]] :: At least v0.1a8, best is a recent git version.
Once you have [[Download][downloaded]] ~dispass.el~ you have at least 2 choices for
installation.
* More...
** package.el
If you have Emacs v24+ or [[http://tromey.com/elpa/install.html][package.el]] and either Marmalade or MELPA
configured, you can just:
#+BEGIN_SRC emacs-lisp
(package-install "dispass")
#+END_SRC
** manual
Otherwise you have to [[Download][dowload]] it and then put it somewhere in your
=load-path=, or add that location to your =load-path=:
#+begin_src emacs-lisp
(add-to-list 'load-path "~/location/of/dispass.el")
#+end_src
After which you can either ~require~ the package in your Emacs init
file:
#+BEGIN_SRC emacs-lisp
(require 'dispass)
#+END_SRC
Or set-up some autoloads:
#+BEGIN_SRC emacs-lisp
(autoload 'dispass "dispass" nil t)
(autoload 'dispass-create "dispass" nil t)
(autoload 'dispass-list-labels "dispass" nil t)
#+END_SRC
* Usage
Once installed you can use ~dispass~ to (re)generate passphrases,
~dispass-create~ to generate a new one (it asks for confirmation on
the password) and ~dispass-list-labels~ to view a list of stored
labels and manage them a little.
For further instructions I would refer you to the [[readme][README]] and [[manual]].

2
site/projects/dlmenu.inc
View file

@ -2,3 +2,5 @@
- [[src][Browse Source]]
- [[tar_gz][Download tar.gz]]
- [[zip][Download zip]]
- [[readme][Read README]]
- [[manual][Read manual]]

49
site/projects/dvdroid.org
View file

@ -2,6 +2,8 @@
#+LINK: src http://code.ryuslash.org/cgit.cgi/dvdroid/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/dvdroid/snapshot/dvdroid-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/dvdroid/snapshot/dvdroid-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/dvdroid/about/
#+LINK: manual http://ryuslash.org/projects/dvdroid/manual/
#+STARTUP: showall
#+begin_html
@ -14,7 +16,7 @@
#+INCLUDE: "dlmenu.inc"
* About
* What does it do?
DVDroid is a DVD collection application for the Android operating
system.
@ -23,44 +25,33 @@
| Language | Java |
| License | GPLv3 |
* Why?
* Why was it written?
Very similar to [[file:eye-on-manga.org][Eye on Manga]], we keep forgetting which DVDs we have
and want when we're in the store.
* Features
* Who is it for?
- Keep a list of DVDs you have.
- Keep a list of DVDs you still need to watch.
- Keep a list of DVDs you want to buy.
Me, I did not take anyone else into consideration when writing
this, but if you find it useful feel free to use it and send me bug
reports and such.
* Dependencies
* Data
- Android :: Version 4.1 or higher.
| Version | 0 (development only) |
| Language | Java |
| License | GPLv3 |
* Download
** Features
There are download links for a ~tar.gz~ and a ~zip~ file of the latest
development version at the top of this page.
- Keep a list of DVDs you have.
- Keep a list of DVDs you still need to watch.
- Keep a list of DVDs you want to buy.
* Install
** Dependencies
In order to install it you need to have the Android Java
Development Kit installed, installing it is then a matter of
building/installing it like any other development package.
- Android :: Version 4.1 or higher.
* Usage
* More...
Start it up, you will have a list of the DVDs you own, which will
be empty. In the top right corner there should be a button to add
new titles to this list, here you can also specify if you have seen
it or if you still want to get it.
There is also a search button there that helps you look through
your collection.
To change the status of any title you can select it and edit and
delete buttons should show up at the top of your screen.
Use the menu button to switch "contexts", wish list, collection
and watch list.
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].

58
site/projects/eye-on-manga.org
View file

@ -2,6 +2,8 @@
#+LINK: src http://code.ryuslash.org/cgit.cgi/eye-on-manga/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/eye-on-manga/snapshot/eye-on-manga-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/eye-on-manga/snapshot/eye-on-manga-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/eye-on-manga/about/
#+LINK: manual http://ryuslash.org/projects/eye-on-manga/manual/
#+STARTUP: showall
#+begin_html
@ -14,58 +16,36 @@
#+INCLUDE: "dlmenu.inc"
* About
* What does it do?
~eye-on-manga~ is a manga collection management application for the
Nokia N900.
| Status | On-hold |
| Language | C |
| License | GPLv2 |
* Why?
* Why was it written?
I just keep forgetting which volumes of which manga I have.
* Features
* Who is it for?
- Create/maintain a list of manga.
- Keep track of which volumes have been acquired and read.
Anyone with a Nokia N900 who has more manga than they care to
remember.
* Requirements
* Data
- A Nokia N900, with Maemo, with fairly recent packages should be
fine.
| Version | 0 (development only) |
| Language | C |
| License | GPLv2 |
* Download
** Features
I'll upload a package as soon as I can.
- Create/maintain a list of manga.
- Keep track of which volumes have been acquired and read.
Until then, if you have the maemo development environment set-up
you can create your own. Use the ~FREMANTLE_ARMEL~ configuration in
scratchbox and create it with:
** Dependencies
#+BEGIN_EXAMPLE
$ dpkg-buildpkg -rfakeroot
#+END_EXAMPLE
- A Nokia N900 :: with Maemo, with fairly recent packages should be
fine.
* Install
* More...
Once you have aqcuired a package, get it to your phone and:
#+BEGIN_EXAMPLE
$ dpkg -I eye-on-manga-*.deb
#+END_EXAMPLE
* Usage
When you start it up you will see a list of your manga, showing the
name, # acquired and # total. To add a new manga entry open the menu
by pressing on the application's title and click "New Manga". You
will then be prompted for the name and total number of books for
this manga.
If you press on one of the manga's names you will see its detail
view. Here you can change the information previously entered and
select the manga you'v acquired (left column) and the manga you've
read (right column).
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].

129
site/projects/git-auto-commit-mode.org
View file

@ -2,6 +2,8 @@
#+LINK: src http://code.ryuslash.org/cgit.cgi/emacs/git-auto-commit-mode/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/emacs/git-auto-commit-mode/snapshot/git-auto-commit-mode-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/emacs/git-auto-commit-mode/snapshot/git-auto-commit-mode-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/emacs/git-auto-commit-mode/about/
#+LINK: manual http://ryulash.org/projects/git-auto-commit-mode/manual/
#+STARTUP: showall
#+begin_html
@ -14,118 +16,45 @@
#+INCLUDE: "dlmenu.inc"
* About
* What does it do?
~git-auto-commit-mode~ is a minor mode for GNU Emacs that, when
enabled, tries to commit changes to a file after every save. It can
enabled, tries to commit changes to a file after every save. It can
also try to push to the default upstream.
| Status | On-hold |
| Language | Emacs Lisp |
| Licennse | GPLv3 |
* Why was it written?
* Features
Some projects / files don't need a very fancy commit log or anything
and are typically only modified in small ways. Configuration files
are a good example, where most changes are just single lines added,
removed or changed. In these projects it can save some effort to
just automatically commit them after every change.
- Automatically commit changes to a file after each save.
* Who is it for?
- The commit message will contain the file name relative to the
repository root.
Anyone who makes a lot of small, separate, changes to a bunch if
git-tracked files and is tired of always having to go through the
=git add; git commit -m description= process.
- Optionally, automatically push commits to the default upstream.
* Data
* Requirements
| Version | 0 (development only) |
| Language | Emacs Lisp |
| License | GPLv3 |
- [[http://gnu.org/software/emacs][GNU Emacs]]
- [[http://git-scm.com][git]]
** Features
* Download
- Automatically commit changes to a file after each save.
- The commit message will contain the file name relative to the
repository root.
- Optionally, automatically push commits to the default upstream.
There are download links for a ~tar.gz~ and a ~zip~ file of the latest
development version at the top of this page.
** Dependencies
~git-auto-commit-mode~ is in the [[http://marmalade-repo.org/][Marmalade]] repo.
- [[http://gnu.org/software/emacs][GNU Emacs]] :: It is developed using Emacs 24, though I am not
averse to supporting older versions.
- [[http://git-scm.com][git]] :: I am not aware of any version restrictions.
* Install
* More...
Once you have [[Download][downloaded]] ~git-auto-commit-mode~ you have at least 2
choices for installation.
** package.el
If you have Emacs v24+ or [[http://tromey.com/elpa/install.html][package.el]] and Marmalade configured, you
can just:
#+BEGIN_SRC emacs-lisp
(package-install "git-auto-commit-mode")
#+END_SRC
** manual
Otherwise you have to [[Download][dowload]] it and then put it somewhere in your
=load-path=, or add that location to your =load-path=:
#+begin_src emacs-lisp
(add-to-list 'load-path "~/location/of/git-auto-commit-mode")
#+end_src
After which you can either ~require~ the package in your Emacs init
file:
#+BEGIN_SRC emacs-lisp
(require 'git-auto-commit-mode)
#+END_SRC
Or set-up some autoloads:
#+BEGIN_SRC emacs-lisp
(autoload 'git-auto-commit-mode "git-auto-commit-mode" nil t)
#+END_SRC
* Usage
There are a few ways this could be used:
** As file-local variable
This is the way I use it and I wanted to use it. Any file that you
would like to have automatically committed upon saving gets this
prop-line:
#+BEGIN_SRC emacs-lisp
;; -*- eval: (git-auto-commit-mode 1) -*-
#+END_SRC
Or, if you're in anything older than emacs 24:
#+BEGIN_SRC emacs-lisp
;; -*- mode: git-auto-commit -*-
#+END_SRC
** As a directory-local variable
Put the following in a ~.dir-locals.el~ file in any directory where
you want to enable ~git-auto-commit-mode~ for *all* files:
#+BEGIN_SRC emacs-lisp
((nil . ((git-auto-commit-mode . t))))
#+END_SRC
** As a hook
I doubt this will ever really be useful, but it is possible:
#+BEGIN_SRC emacs-lisp
(add-hook 'some-hook 'git-auto-commit-mode)
#+END_SRC
** Automatically push
If you wish to push your changes each time the file is saved you
should set =gac-automatically-push-p= to =t=. This is a buffer local
variable, so you will have to put it in your dir-local or
file-local variables. Alternatively, if you're sure you can also
set the default value to =t=, like so:
#+begin_src emacs-lisp
(setq-default gac-automatically-push-p t)
#+end_src
For further instructinos I would refer you to the [[readme][README]] and [[manual]].

69
site/projects/gitto.org
View file

@ -2,6 +2,8 @@
#+LINK: src http://code.ryuslash.org/cgit.cgi/gitto/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/gitto/snapshot/gitto-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/gitto/snapshot/gitto-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/gitto/about/
#+LINK: manual http://ryuslash.org/projects/gitto/manual/
#+STARTUP: showall
#+begin_html
@ -14,67 +16,40 @@
#+INCLUDE: "dlmenu.inc"
* About
* What does it do?
~gitto~ is a utility written in [[http://www.gnu.org/software/guile/][Guile scheme]] to help me keep track of
the status of my git repositories.
~gitto~ is a utility written in [[http://www.gnu.org/software/guile/][Guile scheme]] to help keep track of the
status of git repositories.
| Status | On-hold |
| Language | Scheme (Guile) |
| License | GPLv3 |
* Features
* Why was it written?
- Show a list of how many commits to pull or push and whether or
not the working directory of that repository is dirty.
Remembering the status of all your git repositories can be quite a
task, this project tries to alleviate some of the pain.
* Requirements
* Who is it for?
- [[http://www.gnu.org/software/guile/][Guile]] v2.0.x
- [[http://git-scm.com][git]]
Anyone with lots and lots of git repositories.
* Download
* Data
There are download links for a ~tar.gz~ and a ~zip~ file of the latest
development version at the top of this page.
| Version | 0 (development only) |
| Language | scheme (guile) |
| Licence | GPLv3 |
* Install
** Features
To install this should be enough:
- Show a list of how many commits to pull or push and whether or
not the working directory of that repository is dirty.
#+BEGIN_EXAMPLE
$ make && make install
#+END_EXAMPLE
** Dependencies
* Usage
- [[http://www.gnu.org/software/guile/][Guile]] :: v2.0.x or newer.
- [[http://git-scm.com][git]] :: I am unaware of any version constraints relating to git.
** Register repositories
* More...
First you'll have to register some repositories:
#+begin_example
$ gitto -r ~/projects/project1
$ gitto -r ~/projects/project2
$ gitto -r ~/projects/project3
#+end_example
** List status
Once you have registered some repositories you can list them by
calling ~gitto~ without any arguments:
#+begin_example
$ gitto
project1: 0 to push, 0 to pull and is dirty
project2: 5 to push, 2 to pull and is not dirty
project3: 0 to push, 1 to pull and is not dirty
#+end_example
** Remove repositories
When you're fed up with a repository and no longer care about its
status, you can remove it with the =-R= switch:
#+begin_src shell-script
$ gitto -R ~/projects/project1
#+end_src
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].

30
site/projects/markam.org
View file

@ -1,16 +1,18 @@
#+TITLE: markam
#+TITLE: Markam
#+LINK: src http://code.ryuslash.org/cgit.cgi/markam/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/markam/snapshot/markam-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/markam/snapshot/markam-master.zip
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/markam/snapshot/markam-0.1.0.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/markam/snapshot/markam-0.1.0.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/markam/about/
#+LINK: manual http://ryuslash.org/projects/markam/manual/
#+STARTUP: showall
#+begin_html
<script src="/keyjs.js" type="text/javascript"></script>
<script type="text/javascript">
keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
"h": [ "keyjs_goto", "http://ryuslash.org" ] });
</script>
#+end_html
<script src="/keyjs.js" type="text/javascript"></script>
<script type="text/javascript">
keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
"h": [ "keyjs_goto", "http://ryuslash.org" ] });
</script>
#+end_html
#+INCLUDE: "dlmenu.inc"
@ -31,9 +33,9 @@
* Data
| Version | 0 (development only) |
| Language | scheme (chicken) |
| License | GPLv3 |
| Version | 0.1.0 |
| Language | scheme (chicken) |
| License | GPLv3 |
** Features
@ -48,3 +50,7 @@
** Dependencies
- [[http://call-by.cc][CHICKEN scheme]] :: Any version might do, the latest surely.
* More...
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].

61
site/projects/mode-icons.org Normal file
View file

@ -0,0 +1,61 @@
#+TITLE: mode-icons
#+LINK: src http://code.ryuslash.org/cgit.cgi/emacs/mode-icons/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/emacs/mode-icons/snapshot/mode-icons-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/emacs/mode-icons/snapshot/mode-icons-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/emacs/mode-icons/about/
#+LINK: manual http://ryuslash.org/projects/mode-icons/manual/
#+STARTUP: showall
#+begin_html
<script src="/keyjs.js" type="text/javascript"></script>
<script type="text/javascript">
keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
"h": [ "keyjs_goto", "http://ryuslash.org" ] });
</script>
#+end_html
#+INCLUDE: "dlmenu.inc"
* About
Mode-icons is a package for emacs that, when enabled, replaces
certain major mode names with icons of their logo. This reduces
the size of their position in the mode-line.
| Language | |
| License | GPLv3 |
* Why was it written?
Because I sometimes have a great deal of trouble with the amount of
room my mode-line takes up and also because I like some graphical
elements, when they're useful.
* Who is it for?
Anyone who likes to have a more visual que of their major mode.
* Data
| Version | 0 (development only) |
| Language | Emacs Lisp |
| License | GPLv3 |
** Features
- Show icons for major modes:
- Common Lisp
- Emacs Lisp
- HTML
- PHP
- Python
- Scheme
** Dependencies
- [[http://gnu.org/software/emacs/][GNU Emacs]] :: Probably version 24 or higher, since that is what
it has been developed with.
* More...
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].

50
site/projects/ogi.org Normal file
View file

@ -0,0 +1,50 @@
#+TITLE: ogi
#+LINK: src http://code.ryuslash.org/cgit.cgi/emacs/ogi/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/emacs/ogi/snapshot/ogi-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/emacs/ogi/snapshot/ogi-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/emacs/ogi/about/
#+LINK: manual http://ryuslash.org/projects/ogi/manual/
#+STARTUP: showall
#+begin_html
<script src="/keyjs.js" type="text/javascript"></script>
<script type="text/javascript">
keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
"h": [ "keyjs_goto", "http://ryuslash.org" ] });
</script>
#+end_html
#+INCLUDE: "dlmenu.inc"
* What does it do?
Ogi is Github issues in org-mode
* Why was it written?
Because I dislike web interfaces, am interested in using APIs and
think org-mode would be a perfect way to represent the issues found
there.
* Who is it for?
Anyone who likes org-mode and uses github.
* Data
| Version | 0 (development only) |
| Language | Emacs Lisp |
| License | GPLv3 |
** Features
- Download issues and make org tasks from them.
** Dependencies
- [[http://gnu.org/software/emacs][GNU Emacs]] :: Version 24 or newer probably, since that is what
it's being developed with.
* More...
For further instructions I would refer you to the [[readme][README]] and [[manual]].

36
site/projects/yoshi-theme.org
View file

@ -2,44 +2,48 @@
#+LINK: src http://code.ryuslash.org/cgit.cgi/emacs/yoshi-theme/
#+LINK: tar_gz http://code.ryuslash.org/cgit.cgi/emacs/yoshi-theme/snapshot/yoshi-theme-master.tar.gz
#+LINK: zip http://code.ryuslash.org/cgit.cgi/emacs/yoshi-theme/snapshot/yoshi-theme-master.zip
#+LINK: readme http://code.ryuslash.org/cgit.cgi/emacs/yoshi-theme/about/
#+LINK: manual http://ryuslash.org/projects/yoshi-theme/manual/
#+STARTUP: showall
#+INCLUDE: "jskeys.inc"
#+INCLUDE: "dlmenu.inc"
* About
* What does it do?
~yoshi-theme~ is a GNU Emacs theme named after my cat. It is only
named after him because I couldn't think of another name and
~new-theme~ just wasn't cutting it.
~new-theme~ just wasn't cutting it. [[http://ryuslash.org/mediagoblin/mediagoblin.fcgi/u/ryuslash/m/img-20121103-121638/][He]] doesn't actually look anything
like this.
| Status | Active |
| Language | Emacs Lisp |
| License | GPLv3 |
* Why?
* Why was it written?
Since I wasn't 100% happy with the color themes I found, though
there are some very good ones, I thought I'd try my own.
* Features
* Who is it for?
- Many faces for many functions
- Not too high contrast (no #ffffff on #000000)
Anyone who likes it.
* Dependencies
* Data
- GNU Emacs 24
| Version | 0 (development only) |
| Language | Emacs Lisp |
| License | GPLv3 |
* Download
** Features
There are download links at the top of the page.
- Not too high contrast (no #ffffff on #000000)
- What could be features of a theme? The faces supported?
* Install
** Dependencies
Make sure ~yoshi-theme~ is somewhere in your ~custom-theme-load-path~
and then just ~load-theme~ it.
- [[http://gnu.org/software/emacs/][GNU Emacs 24]] :: It uses the theming system introduced by Emacs
v24.
* Usage
* More...
Just look at your screen when it's activated.
For further instructions I would refer you to the [[readme][README]] and [[manual][manual]].