Nabble - SUP Talk

Re: sup finds exception and exits

2009-12-07T11:01:12Z

Susana Core, 2009-12-07 17:45:
> Below are the error messages.

At glance it doesn't look like the error has anything to do with
deleted mail. But I could just be terribly wrong. :)

Are you able to sup-dump your tags and reindex? That might help you.

For instructions on how to do that, see sup FAQ
<http://sup.rubyforge.org/FAQ.txt> questions "How do I back up my
index?" and "How do I rebuild the index completely?". You might want
to backup your ~/.sup/ferret just in case you would like to go back.

> I should clarify that while I don't delete email from my mailbox the
> policy for the mail account is that after three months messages are
> deleted.

Uough! That policy really sucks. :(

If I had to work with something like that I'd prolly mirror incoming
mails to my own mail archive (using fetchmail, offlineimap or similar)

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: sup finds exception and exits

2009-12-07T10:21:45Z

Excerpts from Susana Core's message of Mon Dec 07 07:45:02 -0800 2009:
> I have been using sup for about six months and today it started
> having fatal problems. I'll appreciate any suggestions.
>
> Below are the error messages. I should clarify that while I don't
> delete email from my mailbox the policy for the mail account
> is that after three months messages are deleted. This might be
> relevant since sup exits while polling for new messages in a thread
> which contains at least one message older than 3 months, i.e.
> while tryint to load a message which has been deleted.

My experience is that sup has dealt with this gracefully (message is
deleted from the actual source, but not from the index) and displays a
message about it "not playing nice with others", but it still should be
avoided if possible.

Are you deleting the message from the index as well or just from the
source?

Cheers,
jonathan

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

signature.asc (204 bytes) Download Attachment

sup finds exception and exits

2009-12-07T07:45:02Z

I have been using sup for about six months and today it started
having fatal problems. I'll appreciate any suggestions.

Below are the error messages. I should clarify that while I don't
delete email from my mailbox the policy for the mail account
is that after three months messages are deleted. This might be
relevant since sup exits while polling for new messages in a thread
which contains at least one message older than 3 months, i.e.
while tryint to load a message which has been deleted.

Thanks,

Susana.

____________________error messages_______________________________

Polling for new messages... (eval):1: warning: instance variable @source_marked_read not initialized
[Mon Dec 07 09:25:33 -0600 2009] stopped cursing
[Mon Dec 07 09:25:33 -0600 2009] oh crap, an exception
[Mon Dec 07 09:25:33 -0600 2009] unlocking /home/susana/.sup/lock...
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. If you don't mind, please send the
contents of ~/.sup/exception-log.txt and a brief report of the
circumstances to sup-talk at rubyforge dot orgs so that I might
address this problem. Thank you!

Sincerely,
William
----------------------------------------------------------------
--- NoMethodError from thread: poll after loading inbox
undefined method `to_indexable_s' for nil:NilClass
./lib/sup/index.rb:244:in `sync_message'
./lib/sup/util.rb:505:in `send'
./lib/sup/util.rb:505:in `method_missing'
./lib/sup/poll.rb:162:in `add_messages_from'
./lib/sup/source.rb:100:in `each'
./lib/sup/util.rb:544:in `send'
./lib/sup/util.rb:544:in `__pass'
./lib/sup/util.rb:531:in `method_missing'
./lib/sup/poll.rb:141:in `add_messages_from'
./lib/sup/poll.rb:98:in `do_poll'
./lib/sup/poll.rb:86:in `each'
./lib/sup/poll.rb:86:in `do_poll'
./lib/sup/poll.rb:85:in `synchronize'
./lib/sup/poll.rb:85:in `do_poll'
./lib/sup/util.rb:505:in `send'
./lib/sup/util.rb:505:in `method_missing'
./lib/sup/modes/poll-mode.rb:17:in `poll'
./lib/sup/poll.rb:53:in `poll'
./lib/sup/util.rb:505:in `send'
./lib/sup/util.rb:505:in `method_missing'
bin/sup:206
./lib/sup.rb:71:in `reporting_thread'
./lib/sup.rb:69:in `initialize'
./lib/sup.rb:69:in `new'
./lib/sup.rb:69:in `reporting_thread'
bin/sup:206
./lib/sup/modes/thread-index-mode.rb:663:in `call'
./lib/sup/modes/thread-index-mode.rb:663:in `__unprotected_load_threads'
./lib/sup/modes/thread-index-mode.rb:605:in `call'
./lib/sup/modes/thread-index-mode.rb:605:in `load_n_threads_background'
./lib/sup.rb:71:in `reporting_thread'
./lib/sup.rb:69:in `initialize'
./lib/sup.rb:69:in `new'
./lib/sup.rb:69:in `reporting_thread'
./lib/sup/modes/thread-index-mode.rb:603:in `load_n_threads_background'
./lib/sup/modes/thread-index-mode.rb:673:in `__unprotected_load_threads'
(eval):12:in `load_threads'
bin/sup:206

____________________ end of error messages_________________________

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

sup-add won't work.

2009-11-29T05:39:56Z

Here, I have a somewhat clean install of sup (gems + next branch), and
here's what I get at the end of sup-config :

Ok, trying to run "bin/sup-add mbox:/home/shivan/.gmail.mbox"...
/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require': no such file to load -- sup (LoadError)
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in `require'
from bin/sup-add:7

Something changed?

--
Guillaume
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: browser filter / attachment ideas

2009-11-26T04:13:18Z

Gaute Hope, 2009-11-25 19:27:
> And sup doesn't understand attachment names with inline encoding:
> i.e.: =?ISO-8859-1?Q?framside_sm=E5_stader_STORE_VYER.jpg?=
> which should be displayed as: framside_små_stader_STORE_VYER.jpg

I think I have this fixed, but haven committed/pushed it. Shame on
me. Should try to find time to do that...

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

browser filter / attachment ideas

2009-11-25T09:27:53Z

Greetings,

Is there already a way to put a filter on the file browser?
i.e: exclude anything that start with a '.' ? is there a hook for this?

I know there is a way of saving all attachments to a folder, but is
there a way to save a single attachment to a folder, now when I want to
save it I have to remove the file name to get tab-completion, and then
type the file name again when I want to save it.

And sup doesn't understand attachment names with inline encoding:
i.e.: =?ISO-8859-1?Q?framside_sm=E5_stader_STORE_VYER.jpg?=
which should be displayed as: framside_små_stader_STORE_VYER.jpg

(see issue 24)

- gaute
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Sup-sync exception

2009-11-23T15:33:06Z

Excerpts from Ned Ludd's message of Fri Nov 20 10:50:47 -0500 2009:

> There was a message about this a week or so ago. Did anyone ever find a fix?
>
> When I run "sup-sync", regardless or the source (I tried IMAP and
> Maildir), I get this error:
>
> $ sup-sync
> Scanning maildir:/home/nedludd/.mail/INBOX...
> /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/source.rb:88:in `done?':
> undefined method `>=' for true:TrueClass (NoMethodError)
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:560:in `__pass'
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:547:in
> `method_missing'
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/poll.rb:137:in
> `each_message_from'
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:520:in
> `method_missing'
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:146:in `block
> in <top (required)>'
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:141:in `each'
> from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:141:in `<top
> (required)>'
> from /usr/bin/supbin/sup-sync:19:in `load'
> from /usr/bin/supbin/sup-sync:19:in `<main>'
>
>
> [I'm on Arch with sup 0.9 and Ruby 1.9.1]

Is there a cur_offset key for every source in sources.yaml? If not (or
if it is nil/blank) see if setting cur_offset to 0 fixes it.
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Sup-sync exception

2009-11-20T21:18:28Z

You can solve this particular problem (I have), but then it uncovers
quite a few other probems with sup and Ruby 1.9. As the maintainer of
the sup package in the AUR, I pretty much recommend using ruby 1.8
until the dev team can beat sup into working.

Sorry,

-AT

On Fri, Nov 20, 2009 at 10:50 AM, Ned Ludd <edwardludd@...> wrote:

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Sup-sync exception

2009-11-20T07:50:47Z

There was a message about this a week or so ago. Did anyone ever find a fix?

When I run "sup-sync", regardless or the source (I tried IMAP and
Maildir), I get this error:

$ sup-sync
Scanning maildir:/home/nedludd/.mail/INBOX...
/usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/source.rb:88:in `done?':
undefined method `>=' for true:TrueClass (NoMethodError)
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:560:in `__pass'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:547:in
`method_missing'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/poll.rb:137:in
`each_message_from'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/lib/sup/util.rb:520:in
`method_missing'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:146:in `block
in <top (required)>'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:141:in `each'
from /usr/lib/ruby/gems/1.9.1/gems/sup-0.9/bin/sup-sync:141:in `<top
(required)>'
from /usr/bin/supbin/sup-sync:19:in `load'
from /usr/bin/supbin/sup-sync:19:in `<main>'

[I'm on Arch with sup 0.9 and Ruby 1.9.1]

-----
Ned Ludd
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Problems with undo archive and thread focus

2009-11-19T20:51:22Z

Excerpts from Andrew Pimlott's message of Thu Nov 12 12:30:01 -0500 2009:

> Excerpts from Matthias Guedemann's message of Thu Nov 05 00:27:25 -0800 2009:
> > One is, if you hit 'a' in thread view mode, the thread is archived but undo does
> > not work. If you go back to index view and hit 'u' the just archived thread does
> > not appear, but the one before.
>
> I was annoyed by this too and found that undo is minimally implemented.
> I added undo to thread view, at least for the cases that I care about or
> were easy. I have to say I was discouraged that this was necessary: the
> code to archive a thread should all be in one place, and the undo
> record should be created there. There's a lot of code duplication, and
> I can't tell if it's because the model and view are too coupled, or
> because nobody has bothered to factor it out.
>
> The patch is appended. (This is the first time I've done this with git.)

Branch thread-view-mode-undo, merged to master at
git://github.com/rlane/sup
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Bug report, importing emails into sup

2009-11-18T04:38:25Z

Dhaval Giani, 2009-11-17 21:04:
> Failure occured when trying to import mails from mbox after setting up
> using sup-config whicch failed and i tried to run sup after that

The trace is from sup, but you say it happened "when trying to import
mails", which is usually done with sup-sync. What was your procedure?
How did sup-config fail?

btw, we now have a brand new tracker <http://masanjin.net/sup-bugs/>

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Bug report, importing emails into sup

2009-11-17T11:04:27Z

Hi,

Attached an exception log.

Failure occured when trying to import mails from mbox after setting up
using sup-config whicch failed and i tried to run sup after that

[dhaval@gondor sup]$ sup --version
sup v0.9
[dhaval@gondor sup]$

Thanks,
Dhaval
--

Joan Crawford - "I, Joan Crawford, I believe in the dollar.
Everything I earn, I spend." -
http://www.brainyquote.com/quotes/authors/j/joan_crawford.html

--- NoMethodError from thread: poll after loading inbox
undefined method `downcase' for nil:NilClass
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:502:in `message_to_chunks'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:239:in `load_from_source!'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/message.rb:335:in `build_from_source'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:145:in `each_message_from'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/source.rb:104:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:560:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:560:in `__pass'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:547:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:139:in `each_message_from'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:93:in `do_poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:81:in `each'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:81:in `do_poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:80:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:80:in `do_poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/poll-mode.rb:15:in `poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/poll.rb:48:in `poll'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `send'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/util.rb:520:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/bin/sup:196
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:77:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `initialize'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `new'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/bin/sup:196
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:669:in `call'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:669:in `__unprotected_load_threads'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:610:in `call'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:610:in `load_n_threads_background'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:77:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `initialize'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `new'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup.rb:75:in `reporting_thread'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:608:in `load_n_threads_background'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:679:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/usr/lib/ruby/gems/1.8/gems/sup-0.9/bin/sup:196
/usr/bin/sup:19:in `load'
/usr/bin/sup:19

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Problems with undo archive and thread focus

2009-11-16T01:42:18Z

Hi Andrew,

> The patch is appended. (This is the first time I've done this with git.)

thanks, works perfectly.

> That's the next most annying thing for me. Hope to get a chance to work
> on it.

I had a look at the code and it should not be too hard, basically when a reply
buffer is spawned (e.g. thread-view-mode line 168), a hook to call set_sursor_pos
0 (as ThreadViewMode is a subclass of LineCursorMode) after successful sending of
the reply should do the job.

But unfortunately I don't know too much about the inner workings of sup (can the
HookManager be used for this? or should the hook be supplied as attribute to the
reply-buffer?), or even Ruby, to do it at the moment.

best regards

Matthias

--
__________________________________________________________
___ __ __
Dipl. Inf. Matthias Guedemann / __\/ _\ /__\
Computer Systems in Engineering / / \ \ /_\
Otto-von-Guericke Universitaet Magdeburg / /___ _\ \//__
Tel.: 0391 / 67-19359 \____/ \__/\__/
__________________________________________________________
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Sup not working anymore after abrupt reboot

2009-11-14T05:22:50Z

Excerpts from Tero Tilus's message of vie nov 13 12:10:17 +0100 2009:

> Carlos Garcia Campos, 2009-11-13 11:11:
> > I don't know whether my ferret index is corrupt, this is the exception I
> > get:
> >
> > ----------------------------------------------------------------
> > Error occured in index.c:901 - sis_find_segments_file
> > Error reading the segment infos.
>
> I'm not familiar with the internals of ferret, but the error looks
> pretty bad. It might have lost part of index data files.

indeed, I have had to build a new index scratch.

> Do you
> happen to have index or dump backups or find deleted files under
> ferret/ with using undelete tools?

No :-/

> Lessons learned...
>
> Always have regular (automatic, if possible) backups of your index
> dump, ALWAYS! I have sup-dump in my backup2l before-hook.

Yes, I have a daily cron script for it now.

> Hum. I think for people who don't do cron backups it wouldn't be a
> bad idea to create (optional) rotating sup-dumps on every start. (and
> stop?)
>

Thank you very much.
--
Carlos Garcia Campos
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

signature.asc (204 bytes) Download Attachment

Re: offlineimap before-poll.rb undefined method 'usual_sources'

2009-11-13T16:12:04Z

Excerpts from Micah Anderson's message of fr. nov. 13 16:53:15 +0100 2009:

>
> The before-poll.rb wiki example[0] seems to be what I am interested in,
> however it doesn't work and provides a traceback. It reads as follows:
>
> def offlineimap(*folders)
> cmd = "offlineimap -q -u Noninteractive.Basic"
> cmd << " -f #{folders * ','}" unless folders.compact.empty?
> `#{cmd}`
> end
>
> def folder_names(sources)
> sources.map { |s| s.uri.split('/').last }
> end
>
> def inbox_sources(sources = Index.usual_sources)
> sources.find_all { |s| !s.archived? }.sort_by {|s| s.id }
> end
>
> if (@last_fetch || Time.at(0)) < Time.now - 120
> say "Running offlineimap..."
> # only check non-auto-archived sources on the first run
> log offlineimap(@last_fetch ? nil : folder_names(inbox_sources))
> say "Finished offlineimap run."
> end
> @last_fetch = Time.now

Im using this modified version; and I filter the folders in
offlineimaprc.

def offlineimap(*folders)
cmd = "offlineimap -u Noninteractive.Basic 2>&1"
#cmd << " -f #{folders * ','}" unless folders.compact.empty?
`#{cmd}`
end

def folder_names(sources)
sources.map { |s| s.uri.split('/').last }
end

def inbox_sources(sources = SourceManager.sources)
sources.find_all { |s| !s.archived? }.sort_by {|s| s.id }
end

if (@last_fetch || Time.at(0)) < Time.now - 20
say "Running offlineimap..."
# only check non-auto-archived sources on the first run
log offlineimap(@last_fetch ? nil : folder_names(inbox_sources))
say "Finished offlineimap."
end
@last_fetch = Time.now

- gaute

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

signature.asc (205 bytes) Download Attachment

offlineimap before-poll.rb undefined method 'usual_sources'

2009-11-13T07:53:15Z

The before-poll.rb wiki example[0] seems to be what I am interested in,
however it doesn't work and provides a traceback. It reads as follows:

def offlineimap(*folders)
cmd = "offlineimap -q -u Noninteractive.Basic"
cmd << " -f #{folders * ','}" unless folders.compact.empty?
`#{cmd}`
end

def folder_names(sources)
sources.map { |s| s.uri.split('/').last }
end

def inbox_sources(sources = Index.usual_sources)
sources.find_all { |s| !s.archived? }.sort_by {|s| s.id }
end

if (@last_fetch || Time.at(0)) < Time.now - 120
say "Running offlineimap..."
# only check non-auto-archived sources on the first run
log offlineimap(@last_fetch ? nil : folder_names(inbox_sources))
say "Finished offlineimap run."
end
@last_fetch = Time.now

When I use this hook, i get this traceback in my sup log:

[Fri Nov 13 10:51:28 -0500 2009] hook: error running hook: undefined method `usual_sources' for #<Redwood::FerretIndex:0xb7520a64>
[Fri Nov 13 10:51:28 -0500 2009] hook: /usr/lib/ruby/1.8/sup/util.rb:520:in `send'
/usr/lib/ruby/1.8/sup/util.rb:520:in `method_missing'
/home/micah/.sup/hooks/before-poll.rb:11:in `inbox_sources'
/home/micah/.sup/hooks/before-poll.rb:18:in `__run'
/usr/lib/ruby/1.8/sup/hook.rb:42:in `__run'
/usr/lib/ruby/1.8/sup/hook.rb:82:in `run'
/usr/lib/ruby/1.8/sup/util.rb:520:in `send'
/usr/lib/ruby/1.8/sup/util.rb:520:in `method_missing'
/usr/lib/ruby/1.8/sup/poll.rb:45:in `poll'
/usr/lib/ruby/1.8/sup/util.rb:520:in `send'
/usr/lib/ruby/1.8/sup/util.rb:520:in `method_missing'
/usr/bin/sup-mail:195
/usr/lib/ruby/1.8/sup.rb:76:in `reporting_thread'
/usr/lib/ruby/1.8/sup.rb:74:in `initialize'
/usr/lib/ruby/1.8/sup.rb:74:in `new'
/usr/lib/ruby/1.8/sup.rb:74:in `reporting_thread'
/usr/bin/sup-mail:195
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:669:in `call'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:669:in `__unprotected_load_threads'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:610:in `call'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:610:in `load_n_threads_background'
/usr/lib/ruby/1.8/sup.rb:76:in `reporting_thread'
/usr/lib/ruby/1.8/sup.rb:74:in `initialize'
/usr/lib/ruby/1.8/sup.rb:74:in `new'
/usr/lib/ruby/1.8/sup.rb:74:in `reporting_thread'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:608:in `load_n_threads_background'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:679:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/usr/bin/sup-mail:195

Thanks,
micah

0. http://sup.rubyforge.org/wiki/wiki.pl?Hooks

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Sup not working anymore after abrupt reboot

2009-11-13T03:57:05Z

Excerpts from Carlos Garcia Campos's message of fr. nov. 13 10:11:38 +0100 2009:

> Hi all,
>
> my laptop ran out of battery while sup was polling new mail and now sup
> always fails to start.
> I don't know whether my ferret index is corrupt, this is the exception I
> get:
>
> ----------------------------------------------------------------
> --- IOError from thread: main
> IO Error occured at <except.c>:93 in xraise
> Error occured in index.c:901 - sis_find_segments_file
> Error reading the segment infos. Store listing was
>
>
> /usr/lib/ruby/1.8/ferret/index.rb:736:in `initialize'
> /usr/lib/ruby/1.8/ferret/index.rb:736:in `new'
> /usr/lib/ruby/1.8/ferret/index.rb:736:in `ensure_reader_open'
> /usr/lib/ruby/1.8/ferret/index.rb:591:in `size'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /usr/lib/ruby/1.8/ferret/index.rb:590:in `size'
> ./lib/sup/ferret_index.rb:31:in `load_index'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> ./lib/sup/ferret_index.rb:29:in `load_index'
> ./lib/sup/index.rb:67:in `load'
> ./lib/sup/util.rb:520:in `send'
> ./lib/sup/util.rb:520:in `method_missing'
> bin/sup:144

Also, the xapian backend works better (doesn't help you now thou, im
afraid).

- gaute
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Sup not working anymore after abrupt reboot

2009-11-13T03:10:17Z

Carlos Garcia Campos, 2009-11-13 11:11:
> I don't know whether my ferret index is corrupt, this is the exception I
> get:
>
> ----------------------------------------------------------------
> Error occured in index.c:901 - sis_find_segments_file
> Error reading the segment infos.

I'm not familiar with the internals of ferret, but the error looks
pretty bad. It might have lost part of index data files. Do you
happen to have index or dump backups or find deleted files under
ferret/ with using undelete tools?

Lessons learned...

Always have regular (automatic, if possible) backups of your index
dump, ALWAYS! I have sup-dump in my backup2l before-hook.

Hum. I think for people who don't do cron backups it wouldn't be a
bad idea to create (optional) rotating sup-dumps on every start. (and
stop?)

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Sup not working anymore after abrupt reboot

2009-11-13T01:11:38Z

Hi all,

my laptop ran out of battery while sup was polling new mail and now sup always fails to start.

I don't know whether my ferret index is corrupt, this is the exception I get:

----------------------------------------------------------------

--- IOError from thread: main

IO Error occured at <except.c>:93 in xraise

Error occured in index.c:901 - sis_find_segments_file

Error reading the segment infos. Store listing was

/usr/lib/ruby/1.8/ferret/index.rb:736:in `initialize'

/usr/lib/ruby/1.8/ferret/index.rb:736:in `new'

/usr/lib/ruby/1.8/ferret/index.rb:736:in `ensure_reader_open'

/usr/lib/ruby/1.8/ferret/index.rb:591:in `size'

/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'

/usr/lib/ruby/1.8/ferret/index.rb:590:in `size'

./lib/sup/ferret_index.rb:31:in `load_index'

/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'

./lib/sup/ferret_index.rb:29:in `load_index'

./lib/sup/index.rb:67:in `load'

./lib/sup/util.rb:520:in `send'

./lib/sup/util.rb:520:in `method_missing'

bin/sup:144

is there any way to recover it? (if possible without losing mi index . . . )

Thanks in advance.

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: mark-as-spam.rb and writing hooks

2009-11-12T10:50:54Z

Excerpts from micah anderson's message of Thu Nov 12 10:35:59 -0500 2009:

> > spam = thread.labels.member? :spam
> > what = spam ? 'spam' : 'ham'
>
> I'm curious about this 'what' piece. It seems like it is a way to
> specify the message as 'spam' or 'ham', which is the second half of the
> puzzle: go into my Spam source and review the messages there, if there
> is a incorrectly categorized as spam message, I would typically stuff
> that into Mistakes as well. It seems like you *have* built this into
> this hook, but I don't understand how it is able to determine one from
> the other? There is the 'S' mark-as-spam key, but there is no 'H'
> mark-as-ham :)

There's only 'S' and the mark-as-spam hook, but you can tell whether the
user has marked the thread as spam or ham by checking the labels. If the
thread is labelled 'spam', it's spam.

> Yeah, I had realized this thread problem when I saw that the thread
> variable was available for this hook. I think that this is mostly ok, I
> think getting threaded spam is somewhat unusual... but I will pay
> attention to see how frequently this happens. In the case that it
> happens, i'll probably fire up mutt, categorize it as Spam, and then
> re-index my sup index, which is what I was doing before.

If you can configure your spam filter so it reads from two folders,
'spam' and 'ham', then you can safely store extra messages in them
(assuming you don't have true-spam threaded with true-ham). My own setup
is slightly different - I write the raw message to a tempfile and run
sa-learn on it with --spam or --ham.

> > We should also have a Thread#each_message which ignores any
> > result of Thread#each that isn't a Message. These two changes would make
> > the hook above a lot less magical. What other API changes could we do
> > to make writing hooks easier?
>
> Would that make it so the above thread problem would go away?

Nope, it would just mean easier iteration over the messages in a thread.
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Problems with undo archive and thread focus

2009-11-12T09:30:01Z

Excerpts from Matthias Guedemann's message of Thu Nov 05 00:27:25 -0800 2009:
> One is, if you hit 'a' in thread view mode, the thread is archived but undo does
> not work. If you go back to index view and hit 'u' the just archived thread does
> not appear, but the one before.

I was annoyed by this too and found that undo is minimally implemented.
I added undo to thread view, at least for the cases that I care about or
were easy. I have to say I was discouraged that this was necessary: the
code to archive a thread should all be in one place, and the undo
record should be created there. There's a lot of code duplication, and
I can't tell if it's because the model and view are too coupled, or
because nobody has bothered to factor it out.

The patch is appended. (This is the first time I've done this with git.)

> The second is, if I respond to a thread and send the mail, I normally want to
> either archive that mail directly or label and archive it. But the thread is put
> to the front and the focus is on the last place of the thread. Therefore I
> sometimes archive the wrong thread (but undo comes in handy)

That's the next most annying thing for me. Hope to get a chance to work
on it.

Andrew

Subject: [PATCH] create undo records in thread view

---
lib/sup/modes/thread-view-mode.rb | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletions(-)

diff --git a/lib/sup/modes/thread-view-mode.rb b/lib/sup/modes/thread-view-mode.rb
index 81197c2..2f2d564 100644
--- a/lib/sup/modes/thread-view-mode.rb
+++ b/lib/sup/modes/thread-view-mode.rb
@@ -254,7 +254,8 @@ EOS
end

def edit_labels
- reserved_labels = @thread.labels.select { |l| LabelManager::RESERVED_LABELS.include? l }
+ old_labels = @thread.labels
+ reserved_labels = old_labels.select { |l| LabelManager::RESERVED_LABELS.include? l }
new_labels = BufferManager.ask_for_labels :label, "Labels for thread: ", @thread.labels

return unless new_labels
@@ -262,6 +263,10 @@ EOS
new_labels.each { |l| LabelManager << l }
update
UpdateManager.relay self, :labeled, @thread.first
+ UndoManager.register "labeling thread" do
+ @thread.labels = old_labels
+ UpdateManager.relay self, :labeled, @thread.first
+ end
end

def toggle_starred
@@ -476,6 +481,10 @@ EOS
dispatch op do
@thread.remove_label :inbox
UpdateManager.relay self, :archived, @thread.first
+ UndoManager.register "archiving 1 thread" do
+ @thread.apply_label :inbox
+ UpdateManager.relay self, :unarchived, @thread.first
+ end
end
end

@@ -483,6 +492,10 @@ EOS
dispatch op do
@thread.apply_label :spam
UpdateManager.relay self, :spammed, @thread.first
+ UndoManager.register "marking 1 thread as spam" do
+ @thread.remove_label :spam
+ UpdateManager.relay self, :unspammed, @thread.first
+ end
end
end

@@ -490,6 +503,10 @@ EOS
dispatch op do
@thread.apply_label :deleted
UpdateManager.relay self, :deleted, @thread.first
+ UndoManager.register "deleting 1 thread" do
+ @thread.remove_label :deleted
+ UpdateManager.relay self, :undeleted, @thread.first
+ end
end
end

--
1.5.6.5

--
I've decided to go back to school. Kindergarden.
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: mark-as-spam.rb and writing hooks

2009-11-11T22:40:14Z

Hi Micah,

Something like the following could work:

spam = thread.labels.member? :spam
what = spam ? 'spam' : 'ham'
source_uri = "maildir:///tmp/mistakes"
source = SourceManager.source_for(source_uri) or fail "source not found"
thread.each do |m,a,b|
next if !m or m == :fake_root
info "marking message #{m.id} as #{what}"
source.store_message m.date, m.from.email do |f|
m.each_raw_message_line { |l| f.puts l }
end
end

This code assumes a maildir (/tmp/mistakes) and that you've added it as
a sup "source" with "sup-add -u maildir:///tmp/mistakes". When you mark
a thread as spam/ham, it will store the messages into that maildir. One
problem with the above code is that it does store the entire thread, so
if only one message was miscategorized you'll end up confusing your spam
filter. Depending on your exact mail setup you can probably do something
smarter here.

Excerpts from Micah Anderson's message of Tue Nov 10 23:08:22 -0500 2009:
> There has to be some way to have sup actually move a message, isn't
> there?

Sup really doesn't like it when messages are deleted from a source.
Best to just keep it a copy.

For other sup developers: it shouldn't take this much hook code to do
this. I suggest renaming Source#store_message to Source#store_raw. A new
Source#store_message should take a Message as the first argument and let
the mbox From header address and date be optional with reasonable
defaults. We should also have a Thread#each_message which ignores any
result of Thread#each that isn't a Message. These two changes would make
the hook above a lot less magical. What other API changes could we do
to make writing hooks easier?
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: [PATCH] moved deriving the cmd for bouncing to Account and fixed a bug in it

2009-11-11T20:30:56Z

Excerpts from Tero Tilus's message of Sat Oct 10 03:21:33 -0400 2009:

> The default sendmail command used for bouncing mail was derived from
> Account#sendmail in ThreadViewMode#bounce. Moved it to
> Account#bounce_sendmail. Part of work towards more DRY mail bouncing
> within mark-as-spam hook. The code also had a bug, "$1" (instead of $1
> or "#{$1}"). Fixed it.
>
> Signed-off-by: Tero Tilus <tero@...>
> ---
> lib/sup/account.rb | 11 +++++++++++
> lib/sup/modes/thread-view-mode.rb | 7 +------
> 2 files changed, 12 insertions(+), 6 deletions(-)

Looks good to me. Pushed to branch fix-bounce-cmd in my repo* and merged
to master.

* git://github.com/rlane/sup
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

mark-as-spam.rb and writing hooks

2009-11-10T20:08:22Z

Howdy folks,

Normally, spam is automatically put into my imap Spam folder, but
something gets through, then I move it to the Mistakes folder, and send
it back to the imap server. Anything put in the Mistakes folder gets
processed for Spam/Ham scenarios (conversely, if I move something from
the Spam folder that is actually not spam and put it in the Mistakes
folder, then spamassassin trains bayes to learn that is actually Ham,
not Spam). This is a pretty common Bayes training
setup.

Sadly, this is something that Sup doesn't do, so I am stuck getting all
of this spam in my inbox. so I think what I need to do is use the
mark-as-spam hook to copy the message to another location. I'm using
offlineimap, so I can just do a file copy of the actual file to the
right spot and let sup do the rest. This seems like the most logical
place to look, use this hook to make a copy of the mail to my Mistakes
maildir folder when I press 'S', and then the offlineimap process will
go and put it back on the IMAP server for processing.

It seems like a hook could do this fairly easily, but because I dont
know ruby its a lot harder for me, also I couldn't find much information
about how to use hooks. I read the hooks.txt file in the debian package,
but it wans't so useful.

Spent some time today trying to figure out how hooks work. Couldn't find
much information out there, but eventually figured out that there are a
handful of hooks available, which you can list via 'sup -l', for
example:

mark-as-spam
------------
File: /home/micah/.sup/hooks/mark-as-spam.rb
This hook is run when a thread is marked as spam
Variables: thread: The message thread being marked as spam.

basically what this means is that if you put a file in
.sup/hooks/mark-as-spam.rb with ruby code it will be executed when you
hit the S key, and the "thread" variable is available to this hook.

The above took me quite some time to determine, not being a ruby person
and all, now that I got that, I want to use it!

So what is that thread variable? I only really found it in thread.rb, so
I looked at that for a while, I find that a thread is a bunch of
messages, so I figure I need to enumerate the array. Then I taught
myself some ruby looping and variable interpolation, and came up with
this:

log "Marking thread #{thread.to_s} of size #{thread.size} as spam..."
thread.each { |message| system 'cp', message, '/home/me/Maildir/Personal/INBOX.Mistakes/cur' }

and hey, it almost works, just incorrectly, my sup log gets:

hook[mark-as-spam]: Marking thread <thread containing: <20091110072526.5236749428B@...>> of size 1 as spam...

But... I dont know how to get the thread array to tell me where the
actual file is. I spent some more quality time with the source, and I am
pretty sure that a @thread is an array of Containers which contain the
different Messages, which are accessed via Store... but i dont know if I
can access any of that, there is a Thread class, Container class,
Message class and finally a Source class, and I think the problem is
that thread.each isn't an actual file its more of a thread object of
some sort, and if I knew how to get at the actual file, I could just
use a simple system call to copy it where I need to.

There has to be some way to have sup actually move a message, isn't
there?

thanks for any help!
micah

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Getting gpg to work

2009-11-10T15:47:18Z

William Morgan <wmorgan-sup@...> writes:

> Reformatted excerpts from Micah Anderson's message of 2009-05-28:
>> [Fri May 29 00:17:42 -0400 2009] crypto: detected gpg binary in /usr/bin/gpg
>
> Any other obvious messages in the log about multipart/encrypted?

I failed to respond to this message, partly because I think I decided to
give up on sup at the time. But I am back now, because sup is so
alluring, and I'm trying harder to switch this time :)

This time, gpg works fine... although it is using the wrong gpg keyid
when I try to send. I did manage to find and set the gpgkey configurable
in the .sup/config.yaml:

:accounts:
:default:
:signature: /home/micah/.signature
:email: micah@...
:sendmail: /usr/sbin/sendmail -oem -ti
:name: micah anderson
:gpgkey: 0xDEADBEEF

but still, that key does not get used, and instead the first key in my
keyring for my email@address gets used instead. I do not want that,
because that key is set to expire in about a week.

micah

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Error upon starting sup

2009-11-10T09:10:42Z

Excerpts from k.v.ramakrishna reddy's message of Tue Nov 10 04:23:22 -0500 2009:
> --- RuntimeError from thread: load threads for thread-index-mode
> invalid source 3

It looks like you removed a source. If you remember what it was, you can
just re-add it (and tweak the id in sources.yaml). Otherwise, a
sup-dump, deleting the ferret db, and sup-sync -a --restore will solve
the problem.
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Error upon starting sup

2009-11-10T01:23:22Z

--- RuntimeError from thread: load threads for thread-index-mode
invalid source 3
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:260:in `build_message'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:256:in `build_message'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:163:in `each_id_by_date'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/thread.rb:332:in `call'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/thread.rb:332:in `load_n_threads'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:163:in `each_id_by_date'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:162:in `each'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/ferret_index.rb:162:in `each_id_by_date'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/thread.rb:328:in `load_n_threads'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:625:in `__unprotected_load_n_threads'
(eval):12:in `load_n_threads'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:609:in `load_n_threads_background'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup.rb:77:in `reporting_thread'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup.rb:75:in `initialize'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup.rb:75:in `new'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup.rb:75:in `reporting_thread'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:608:in `load_n_threads_background'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/lib/sup/modes/thread-index-mode.rb:679:in `__unprotected_load_threads'
(eval):12:in `load_threads'
/home/karri/.gem/ruby/1.8/gems/sup-0.9/bin/sup:196
/home/karri/.gem/ruby/1.8/bin/sup:19:in `load'

/home/karri/.gem/ruby/1.8/bin/sup:19

thanks

karri

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: [PATCH 2/4] async thread indexing

2009-11-08T22:22:03Z

Excerpts from Eugene Marinelli's message of Mon Nov 09 01:02:07 -0500 2009:
> > - Index.save_thread t
> > + Index.save_thread_async t
> Where is the "save_thread_async" function?
>
> In patch 3/4, this looks like a syntax error:
> > - end
> > + threads.each { |t| Index.save_thread async t }
> > end

Nice catch. I'd originally named the method save_thread_async and it
looks like my search-and-replace wasn't complete. I've fixed this on the
immediate-updates branch. Thanks for the review!
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: [PATCH 2/4] async thread indexing

2009-11-08T22:02:07Z

> - Index.save_thread t
> + Index.save_thread_async t
Where is the "save_thread_async" function?

In patch 3/4, this looks like a syntax error:
> - end
> + threads.each { |t| Index.save_thread async t }
> end

- Eugene Marinelli

On Wed, Nov 4, 2009 at 9:45 PM, Rich Lane <rlane@...> wrote:

> ---
> bin/sup | 2 ++
> lib/sup/index.rb | 26 +++++++++++++++++++++++++-
> lib/sup/modes/thread-index-mode.rb | 2 +-
> 3 files changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/bin/sup b/bin/sup
> index 78c396a..910ff12 100755
> --- a/bin/sup
> +++ b/bin/sup
> @@ -142,6 +142,7 @@ Index.lock_interactively or exit
> begin
> Redwood::start
> Index.load
> + Index.start_sync_worker unless $opts[:no_threads]
>
> $die = false
> trap("TERM") { |x| $die = true }
> @@ -335,6 +336,7 @@ ensure
>
> HookManager.run "shutdown"
>
> + Index.stop_sync_worker
> Redwood::finish
> stop_cursing
> Redwood::Logger.remove_all_sinks!
> diff --git a/lib/sup/index.rb b/lib/sup/index.rb
> index 5d8d714..1131ec7 100644
> --- a/lib/sup/index.rb
> +++ b/lib/sup/index.rb
> @@ -28,6 +28,8 @@ class BaseIndex
> def initialize dir=BASE_DIR
> @dir = dir
> @lock = Lockfile.new lockfile, :retries => 0, :max_age => nil
> + @sync_worker = nil
> + @sync_queue = Queue.new
> end
>
> def lockfile; File.join @dir, "lock" end
> @@ -175,10 +177,32 @@ class BaseIndex
>
> def save_thread t
> t.each_dirty_message do |m|
> - update_message_state m
> + if @sync_worker
> + @sync_queue << m
> + else
> + update_message_state m
> + end
> m.clear_dirty
> end
> end
> +
> + def start_sync_worker
> + @sync_worker = Redwood::reporting_thread('index sync') { run_sync_worker }
> + end
> +
> + def stop_sync_worker
> + return unless worker = @sync_worker
> + @sync_worker = nil
> + @sync_queue << :die
> + worker.join
> + end
> +
> + def run_sync_worker
> + while m = @sync_queue.deq
> + return if m == :die
> + update_message_state m
> + end
> + end
> end
>
> index_name = ENV['SUP_INDEX'] || $config[:index] || DEFAULT_INDEX
> diff --git a/lib/sup/modes/thread-index-mode.rb b/lib/sup/modes/thread-index-mode.rb
> index 370903a..d2b1651 100644
> --- a/lib/sup/modes/thread-index-mode.rb
> +++ b/lib/sup/modes/thread-index-mode.rb
> @@ -477,7 +477,7 @@ EOS
> BufferManager.say("Saving threads...") do |say_id|
> dirty_threads.each_with_index do |t, i|
> BufferManager.say "Saving modified thread #{i + 1} of #{dirty_threads.length}...", say_id
> - Index.save_thread t
> + Index.save_thread_async t
> end
> end
> end
> --
> 1.6.4.2
>
> _______________________________________________
> sup-talk mailing list
> sup-talk@...
> http://rubyforge.org/mailman/listinfo/sup-talk
>

_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: Apple Address Book integration for Sup?

2009-11-07T09:18:51Z

Excerpts from tom's message of Sat Nov 07 12:01:31 -0500 2009:

> Hey,
>
> Could anyone point me towards where I should start hacking or looking
> to get my address book contacts as options in Sup? I'm up for the task
> if the contact list is pluggable, but obviously documentation is
> somewhat minimal here.
>
> Thanks!
>
> Tom

Hi Tom,

If you're just looking to get tab-completion for these contacts you can
create a extra-contact-addresses hook script that imports them.

- Rich
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Apple Address Book integration for Sup?

2009-11-07T09:01:31Z

Hey,

Could anyone point me towards where I should start hacking or looking
to get my address book contacts as options in Sup? I'm up for the task
if the contact list is pluggable, but obviously documentation is
somewhat minimal here.

Thanks!

Tom
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: slowly catching up

2009-11-07T08:56:10Z

Reformatted excerpts from Rich Lane's message of 2009-11-06:
> As for getting changes to William, I'll occasionally (weekly?) apply
> the patches I deem stable on top of his master branch and send mail to
> the list. This way it should be a fast-forward when he pulls and we
> won't have to worry about resolving merges differently.

Sounds good to me. I'm not even that concerned about fastforward vs
merge.

> As a side note, I just created a Wishlist wiki page for feature requests:
> http://sup.rubyforge.org/wiki/wiki.pl?Wishlist

I agree that these would be great to have on the issue tracker.
--
William <wmorgan-sup@...>
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: sup bug tracker

2009-11-07T08:32:08Z

Reformatted excerpts from Tero Tilus's message of 2009-11-07:
> What should be the policy with issues are reported/discussed on irc or
> mailinglist but are not reported to tracker? Should The Sup Issues
> Task Force(TM) ;) report them to tracker or try to push the original
> reporter to do it?

I would like all new issues to go on the tracker, and I think it's
completely reasonable to tell people who report things to the mailing
list or IRC to instead use the issue tracker instead.

> Should we (The SITF) skim mailinglist archives and transfer reported
> unfixed bugs (with links to archives) to tracker?

If the SITF wants to creating issues for existing bug reports, that
would be very helpful. But please don't do it to the point that you get
sick of it.

> Sup home http://sup.rubyforge.org/ is not yet pointing there.

Fixed, thanks!
--
William <wmorgan-sup@...>
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: sup bug tracker

2009-11-07T03:15:56Z

William Morgan, 2009-11-06 18:33:
> If you have existing bug reports or feature requests and you don't
> want to rely on my faulty memory any more, feel free to resubmit
> them here.

What should be the policy with issues are reported/discussed on irc or
mailinglist but are not reported to tracker? Should The Sup Issues
Task Force(TM) ;) report them to tracker or try to push the original
reporter to do it?

Should we (The SITF) skim mailinglist archives and transfer reported
unfixed bugs (with links to archives) to tracker?

> I'm going to point the 0.9.1 crash message there too.

Sup home http://sup.rubyforge.org/ is not yet pointing there.

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk

Re: slowly catching up

2009-11-07T01:34:38Z

Rich Lane, 2009-11-07 09:09:
> Sounds good. I'll keep using my clone at
> http://github.com/rlane/sup/tree/master unless people would prefer I
> move it to gitorious.

Does it really make that big difference? I don't think.

> As a side note, I just created a Wishlist wiki page for feature
> requests: http://sup.rubyforge.org/wiki/wiki.pl?Wishlist

Why not use tracker for feature requests too? If I don't hear any
reasons why, I'll go put the wishlist items there too.

--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@...
http://rubyforge.org/mailman/listinfo/sup-talk