Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Introduction, thanks, and a small patch
Date: Sun, 16 Aug 2009 14:38:31 -0700	[thread overview]
Message-ID: <1250457809-sup-6784@masanjin.net> (raw)
In-Reply-To: <20090815041446.GA1249@yoom.home.cworth.org>

Reformatted excerpts from Carl Worth's message of 2009-08-14:
> Hi. My name's Carl, and I've uh, been collecting email for 12 years.

Hi Carl! Welcome.

> 1. Most text is white-on-white (invisible) if the default terminal
>    background color is white. I would suggest that the default
>    background color be changed from "default" to "black" to avoid
>    this trap.

Complaining about the colors already? You're fitting right in around
here.

We recently changed it from black to default in order to make it work
for people with transparent terminals. Since there's clearly not a
setting that works for everyone, I think the best solution is your
suggestion in a later email: provide a few reasonable color schemes
directly in sup-sync.

> I've attached a patch to fix this second issue, (a single-character
> change).

Great, thanks. The patch looks good but I think you left a debugging
puts call in there. If you want to resubmit,  I will apply this.

> I love the NewUserGuide, but I've needed a ReferenceManual for various
> issues already, (configuring colors, configuring SMTP, understanding
> the sources.yaml file well enough to be able to re-process mail that
> was mis-labelled the first time, etc.).

Agree. This would be very valuable and is currently a sore spot, IMO.

> One potential issue is that I don't see any explicit license terms on
> the wiki. Can I assume that any text on the wiki is suitable for
> putting into a document to be contributed to and distributed with sup?

I think it's fair to assume that anyone contributing to a wiki for an
open-source product knows what they're getting into. So, yes.

Of course, if anyone objects to their wiki content being distributed as
part of Sup (which is currently distributed under GPL v2), please speak
now!

> I really like the ideas William has posted on his blog about
> separating the interface from the guts of sup, (to make the new STS).
> I'd be happy to help with that as well if possible.

Although it's been over a year of vaporware promises, this is slowly
happening. I have a protocol defined and a simple server written. Recent
work on replacing Ferret with Xapian has actually been helpful in terms
of moving us away from Ferretisms. Expect something "soon".

> NoMethodError from thread: main
> undefined method `to_indexable_s' for nil:NilClass

This should now be fixed in git master; see my previous email in this
thread. (You will have to manually edit your sent.mbox a bit.)
-- 
William <wmorgan-sup at masanjin.net>


      parent reply	other threads:[~2009-08-16 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090815041446.GA1249@yoom.home.cworth.org>
2009-08-15 10:18 ` Igor Brkic
2009-08-15 14:35   ` Carl Worth
2009-08-16 21:22   ` William Morgan
2009-08-16 23:18     ` Igor Brkic
2009-08-15 11:03 ` Marc Weber
2009-08-15 14:41   ` Carl Worth
2009-08-16 21:38 ` William Morgan [this message]

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=1250457809-sup-6784@masanjin.net \
    --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