* [sup-talk] fun stuff in git next
@ 2010-01-01 21:48 William Morgan
2010-01-01 22:05 ` Edward Z. Yang
2010-01-02 4:27 ` Richard Sandilands
0 siblings, 2 replies; 4+ messages in thread
From: William Morgan @ 2010-01-01 21:48 UTC (permalink / raw)
To: Sup-talk mailing list
Thanks to inestimable Rich Lane, we have two particularly exciting
things happening now in git next:
1. Autosave. No more hitting '$' in thread-view-mode. (Actually hitting
'$' will now send you to the bottom of the buffer.)
2. Ruby 1.9 support. There are a few warts here and there, but it works!
You will need either Xapian or the special compiled-for-1.9 Ferret gem
that's been floating around for this.
Those of you following git master will also notice a bunch of new
features that have been merged down from next, in preparation for the
0.10 release.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] fun stuff in git next
2010-01-01 21:48 [sup-talk] fun stuff in git next William Morgan
@ 2010-01-01 22:05 ` Edward Z. Yang
2010-01-02 4:27 ` Richard Sandilands
1 sibling, 0 replies; 4+ messages in thread
From: Edward Z. Yang @ 2010-01-01 22:05 UTC (permalink / raw)
To: sup-talk
Excerpts from William Morgan's message of Fri Jan 01 16:48:15 -0500 2010:
> Thanks to inestimable Rich Lane, we have two particularly exciting
> things happening now in git next:
Happy news! I'll upgrade shortly.
Cheers,
Edward
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] fun stuff in git next
2010-01-01 21:48 [sup-talk] fun stuff in git next William Morgan
2010-01-01 22:05 ` Edward Z. Yang
@ 2010-01-02 4:27 ` Richard Sandilands
2010-01-02 4:36 ` Rich Lane
1 sibling, 1 reply; 4+ messages in thread
From: Richard Sandilands @ 2010-01-02 4:27 UTC (permalink / raw)
To: Sup-talk mailing list
I'm getting the following error after pulling next:
/Library/Ruby/Gems/1.8/gems/sup-999/lib/sup/util.rb:520:in `send':
undefined method `stop_sync_worker' for
#<Redwood::XapianIndex:0x101fd15b8> (NoMethodError)
from /Library/Ruby/Gems/1.8/gems/sup-999/lib/sup/util.rb:520:in
`method_missing'
from /Users/richard/src/mainline/bin/sup:350
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] fun stuff in git next
2010-01-02 4:27 ` Richard Sandilands
@ 2010-01-02 4:36 ` Rich Lane
0 siblings, 0 replies; 4+ messages in thread
From: Rich Lane @ 2010-01-02 4:36 UTC (permalink / raw)
To: Richard Sandilands; +Cc: Sup-talk mailing list
Excerpts from Richard Sandilands's message of Fri Jan 01 23:27:25 -0500 2010:
> I'm getting the following error after pulling next:
>
> /Library/Ruby/Gems/1.8/gems/sup-999/lib/sup/util.rb:520:in `send':
> undefined method `stop_sync_worker' for
> #<Redwood::XapianIndex:0x101fd15b8> (NoMethodError)
> from /Library/Ruby/Gems/1.8/gems/sup-999/lib/sup/util.rb:520:in
> `method_missing'
> from /Users/richard/src/mainline/bin/sup:350
It looks like you're using the lib/ directory of an older installed gem.
Make sure you have -I./lib (or the correct path to your sup lib dir) in
your ruby arguments when running your git working copy.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-01-02 4:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-01-01 21:48 [sup-talk] fun stuff in git next William Morgan
2010-01-01 22:05 ` Edward Z. Yang
2010-01-02 4:27 ` Richard Sandilands
2010-01-02 4:36 ` Rich Lane
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox