# ANN: Relisp 1.0.0 (rubyfied emacs lisp)

**URL:** <https://www.ruby-forum.com/t/ann-relisp-1-0-0-rubyfied-emacs-lisp/167238>\
**Category:** Ruby\
**Created:** [May 5, 2009, 8:47pm UTC](https://www.ruby-forum.com/t/ann-relisp-1-0-0-rubyfied-emacs-lisp/167238 "2009-05-05T20:47:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmcclean](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/91b2a8/32.png) [@dmcclean](https://www.ruby-forum.com/u/dmcclean)\
**Post date:** [May 5, 2009, 8:47pm UTC](https://www.ruby-forum.com/t/ann-relisp-1-0-0-rubyfied-emacs-lisp/167238/1 "2009-05-05T20:47:46Z")

</div>

This purpose of Relisp is to:

- call Ruby from Emacs
- call Elisp from Ruby
- manipulate Emacs without using Elisp to some extent (Ruby wrappers  
around some Elisp functions and objects)
- reduce the number of blog entries titled “Is Ruby an acceptable Lisp?”  
and flame wars under the title “ruby vs. lisp vs. scheme vs. haskell vs.  
…”

Wouldn’t it be nice to have a Ruby interface to things like buffers,  
windows and frames? Yes. Yes it would:

new\_buffer = Relisp::Buffer.new(“name\_of\_new\_buffer”)  
new\_buffer.switch\_to  
Relisp::Frame.new({:width =\> 80, :height =\> 20, :name =\> “ruby  
frame”})

For more examples and details, see

- Original blog post:  
[http://ohspite.net/2009/01/30/relisp-rubyfied-emacs-lisp/](http://ohspite.net/2009/01/30/relisp-rubyfied-emacs-lisp/)
- Documentation: [http://relisp.rubyforge.org/](http://relisp.rubyforge.org/)