From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] backspace and delete keys
Date: Wed, 09 Jan 2008 11:02:47 -0800 [thread overview]
Message-ID: <1199905135-sup-2008@south> (raw)
In-Reply-To: <1199813518-sup-5839@clarabella.clarabella>
Excerpts from Giorgio Lando's message of Tue Jan 08 09:32:54 -0800 2008:
> The version of gem is 0.9.4. May be I should clarify the scenario
> where the exception happened. I had sup-0.3 in the standard gems
> system directory ans sup-git in a folder in my home directory. I cd to
> the sup-git folder and did ruby -Ilib -w sup.
That was my setup too. Weird that I no longer seem to have this problem.
I've committed the following patch to next, which explicitly versions
bin/sup and lib/sup.rb and compares the two upon startup. Hopefully this
should detect this type of situation. For those of you who like to play
with sup via "rake gem", gems built from your checkout will have version
999. (This was a suggestion Ian Taylor made a long time ago.)
diff --git a/Rakefile b/Rakefile
index 1932f62..33e9883 100644
--- a/Rakefile
+++ b/Rakefile
@@ -7,7 +7,12 @@ class Hoe
def extra_deps; @extra_deps.reject { |x| Array(x).first == "hoe" } end
end # thanks to "Mike H"
-Hoe.new('sup', Redwood::VERSION) do |p|
+## allow people who use development versions by running "rake gem"
+## and installing the resulting gem it to be able to do this. (gem
+## versions must be in dotted-digit notation only).
+version = Redwood::VERSION == "git" ? 999 : Redwood::VERSION
+
+Hoe.new('sup', version) do |p|
p.rubyforge_name = 'sup'
p.author = "William Morgan"
p.summary = 'A console-based email client with the best features of GMail, mutt, and emacs. Features full text search, labels, tagged operations, multiple buffers, recent contacts, and more.'
diff --git a/bin/sup b/bin/sup
index 0f48ab4..7314227 100644
--- a/bin/sup
+++ b/bin/sup
@@ -7,6 +7,20 @@ require 'fileutils'
require 'trollop'
require "sup"
+BIN_VERSION = "git"
+
+unless Redwood::VERSION == BIN_VERSION
+ $stderr.puts <<EOS
+
+Error: version mismatch!
+The sup executable is at version #{BIN_VERSION.inspect}.
+The sup libraries are at version #{Redwood::VERSION.inspect}.
+
+Is your development environment conflicting with rubygems?
+EOS
+ exit(-1)
+end
+
$exceptions = []
$opts = Trollop::options do
version "sup v#{Redwood::VERSION}"
diff --git a/lib/sup.rb b/lib/sup.rb
index 5bb27ba..d34dec3 100644
--- a/lib/sup.rb
+++ b/lib/sup.rb
@@ -32,7 +32,7 @@ class Module
end
module Redwood
- VERSION = "0.3"
+ VERSION = "git"
BASE_DIR = ENV["SUP_BASE"] || File.join(ENV["HOME"], ".sup")
CONFIG_FN = File.join(BASE_DIR, "config.yaml")
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-09 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 22:59 Giorgio Lando
2008-01-08 0:12 ` William Morgan
2008-01-08 0:22 ` Giorgio Lando
2008-01-08 3:24 ` Giorgio Lando
2008-01-08 6:39 ` William Morgan
2008-01-08 11:31 ` Giorgio Lando
2008-01-08 15:34 ` William Morgan
2008-01-08 16:21 ` Giorgio Lando
2008-01-08 16:40 ` William Morgan
2008-01-08 17:23 ` William Morgan
2008-01-08 17:32 ` Giorgio Lando
2008-01-09 19:02 ` William Morgan [this message]
2008-01-10 7:05 ` Ingmar Vanhassel
2008-01-10 16:22 ` William Morgan
2008-01-10 17:23 ` Ingmar Vanhassel
2008-01-10 17:45 ` William Morgan
2008-01-08 1:34 ` Nicolas Pouillard
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=1199905135-sup-2008@south \
--to=wmorgan-sup@masanjin.net \
/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