D
Don March
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/
* Documentation: http://relisp.rubyforge.org/
* 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/
* Documentation: http://relisp.rubyforge.org/