Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: itaylor@uark.edu (Ian Taylor)
Subject: [sup-talk] forward is broken in svn
Date: Sat, 11 Aug 2007 17:35:22 -0400	[thread overview]
Message-ID: <1186867471-sup-8895@zap> (raw)
In-Reply-To: <1186863923-sup-9365@south>

Excerpts from William Morgan's message of Sat Aug 11 16:26:22 -0400 2007:
> Excerpts from Ian Taylor's message of Sat Aug 11 12:34:38 -0700 2007:
> > thread-view-mode.rb:136 'compose' undefined method 'edit'
> 
> This was fixed in r519 (2007-08-06 21:16:53 -0700).
> 

I'm sorry, but it doesn't appear to be fixed here. Just in case, here is
the whole exection:

The problem was: 'undefined method `edit' for #<Redwood::ForwardMode:0x2aaaab5044b8>' (error type NoMethodError)
A backtrace follows:
/usr/lib64/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:337:in `forward': undefined method `edit' for #<Redwood::ForwardMode:0x2aaaab5044b8> (NoMethodError)
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.9/lib/sup/mode.rb:52:in `send'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.9/lib/sup/mode.rb:52:in `handle_input'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.9/lib/sup/buffer.rb:191:in `handle_input'
        from /usr/lib64/ruby/gems/1.8/gems/sup-0.9/bin/sup:186
        from /usr/bin/sup:16:in `load'
        from /usr/bin/sup:16


Also, I think in the Rakefile, doing require 'lib/sup.rb' doesn't work
as imagined. The requires within lib/sup.rb require 'sup/*' and so try
to load from the local gem repository. I looked at the hoe project's
Rakefile and I see them doing a trick which probably is what we want:

require 'rubygems'
require 'hoe'
$:.unshift 'lib'
require 'sup'



Also, I think the change of the VERSION to 0 for development is a
problem. I got this after installing dev version of sup (after removing
the old ones):
/usr/lib64/ruby/site_ruby/1.8/rubygems.rb:304:in `report_activate_error': RubyGem version error: sup(0 not > 0) (Gem::LoadError)
        from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:238:in `activate'
        from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:76:in `active_gem_with_options'
        from /usr/lib64/ruby/site_ruby/1.8/rubygems.rb:50:in `gem'
        from /usr/bin/sup:15

Maybe some really high version number would be good since gems does a
comparison for choosing which version to use?

-- 
Ian Taylor, Technical Assistant
Computer Science Computer Engineering
http://www.csce.uark.edu itaylor at uark.edu
University of Arkansas



  reply	other threads:[~2007-08-11 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11 19:34 Ian Taylor
2007-08-11 20:26 ` William Morgan
2007-08-11 21:35   ` Ian Taylor [this message]
2007-08-12 22:21     ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1186867471-sup-8895@zap \
    --to=itaylor@uark.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox