From affc5b3e5f1e50f477f58b6e95e35c13e8a1dd8c Mon Sep 17 00:00:00 2001 From: William Morgan Date: Wed, 30 Jul 2008 17:18:04 -0700 Subject: [PATCH] add bugs dir back to master --- ...0b36671ecb019e57ef27e0901bff055385371.yaml | 22 ++++++++ ...6bae05fa885bf6fcae39f864eb923c1e9a79e.yaml | 27 ++++++++++ ...79a2ada22c2a0d76427e12ef2514d4753d070.yaml | 18 +++++++ ...38247f939d20f8f202f80ccb85d9ad92101e0.yaml | 18 +++++++ ...841e15d6909892adf43678bae03597ce10519.yaml | 25 +++++++++ ...527438c2d198eae9a264ce9e6b847854d9837.yaml | 30 +++++++++++ ...2263b6a2b7de6ae1ec4ab315c7829763e61be.yaml | 22 ++++++++ ...58477a445c2e61405fecb4cb641a2298caba6.yaml | 27 ++++++++++ ...363cdf9d25edfa2a04b21299a538365e8b319.yaml | 25 +++++++++ ...4aa6843feee4daefe740b6e3f1fc54ff4bfcb.yaml | 22 ++++++++ ...f0cdac8d1998c46759a4ebef9077999bcef09.yaml | 18 +++++++ ...8c200a5f47f92d12b5c063a00ce891c2ba4ce.yaml | 22 ++++++++ ...1fb8b7f955d625633d06fa0bf67a9afab046e.yaml | 18 +++++++ ...6f805b0c8bad013ec73f56e6245c890528591.yaml | 29 ++++++++++ ...5f1d56b9be533edaf232b9e60dc24e00cba0b.yaml | 26 +++++++++ ...b0840f9a1924f1c0561e8ddcf7e6988543ba0.yaml | 26 +++++++++ ...f983ccdb75408a37b3911472d4015664a3cf6.yaml | 20 +++++++ ...ab6443b6c107c3067cdb614186099db570acf.yaml | 37 +++++++++++++ ...242013994ae557e431ba350a92c4f9e1739ef.yaml | 28 ++++++++++ ...a2721dac8dfeb8730ee081f73b6c62702bd3e.yaml | 18 +++++++ ...01973cea5bd1f28739ae4cea98edce8249895.yaml | 32 +++++++++++ ...8fec2b1112250e241afc7467de29e5691d1be.yaml | 21 ++++++++ ...68c69d0190d6e849309834d4ad1d215efa779.yaml | 21 ++++++++ ...5c3c1b47e88f7261f57f31d33fe15ad08465d.yaml | 20 +++++++ ...b957dcd16f1da8962fe5b1f3a58d970315deb.yaml | 24 +++++++++ ...86dd32054533a6206f698033ec668af6a7574.yaml | 18 +++++++ ...49ec83770b5d46f89eff21799968187012cce.yaml | 22 ++++++++ ...06670167642cc581956bc1b25c26b5bff215b.yaml | 30 +++++++++++ ...389418b5f0038cc3e6bc20fd3fd1566eb7111.yaml | 26 +++++++++ ...785cddcc6e09ef0a357151373b3aa923d5e3f.yaml | 22 ++++++++ ...53cca2eb05af486a2d09c6772fd5bd0cca444.yaml | 20 +++++++ ...d634de74b2eb8297174ecd408b3810ba9351b.yaml | 24 +++++++++ ...960514f66ee67da083bc7bb5632d5808fc607.yaml | 30 +++++++++++ ...6c2d8fbd5de4dac651f6f4e9756f577497e01.yaml | 26 +++++++++ ...02330c4fdd091e8b1dd08dcc29ed432f003d4.yaml | 26 +++++++++ ...771a6a435dcad66dc80e7e051d91d24d005b1.yaml | 31 +++++++++++ ...8c1e7120a8540c7c51c6095f4815918d16641.yaml | 28 ++++++++++ ...7e757321c2639daea013824ad1a14099815b1.yaml | 26 +++++++++ ...474dfeeefaa50151c3ce48bee6b686d36a216.yaml | 29 ++++++++++ ...b449c51fca9a39047d00fabc552cc110c69b2.yaml | 24 +++++++++ ...80f6dc2ce7b10b9e8f503d68253ced0ee8a1b.yaml | 24 +++++++++ ...cf9242ca60fa6c81091e425f734b4fb03e41a.yaml | 53 +++++++++++++++++++ ...7ea95f066fd0668452093b85903bd142905c9.yaml | 26 +++++++++ ...e627c500f679badca28f60ba76998fd65d46a.yaml | 26 +++++++++ ...1549102c0bfa2c201476d9618f7d234d1a626.yaml | 22 ++++++++ ...e28de46d74f7f1e445ae75ea4e230c7473374.yaml | 22 ++++++++ ...3427de5e8d4f74c0620f99e97ed92d21e924c.yaml | 30 +++++++++++ ...622dbae0e1841b4d9a376d419aed1d91460e0.yaml | 26 +++++++++ ...3480a30a18c3e823dbe20b759e1dcb32ca2b9.yaml | 26 +++++++++ ...148169baa3838051f4bdb4c175e11cbf7f143.yaml | 22 ++++++++ ...5ae6378afa9bd2a8e1b15d28ba7ccef867791.yaml | 18 +++++++ ...2aa00f4064fc7e1332cee0dae2c2ae95bb217.yaml | 26 +++++++++ ...1579fd8350d8add15c5cb588169acfdc5ea24.yaml | 24 +++++++++ ...aa39ef3b8d33bd57e4988c55d89c7c0df5c96.yaml | 24 +++++++++ ...4415a9d4c8fd3602500111bf9268aa7c7c6a4.yaml | 27 ++++++++++ ...2527210b3aacae2f74029e5856fed82f1689c.yaml | 33 ++++++++++++ ...f7fc58bba0b38ff6ae14cca01b08a5a7a6c33.yaml | 21 ++++++++ ...f9762bc24a8f45863eb2e7beefa4201db34e8.yaml | 22 ++++++++ ...0ddfa9d633501140dd199bdfd7cd9fed5df0b.yaml | 22 ++++++++ ...3096582de268c050f78223eb6a22ac2599606.yaml | 31 +++++++++++ ...9ec6ec7c35d7d8c002b0521f97b6e94dc9b3e.yaml | 26 +++++++++ ...fc65dc90280fa5ecc63094af01d2a47ff0c6e.yaml | 22 ++++++++ ...1464e921aefc35571c119aac4d9f1decdebae.yaml | 30 +++++++++++ ...4a360c9cb2a6e12a734962a39ffbc6486a725.yaml | 29 ++++++++++ ...6be1b524c6c0a5c31c9c468bda170c2a8cb58.yaml | 28 ++++++++++ ...b18777ea3aef3566bd80acd126e9ef8a5883a.yaml | 34 ++++++++++++ ...39718b4dbf49bbd3dd47133affbf7cb1e2361.yaml | 24 +++++++++ ...2f66a7ff4fb4525c2719e77ac8eedf3835dfd.yaml | 20 +++++++ ...7a9d2071da7b0f66698ce74e642bf347be96b.yaml | 21 ++++++++ ...c7a7d7caf41ff20e7d10ca3f074fc02c14a5b.yaml | 25 +++++++++ ...c906e8f4f6eb10f1ebdf39c416415d9ab6af9.yaml | 26 +++++++++ bugs/project.yaml | 49 +++++++++++++++++ 72 files changed, 1837 insertions(+) create mode 100644 bugs/issue-0240b36671ecb019e57ef27e0901bff055385371.yaml create mode 100644 bugs/issue-08d6bae05fa885bf6fcae39f864eb923c1e9a79e.yaml create mode 100644 bugs/issue-09479a2ada22c2a0d76427e12ef2514d4753d070.yaml create mode 100644 bugs/issue-15738247f939d20f8f202f80ccb85d9ad92101e0.yaml create mode 100644 bugs/issue-182841e15d6909892adf43678bae03597ce10519.yaml create mode 100644 bugs/issue-1a1527438c2d198eae9a264ce9e6b847854d9837.yaml create mode 100644 bugs/issue-2312263b6a2b7de6ae1ec4ab315c7829763e61be.yaml create mode 100644 bugs/issue-23658477a445c2e61405fecb4cb641a2298caba6.yaml create mode 100644 bugs/issue-2a0363cdf9d25edfa2a04b21299a538365e8b319.yaml create mode 100644 bugs/issue-2e74aa6843feee4daefe740b6e3f1fc54ff4bfcb.yaml create mode 100644 bugs/issue-314f0cdac8d1998c46759a4ebef9077999bcef09.yaml create mode 100644 bugs/issue-3408c200a5f47f92d12b5c063a00ce891c2ba4ce.yaml create mode 100644 bugs/issue-3441fb8b7f955d625633d06fa0bf67a9afab046e.yaml create mode 100644 bugs/issue-38d6f805b0c8bad013ec73f56e6245c890528591.yaml create mode 100644 bugs/issue-3b25f1d56b9be533edaf232b9e60dc24e00cba0b.yaml create mode 100644 bugs/issue-42ab0840f9a1924f1c0561e8ddcf7e6988543ba0.yaml create mode 100644 bugs/issue-46df983ccdb75408a37b3911472d4015664a3cf6.yaml create mode 100644 bugs/issue-47aab6443b6c107c3067cdb614186099db570acf.yaml create mode 100644 bugs/issue-4af242013994ae557e431ba350a92c4f9e1739ef.yaml create mode 100644 bugs/issue-4daa2721dac8dfeb8730ee081f73b6c62702bd3e.yaml create mode 100644 bugs/issue-4e501973cea5bd1f28739ae4cea98edce8249895.yaml create mode 100644 bugs/issue-5348fec2b1112250e241afc7467de29e5691d1be.yaml create mode 100644 bugs/issue-57668c69d0190d6e849309834d4ad1d215efa779.yaml create mode 100644 bugs/issue-5795c3c1b47e88f7261f57f31d33fe15ad08465d.yaml create mode 100644 bugs/issue-5fab957dcd16f1da8962fe5b1f3a58d970315deb.yaml create mode 100644 bugs/issue-60d86dd32054533a6206f698033ec668af6a7574.yaml create mode 100644 bugs/issue-61949ec83770b5d46f89eff21799968187012cce.yaml create mode 100644 bugs/issue-65506670167642cc581956bc1b25c26b5bff215b.yaml create mode 100644 bugs/issue-658389418b5f0038cc3e6bc20fd3fd1566eb7111.yaml create mode 100644 bugs/issue-69f785cddcc6e09ef0a357151373b3aa923d5e3f.yaml create mode 100644 bugs/issue-6c053cca2eb05af486a2d09c6772fd5bd0cca444.yaml create mode 100644 bugs/issue-6e0d634de74b2eb8297174ecd408b3810ba9351b.yaml create mode 100644 bugs/issue-6e7960514f66ee67da083bc7bb5632d5808fc607.yaml create mode 100644 bugs/issue-7456c2d8fbd5de4dac651f6f4e9756f577497e01.yaml create mode 100644 bugs/issue-76802330c4fdd091e8b1dd08dcc29ed432f003d4.yaml create mode 100644 bugs/issue-799771a6a435dcad66dc80e7e051d91d24d005b1.yaml create mode 100644 bugs/issue-7a68c1e7120a8540c7c51c6095f4815918d16641.yaml create mode 100644 bugs/issue-7c77e757321c2639daea013824ad1a14099815b1.yaml create mode 100644 bugs/issue-7d8474dfeeefaa50151c3ce48bee6b686d36a216.yaml create mode 100644 bugs/issue-829b449c51fca9a39047d00fabc552cc110c69b2.yaml create mode 100644 bugs/issue-82c80f6dc2ce7b10b9e8f503d68253ced0ee8a1b.yaml create mode 100644 bugs/issue-8a5cf9242ca60fa6c81091e425f734b4fb03e41a.yaml create mode 100644 bugs/issue-8aa7ea95f066fd0668452093b85903bd142905c9.yaml create mode 100644 bugs/issue-8c0e627c500f679badca28f60ba76998fd65d46a.yaml create mode 100644 bugs/issue-91e1549102c0bfa2c201476d9618f7d234d1a626.yaml create mode 100644 bugs/issue-9f7e28de46d74f7f1e445ae75ea4e230c7473374.yaml create mode 100644 bugs/issue-a1a3427de5e8d4f74c0620f99e97ed92d21e924c.yaml create mode 100644 bugs/issue-a1e622dbae0e1841b4d9a376d419aed1d91460e0.yaml create mode 100644 bugs/issue-a533480a30a18c3e823dbe20b759e1dcb32ca2b9.yaml create mode 100644 bugs/issue-a68148169baa3838051f4bdb4c175e11cbf7f143.yaml create mode 100644 bugs/issue-aae5ae6378afa9bd2a8e1b15d28ba7ccef867791.yaml create mode 100644 bugs/issue-ad82aa00f4064fc7e1332cee0dae2c2ae95bb217.yaml create mode 100644 bugs/issue-b1f1579fd8350d8add15c5cb588169acfdc5ea24.yaml create mode 100644 bugs/issue-b80aa39ef3b8d33bd57e4988c55d89c7c0df5c96.yaml create mode 100644 bugs/issue-bdd4415a9d4c8fd3602500111bf9268aa7c7c6a4.yaml create mode 100644 bugs/issue-bff2527210b3aacae2f74029e5856fed82f1689c.yaml create mode 100644 bugs/issue-c48f7fc58bba0b38ff6ae14cca01b08a5a7a6c33.yaml create mode 100644 bugs/issue-c52f9762bc24a8f45863eb2e7beefa4201db34e8.yaml create mode 100644 bugs/issue-c660ddfa9d633501140dd199bdfd7cd9fed5df0b.yaml create mode 100644 bugs/issue-cef3096582de268c050f78223eb6a22ac2599606.yaml create mode 100644 bugs/issue-cf09ec6ec7c35d7d8c002b0521f97b6e94dc9b3e.yaml create mode 100644 bugs/issue-cfbfc65dc90280fa5ecc63094af01d2a47ff0c6e.yaml create mode 100644 bugs/issue-d131464e921aefc35571c119aac4d9f1decdebae.yaml create mode 100644 bugs/issue-d994a360c9cb2a6e12a734962a39ffbc6486a725.yaml create mode 100644 bugs/issue-d9e6be1b524c6c0a5c31c9c468bda170c2a8cb58.yaml create mode 100644 bugs/issue-e43b18777ea3aef3566bd80acd126e9ef8a5883a.yaml create mode 100644 bugs/issue-e7739718b4dbf49bbd3dd47133affbf7cb1e2361.yaml create mode 100644 bugs/issue-e9c2f66a7ff4fb4525c2719e77ac8eedf3835dfd.yaml create mode 100644 bugs/issue-f767a9d2071da7b0f66698ce74e642bf347be96b.yaml create mode 100644 bugs/issue-fd7c7a7d7caf41ff20e7d10ca3f074fc02c14a5b.yaml create mode 100644 bugs/issue-fdfc906e8f4f6eb10f1ebdf39c416415d9ab6af9.yaml create mode 100644 bugs/project.yaml diff --git a/bugs/issue-0240b36671ecb019e57ef27e0901bff055385371.yaml b/bugs/issue-0240b36671ecb019e57ef27e0901bff055385371.yaml new file mode 100644 index 0000000..e5565ce --- /dev/null +++ b/bugs/issue-0240b36671ecb019e57ef27e0901bff055385371.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: messages with unparseable date headers are being discarded entirely +desc: it's better to forge the date headers and keep the messages +type: :bugfix +component: sup +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 03:57:25.399978 Z +references: [] + +id: 0240b36671ecb019e57ef27e0901bff055385371 +log_events: +- - 2008-03-07 03:57:25.400014 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:57:29.249827 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-08d6bae05fa885bf6fcae39f864eb923c1e9a79e.yaml b/bugs/issue-08d6bae05fa885bf6fcae39f864eb923c1e9a79e.yaml new file mode 100644 index 0000000..3c4be72 --- /dev/null +++ b/bugs/issue-08d6bae05fa885bf6fcae39f864eb923c1e9a79e.yaml @@ -0,0 +1,27 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: reply-from hook +desc: "hook for setting the from: address of a reply programmatically" +type: :feature +component: hooks +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-06-19 17:58:26.142289 Z +references: [] + +id: 08d6bae05fa885bf6fcae39f864eb923c1e9a79e +log_events: +- - 2008-06-19 17:58:27.334371 Z + - William Morgan + - created + - "" +- - 2008-06-19 17:58:40.526270 Z + - William Morgan + - changed status from unstarted to in_progress + - branch reply-from-hook, merged into next +- - 2008-07-30 23:41:56.898257 Z + - William Morgan + - closed with disposition fixed + - merged into master +git_branch: reply-from-hook diff --git a/bugs/issue-09479a2ada22c2a0d76427e12ef2514d4753d070.yaml b/bugs/issue-09479a2ada22c2a0d76427e12ef2514d4753d070.yaml new file mode 100644 index 0000000..94aa231 --- /dev/null +++ b/bugs/issue-09479a2ada22c2a0d76427e12ef2514d4753d070.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: forwarded messages should be threaded under original +desc: "" +type: :feature +component: threading +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-06-07 23:45:11.606455 Z +references: [] + +id: 09479a2ada22c2a0d76427e12ef2514d4753d070 +log_events: +- - 2008-06-07 23:45:12.746568 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-15738247f939d20f8f202f80ccb85d9ad92101e0.yaml b/bugs/issue-15738247f939d20f8f202f80ccb85d9ad92101e0.yaml new file mode 100644 index 0000000..3c780b9 --- /dev/null +++ b/bugs/issue-15738247f939d20f8f202f80ccb85d9ad92101e0.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: command to reload hooks +desc: useful for debugging hooks without having to restart sup each time +type: :feature +component: hooks +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-09 06:09:46.127686 Z +references: [] + +id: 15738247f939d20f8f202f80ccb85d9ad92101e0 +log_events: +- - 2008-05-09 06:09:46.803222 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-182841e15d6909892adf43678bae03597ce10519.yaml b/bugs/issue-182841e15d6909892adf43678bae03597ce10519.yaml new file mode 100644 index 0000000..b680b9d --- /dev/null +++ b/bugs/issue-182841e15d6909892adf43678bae03597ce10519.yaml @@ -0,0 +1,25 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: external mime viewing logic not quite right +desc: |- + weird things happen depending on the specifics on whether you have + certain binaries in your path, or you implement the mime-view hook, + you can get very weird behavior +type: :bugfix +component: hooks +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:05:53.956188 Z +references: [] + +id: 182841e15d6909892adf43678bae03597ce10519 +log_events: +- - 2008-03-07 04:05:53.956222 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:06:02.239869 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-1a1527438c2d198eae9a264ce9e6b847854d9837.yaml b/bugs/issue-1a1527438c2d198eae9a264ce9e6b847854d9837.yaml new file mode 100644 index 0000000..87d0472 --- /dev/null +++ b/bugs/issue-1a1527438c2d198eae9a264ce9e6b847854d9837.yaml @@ -0,0 +1,30 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: attachment name searchability +desc: "" +type: :feature +component: indexing +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-25 03:53:44.524558 Z +references: [] + +id: 1a1527438c2d198eae9a264ce9e6b847854d9837 +log_events: +- - 2008-05-25 03:53:45.177580 Z + - William Morgan + - created + - "" +- - 2008-05-25 03:54:05.978412 Z + - William Morgan + - changed status from unstarted to in_progress + - branch attachments, merged into next +- - 2008-05-31 17:09:04.254381 Z + - William Morgan + - commented + - see {issue 65506670167642cc581956bc1b25c26b5bff215b} and {issue 7a68c1e7120a8540c7c51c6095f4815918d16641} +- - 2008-06-19 18:20:41.656527 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-2312263b6a2b7de6ae1ec4ab315c7829763e61be.yaml b/bugs/issue-2312263b6a2b7de6ae1ec4ab315c7829763e61be.yaml new file mode 100644 index 0000000..38364d9 --- /dev/null +++ b/bugs/issue-2312263b6a2b7de6ae1ec4ab315c7829763e61be.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: sup-sync-back "nothing to do" error message not informative +desc: should tell the user that one of the four magic options are required +type: :bugfix +component: sup-sync-back +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 03:37:41.693484 Z +references: [] + +id: 2312263b6a2b7de6ae1ec4ab315c7829763e61be +log_events: +- - 2008-03-07 03:37:41.693520 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:37:46.110644 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-23658477a445c2e61405fecb4cb641a2298caba6.yaml b/bugs/issue-23658477a445c2e61405fecb4cb641a2298caba6.yaml new file mode 100644 index 0000000..91e661a --- /dev/null +++ b/bugs/issue-23658477a445c2e61405fecb4cb641a2298caba6.yaml @@ -0,0 +1,27 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: wide character ncurses support +desc: "" +type: :feature +component: curses +release: +reporter: William Morgan +status: :in_progress +disposition: +creation_time: 2008-04-22 22:43:23.153185 Z +references: [] + +id: 23658477a445c2e61405fecb4cb641a2298caba6 +log_events: +- - 2008-04-22 22:43:24.808717 Z + - William Morgan + - created + - "" +- - 2008-04-22 22:45:52.511820 Z + - William Morgan + - changed status from unstarted to in_progress + - |- + Branch 'ncurses-widechar' has been merged into next. + + Branch "ncursesw" now has a copy of the ncurses 0.9.2 gem with wide character + modifications, and a script "run-this-for-sup.sh" to build and install it + (assuming you're running from git, of course.) diff --git a/bugs/issue-2a0363cdf9d25edfa2a04b21299a538365e8b319.yaml b/bugs/issue-2a0363cdf9d25edfa2a04b21299a538365e8b319.yaml new file mode 100644 index 0000000..09ffc12 --- /dev/null +++ b/bugs/issue-2a0363cdf9d25edfa2a04b21299a538365e8b319.yaml @@ -0,0 +1,25 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: gpg mode hook +desc: |- + need a hook for controlling the default setting of the gpg mode (none, + sign, sign & encrypt) in reply-mode, based on the gpg mode of the original + message. +type: :feature +component: hooks +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-07 02:42:29.391022 Z +references: [] + +id: 2a0363cdf9d25edfa2a04b21299a538365e8b319 +log_events: +- - 2008-03-07 02:42:29.391058 Z + - William Morgan + - created + - "" +- - 2008-04-20 21:18:14.263736 Z + - William Morgan + - assigned to release 0.6 from 0.5 + - "" diff --git a/bugs/issue-2e74aa6843feee4daefe740b6e3f1fc54ff4bfcb.yaml b/bugs/issue-2e74aa6843feee4daefe740b6e3f1fc54ff4bfcb.yaml new file mode 100644 index 0000000..87252e4 --- /dev/null +++ b/bugs/issue-2e74aa6843feee4daefe740b6e3f1fc54ff4bfcb.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: oldest-first thread ordering +desc: "" +type: :feature +component: indexing +release: +reporter: Matt Liggett +status: :unstarted +disposition: +creation_time: 2008-03-14 18:33:01.603318 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-March/001271.html +id: 2e74aa6843feee4daefe740b6e3f1fc54ff4bfcb +log_events: +- - 2008-03-14 18:33:01.603569 Z + - William Morgan + - created + - "" +- - 2008-03-14 18:33:31.116057 Z + - William Morgan + - added reference 1 + - "" diff --git a/bugs/issue-314f0cdac8d1998c46759a4ebef9077999bcef09.yaml b/bugs/issue-314f0cdac8d1998c46759a4ebef9077999bcef09.yaml new file mode 100644 index 0000000..431a522 --- /dev/null +++ b/bugs/issue-314f0cdac8d1998c46759a4ebef9077999bcef09.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: new user welcome screen the first time you start up +desc: "" +type: :feature +component: curses +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-07 02:44:24.399133 Z +references: [] + +id: 314f0cdac8d1998c46759a4ebef9077999bcef09 +log_events: +- - 2008-03-07 02:44:24.399167 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-3408c200a5f47f92d12b5c063a00ce891c2ba4ce.yaml b/bugs/issue-3408c200a5f47f92d12b5c063a00ce891c2ba4ce.yaml new file mode 100644 index 0000000..cde47bd --- /dev/null +++ b/bugs/issue-3408c200a5f47f92d12b5c063a00ce891c2ba4ce.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "email header parsing: space doesn't need to follow colon" +desc: "" +type: :bugfix +component: sup +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:31:55.733379 Z +references: [] + +id: 3408c200a5f47f92d12b5c063a00ce891c2ba4ce +log_events: +- - 2008-03-07 04:31:55.733416 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:31:59.580856 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-3441fb8b7f955d625633d06fa0bf67a9afab046e.yaml b/bugs/issue-3441fb8b7f955d625633d06fa0bf67a9afab046e.yaml new file mode 100644 index 0000000..bd3c0fe --- /dev/null +++ b/bugs/issue-3441fb8b7f955d625633d06fa0bf67a9afab046e.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: saving a message as a draft drops attachments +desc: "" +type: :bugfix +component: sup +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-25 02:14:13.362087 Z +references: [] + +id: 3441fb8b7f955d625633d06fa0bf67a9afab046e +log_events: +- - 2008-05-25 02:14:14.224040 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-38d6f805b0c8bad013ec73f56e6245c890528591.yaml b/bugs/issue-38d6f805b0c8bad013ec73f56e6245c890528591.yaml new file mode 100644 index 0000000..635bd65 --- /dev/null +++ b/bugs/issue-38d6f805b0c8bad013ec73f56e6245c890528591.yaml @@ -0,0 +1,29 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "'m' in edit-message-mode should prompt for a to: with a default" +desc: |- + the current behavior is to just go ahead and compose the message, which + is irritating if you're just trying to compose a message incidental to + having highlighted someone's email address. +type: :bugfix +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-03-07 02:37:38.905689 Z +references: [] + +id: 38d6f805b0c8bad013ec73f56e6245c890528591 +log_events: +- - 2008-03-07 02:37:38.905723 Z + - William Morgan + - created + - "" +- - 2008-04-20 21:44:06.473431 Z + - William Morgan + - assigned to release 0.6 from 0.5 + - "" +- - 2008-05-25 03:47:42.600153 Z + - William Morgan + - closed issue with disposition fixed + - fixed in master diff --git a/bugs/issue-3b25f1d56b9be533edaf232b9e60dc24e00cba0b.yaml b/bugs/issue-3b25f1d56b9be533edaf232b9e60dc24e00cba0b.yaml new file mode 100644 index 0000000..07ca173 --- /dev/null +++ b/bugs/issue-3b25f1d56b9be533edaf232b9e60dc24e00cba0b.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: maildir speedups +desc: caching mtimes, using dir mtimes as an upper bound on file mtimes +type: :feature +component: maildir +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-25 02:30:42.010965 Z +references: [] + +id: 3b25f1d56b9be533edaf232b9e60dc24e00cba0b +log_events: +- - 2008-05-25 02:30:42.815974 Z + - William Morgan + - created + - "" +- - 2008-05-25 02:30:59.062438 Z + - William Morgan + - changed status from unstarted to in_progress + - branch maildir-speedups. merged into next. +- - 2008-06-19 18:09:27.239553 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-42ab0840f9a1924f1c0561e8ddcf7e6988543ba0.yaml b/bugs/issue-42ab0840f9a1924f1c0561e8ddcf7e6988543ba0.yaml new file mode 100644 index 0000000..ba95c00 --- /dev/null +++ b/bugs/issue-42ab0840f9a1924f1c0561e8ddcf7e6988543ba0.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: query normalization breaking disjunctive queries, date modifers, etc +desc: "" +type: :bugfix +component: indexing +release: "0.5" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-03-07 03:39:26.683059 Z +references: [] + +id: 42ab0840f9a1924f1c0561e8ddcf7e6988543ba0 +log_events: +- - 2008-03-07 03:39:26.683093 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:50:16.796313 Z + - William Morgan + - changed status from unstarted to in_progress + - "" +- - 2008-04-20 22:10:39.075075 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-46df983ccdb75408a37b3911472d4015664a3cf6.yaml b/bugs/issue-46df983ccdb75408a37b3911472d4015664a3cf6.yaml new file mode 100644 index 0000000..5358756 --- /dev/null +++ b/bugs/issue-46df983ccdb75408a37b3911472d4015664a3cf6.yaml @@ -0,0 +1,20 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: curses interface generally sluggish +desc: |- + moving cursors around, etc is sluggish. should be faster. will require + profiling. might require dipping into the C level. +type: :bugfix +component: curses +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-19 23:38:35.608104 Z +references: [] + +id: 46df983ccdb75408a37b3911472d4015664a3cf6 +log_events: +- - 2008-05-19 23:38:36.229747 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-47aab6443b6c107c3067cdb614186099db570acf.yaml b/bugs/issue-47aab6443b6c107c3067cdb614186099db570acf.yaml new file mode 100644 index 0000000..ced024b --- /dev/null +++ b/bugs/issue-47aab6443b6c107c3067cdb614186099db570acf.yaml @@ -0,0 +1,37 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: before-add-hook not applied to sent messages +desc: |- + they're not being polled in the regular way but in a vestigal irregular + way +type: :bugfix +component: sup +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 03:54:10.773413 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-March/001259.html +- http://rubyforge.org/pipermail/sup-talk/2008-February/001203.html +id: 47aab6443b6c107c3067cdb614186099db570acf +log_events: +- - 2008-03-07 03:54:10.773449 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:54:15.699906 Z + - William Morgan + - changed status from unstarted to in_progress + - "" +- - 2008-03-08 22:02:45.840451 Z + - William Morgan + - changed status from in_progress to fixed + - merged down to master. +- - 2008-03-08 22:16:00.346710 Z + - William Morgan + - added reference 1 + - "" +- - 2008-03-08 22:22:02.528552 Z + - William Morgan + - added reference 2 + - "" diff --git a/bugs/issue-4af242013994ae557e431ba350a92c4f9e1739ef.yaml b/bugs/issue-4af242013994ae557e431ba350a92c4f9e1739ef.yaml new file mode 100644 index 0000000..db4b825 --- /dev/null +++ b/bugs/issue-4af242013994ae557e431ba350a92c4f9e1739ef.yaml @@ -0,0 +1,28 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: sup-sync shouldn't save the index and sources if an error occurred +desc: |- + If the error was caused by a particular message, saving the source file + will move the pointer past the message, so it will never get added. +type: :bugfix +component: sup-sync +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:14:07.913103 Z +references: [] + +id: 4af242013994ae557e431ba350a92c4f9e1739ef +log_events: +- - 2008-03-07 04:14:07.913140 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:14:12.599051 Z + - William Morgan + - changed status from unstarted to fixed + - "" +- - 2008-03-09 18:29:51.789364 Z + - William Morgan + - changed description + - "" diff --git a/bugs/issue-4daa2721dac8dfeb8730ee081f73b6c62702bd3e.yaml b/bugs/issue-4daa2721dac8dfeb8730ee081f73b6c62702bd3e.yaml new file mode 100644 index 0000000..e9605cc --- /dev/null +++ b/bugs/issue-4daa2721dac8dfeb8730ee081f73b6c62702bd3e.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: last message of every source is returned twice during polling +desc: http://rubyforge.org/pipermail/sup-talk/2008-April/001358.html +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-01 01:11:50.650800 Z +references: [] + +id: 4daa2721dac8dfeb8730ee081f73b6c62702bd3e +log_events: +- - 2008-05-01 01:11:51.434589 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-4e501973cea5bd1f28739ae4cea98edce8249895.yaml b/bugs/issue-4e501973cea5bd1f28739ae4cea98edce8249895.yaml new file mode 100644 index 0000000..1c3d0a4 --- /dev/null +++ b/bugs/issue-4e501973cea5bd1f28739ae4cea98edce8249895.yaml @@ -0,0 +1,32 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: thread joining is not preserved when reindexing +desc: | + the current thread joining just adds references to the index entries. that's + fine but if the messages are reindexed, the references obviously won't be + there. + i think we need to add some separate blob of information somewhere that + maintains these references, which sup-sync is aware of. + + if we're going down the bdb route for state preservation, that might be an + obvious place to put this too, because it's essentially a hashtable keyed on + message ids. + +type: :bugfix +component: indexing +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-14 18:39:59.697902 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-March/001270.html +id: 4e501973cea5bd1f28739ae4cea98edce8249895 +log_events: +- - 2008-03-14 18:39:59.698163 Z + - William Morgan + - created + - "" +- - 2008-03-14 18:40:26.559418 Z + - William Morgan + - added reference 1 + - "" diff --git a/bugs/issue-5348fec2b1112250e241afc7467de29e5691d1be.yaml b/bugs/issue-5348fec2b1112250e241afc7467de29e5691d1be.yaml new file mode 100644 index 0000000..64d84a2 --- /dev/null +++ b/bugs/issue-5348fec2b1112250e241afc7467de29e5691d1be.yaml @@ -0,0 +1,21 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: imap header caching +desc: |- + imap headers aren't cached at all. that would speed up the initial + connection, at least for servers that didn't set uid_validity to + the current time (blearf). +type: :feature +component: imap +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-07 04:26:31.474463 Z +references: [] + +id: 5348fec2b1112250e241afc7467de29e5691d1be +log_events: +- - 2008-03-07 04:26:31.474497 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-57668c69d0190d6e849309834d4ad1d215efa779.yaml b/bugs/issue-57668c69d0190d6e849309834d4ad1d215efa779.yaml new file mode 100644 index 0000000..fcb39c1 --- /dev/null +++ b/bugs/issue-57668c69d0190d6e849309834d4ad1d215efa779.yaml @@ -0,0 +1,21 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: make sup-sync-back work on Maildir folders +desc: |- + possibly we could abstract things entirely between mbox and maildir, but + it might just be easiest to have a sup-sync-back-maildir or a big if + statement. +type: :feature +component: sup-sync-back +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-06-12 19:24:51.772444 Z +references: [] + +id: 57668c69d0190d6e849309834d4ad1d215efa779 +log_events: +- - 2008-06-12 19:24:53.668373 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-5795c3c1b47e88f7261f57f31d33fe15ad08465d.yaml b/bugs/issue-5795c3c1b47e88f7261f57f31d33fe15ad08465d.yaml new file mode 100644 index 0000000..8f774aa --- /dev/null +++ b/bugs/issue-5795c3c1b47e88f7261f57f31d33fe15ad08465d.yaml @@ -0,0 +1,20 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: flat (gmail-style) version of thread-view-mode +desc: |- + make thread-view-mode show a flat, chronological list of messages + instead of a tree, based on some configuration variable. +type: :feature +component: curses +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-25 02:38:06.098950 Z +references: [] + +id: 5795c3c1b47e88f7261f57f31d33fe15ad08465d +log_events: +- - 2008-05-25 02:38:06.823848 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-5fab957dcd16f1da8962fe5b1f3a58d970315deb.yaml b/bugs/issue-5fab957dcd16f1da8962fe5b1f3a58d970315deb.yaml new file mode 100644 index 0000000..7c3c725 --- /dev/null +++ b/bugs/issue-5fab957dcd16f1da8962fe5b1f3a58d970315deb.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: extra-contact-addresses hook for lbdb (etc.) integration +desc: |- + add an extra-contact-addresses hook for inserting addresses into the + tab-completion list for To:, Cc:, etc. entries. +type: :feature +component: hooks +release: "0.5" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-04-20 20:43:06.972853 Z +references: [] + +id: 5fab957dcd16f1da8962fe5b1f3a58d970315deb +log_events: +- - 2008-04-20 20:43:08.667355 Z + - William Morgan + - created + - "" +- - 2008-04-20 20:43:20.678566 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-60d86dd32054533a6206f698033ec668af6a7574.yaml b/bugs/issue-60d86dd32054533a6206f698033ec668af6a7574.yaml new file mode 100644 index 0000000..ac7e701 --- /dev/null +++ b/bugs/issue-60d86dd32054533a6206f698033ec668af6a7574.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: killed threads showing up in inbox-mode +desc: this goddamn problem is recurring +type: :bugfix +component: indexing +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-04-25 19:28:51.369257 Z +references: [] + +id: 60d86dd32054533a6206f698033ec668af6a7574 +log_events: +- - 2008-04-25 19:28:52.476687 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-61949ec83770b5d46f89eff21799968187012cce.yaml b/bugs/issue-61949ec83770b5d46f89eff21799968187012cce.yaml new file mode 100644 index 0000000..fb3df1a --- /dev/null +++ b/bugs/issue-61949ec83770b5d46f89eff21799968187012cce.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: \127 should be handled like backspace (it's the 70's all over again) +desc: "" +type: :bugfix +component: curses +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:29:46.043812 Z +references: [] + +id: 61949ec83770b5d46f89eff21799968187012cce +log_events: +- - 2008-03-07 04:29:46.043850 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:29:52.233706 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-65506670167642cc581956bc1b25c26b5bff215b.yaml b/bugs/issue-65506670167642cc581956bc1b25c26b5bff215b.yaml new file mode 100644 index 0000000..e43d6af --- /dev/null +++ b/bugs/issue-65506670167642cc581956bc1b25c26b5bff215b.yaml @@ -0,0 +1,30 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: attachment markers in thread-index-mode +desc: show a little @ if the message has an attachment +type: :feature +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-25 03:53:10.005404 Z +references: [] + +id: 65506670167642cc581956bc1b25c26b5bff215b +log_events: +- - 2008-05-25 03:53:10.994290 Z + - William Morgan + - created + - "" +- - 2008-05-25 03:53:26.388023 Z + - William Morgan + - changed status from unstarted to in_progress + - branch attachments, merged into next +- - 2008-05-31 17:09:17.710631 Z + - William Morgan + - commented + - see {issue 1a1527438c2d198eae9a264ce9e6b847854d9837} and {issue 7a68c1e7120a8540c7c51c6095f4815918d16641} +- - 2008-06-19 18:20:33.912937 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-658389418b5f0038cc3e6bc20fd3fd1566eb7111.yaml b/bugs/issue-658389418b5f0038cc3e6bc20fd3fd1566eb7111.yaml new file mode 100644 index 0000000..26ce1e8 --- /dev/null +++ b/bugs/issue-658389418b5f0038cc3e6bc20fd3fd1566eb7111.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: add a startup hook +desc: "" +type: :feature +component: hooks +release: "0.5" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-03-07 04:03:52.999956 Z +references: [] + +id: 658389418b5f0038cc3e6bc20fd3fd1566eb7111 +log_events: +- - 2008-03-07 04:03:52.999992 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:03:56.880347 Z + - William Morgan + - changed status from unstarted to in_progress + - "" +- - 2008-04-20 20:45:20.047253 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-69f785cddcc6e09ef0a357151373b3aa923d5e3f.yaml b/bugs/issue-69f785cddcc6e09ef0a357151373b3aa923d5e3f.yaml new file mode 100644 index 0000000..6a6f488 --- /dev/null +++ b/bugs/issue-69f785cddcc6e09ef0a357151373b3aa923d5e3f.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: escape filenames in call to run-mailcap +desc: otherwise, filenames with spaces don't work +type: :bugfix +component: sup +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:10:43.771843 Z +references: [] + +id: 69f785cddcc6e09ef0a357151373b3aa923d5e3f +log_events: +- - 2008-03-07 04:10:43.771878 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:10:48.789189 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-6c053cca2eb05af486a2d09c6772fd5bd0cca444.yaml b/bugs/issue-6c053cca2eb05af486a2d09c6772fd5bd0cca444.yaml new file mode 100644 index 0000000..bbdf1c6 --- /dev/null +++ b/bugs/issue-6c053cca2eb05af486a2d09c6772fd5bd0cca444.yaml @@ -0,0 +1,20 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: cache threading +desc: |- + thread information should be cached so that it doesn't have to be + recomputed each time. +type: :feature +component: threading +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-19 23:39:19.716625 Z +references: [] + +id: 6c053cca2eb05af486a2d09c6772fd5bd0cca444 +log_events: +- - 2008-05-19 23:39:20.190260 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-6e0d634de74b2eb8297174ecd408b3810ba9351b.yaml b/bugs/issue-6e0d634de74b2eb8297174ecd408b3810ba9351b.yaml new file mode 100644 index 0000000..564b3b1 --- /dev/null +++ b/bugs/issue-6e0d634de74b2eb8297174ecd408b3810ba9351b.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: imap connection sharing +desc: | + current behavior is a separate connection for each folder, which is kinda + silly. + potentially want to still keep a separate connection for polling, but that + might be micro-optimization, especially given that the whole ruby imap + library seems quite slow. + +type: :feature +component: imap +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-07 04:25:12.351934 Z +references: [] + +id: 6e0d634de74b2eb8297174ecd408b3810ba9351b +log_events: +- - 2008-03-07 04:25:12.351966 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-6e7960514f66ee67da083bc7bb5632d5808fc607.yaml b/bugs/issue-6e7960514f66ee67da083bc7bb5632d5808fc607.yaml new file mode 100644 index 0000000..9656537 --- /dev/null +++ b/bugs/issue-6e7960514f66ee67da083bc7bb5632d5808fc607.yaml @@ -0,0 +1,30 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "'!!' will load all threads in current search" +desc: |- + can be dangerous, but sometimes you know there aren't a million and you + just want them all loaded, e.g. to apply some mass tagging operation. + with the cancel-search feature, can always be canceled if + onerous. +type: :feature +component: sup +release: "0.5" +reporter: Marcus Williams +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:17:44.706909 Z +references: [] + +id: 6e7960514f66ee67da083bc7bb5632d5808fc607 +log_events: +- - 2008-03-07 04:17:44.706948 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:17:48.834972 Z + - William Morgan + - changed status from unstarted to fixed + - "" +- - 2008-03-11 06:52:15.604233 Z + - William Morgan + - changed description + - "" diff --git a/bugs/issue-7456c2d8fbd5de4dac651f6f4e9756f577497e01.yaml b/bugs/issue-7456c2d8fbd5de4dac651f6f4e9756f577497e01.yaml new file mode 100644 index 0000000..915eb68 --- /dev/null +++ b/bugs/issue-7456c2d8fbd5de4dac651f6f4e9756f577497e01.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: edit-as-new doesn't preserve replyto and references headers +desc: "" +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-31 17:07:05.126884 Z +references: [] + +id: 7456c2d8fbd5de4dac651f6f4e9756f577497e01 +log_events: +- - 2008-05-31 17:07:07.008637 Z + - William Morgan + - created + - "" +- - 2008-05-31 17:07:22.611383 Z + - William Morgan + - changed status from unstarted to in_progress + - in branch edit-as-new-fix, merged into next +- - 2008-06-19 18:22:24.036557 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-76802330c4fdd091e8b1dd08dcc29ed432f003d4.yaml b/bugs/issue-76802330c4fdd091e8b1dd08dcc29ed432f003d4.yaml new file mode 100644 index 0000000..e219937 --- /dev/null +++ b/bugs/issue-76802330c4fdd091e8b1dd08dcc29ed432f003d4.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: in-buffer search always shifts the screen, even when unnecessary +desc: "" +type: :bugfix +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-01 22:34:01.983057 Z +references: [] + +id: 76802330c4fdd091e8b1dd08dcc29ed432f003d4 +log_events: +- - 2008-05-01 22:34:02.958758 Z + - William Morgan + - created + - "" +- - 2008-05-01 22:34:24.254778 Z + - William Morgan + - changed status from unstarted to in_progress + - branch find-in-buffer-fix, merged into next +- - 2008-05-25 04:19:45.168367 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-799771a6a435dcad66dc80e7e051d91d24d005b1.yaml b/bugs/issue-799771a6a435dcad66dc80e7e051d91d24d005b1.yaml new file mode 100644 index 0000000..f1f2397 --- /dev/null +++ b/bugs/issue-799771a6a435dcad66dc80e7e051d91d24d005b1.yaml @@ -0,0 +1,31 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: IMAP server restart crashes sup +desc: |- + this very bizarre backtrace: + + --- SystemExit from thread: main + closed stream + /usr/lib/ruby/1.8/openssl/buffering.rb:237:in `select' + ./lib/sup/buffer.rb:31:in `nonblocking_getch' + bin/sup:227 + + wtf? + + There's no reason that + nonblocking_getch would be calling the openssl stuff, and openssl's + buffering.rb doesn't mention select at all. Weird. +type: :bugfix +component: imap +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-19 23:17:32.271870 Z +references: [] + +id: 799771a6a435dcad66dc80e7e051d91d24d005b1 +log_events: +- - 2008-05-19 23:17:33.615525 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-7a68c1e7120a8540c7c51c6095f4815918d16641.yaml b/bugs/issue-7a68c1e7120a8540c7c51c6095f4815918d16641.yaml new file mode 100644 index 0000000..3892dc7 --- /dev/null +++ b/bugs/issue-7a68c1e7120a8540c7c51c6095f4815918d16641.yaml @@ -0,0 +1,28 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: attachment markers in thread-view-mode +desc: |- + i'd like to see them in thread-view-mode as well + (c.f. {issue 65506670167642cc581956bc1b25c26b5bff215b} and {issue 1a1527438c2d198eae9a264ce9e6b847854d9837}) +type: :feature +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-31 17:08:28.081944 Z +references: [] + +id: 7a68c1e7120a8540c7c51c6095f4815918d16641 +log_events: +- - 2008-05-31 17:08:28.710190 Z + - William Morgan + - created + - "" +- - 2008-05-31 17:08:50.679595 Z + - William Morgan + - changed status from unstarted to in_progress + - on branch attachments as well, remerged into next +- - 2008-06-19 18:20:56.657318 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-7c77e757321c2639daea013824ad1a14099815b1.yaml b/bugs/issue-7c77e757321c2639daea013824ad1a14099815b1.yaml new file mode 100644 index 0000000..ecc1ae8 --- /dev/null +++ b/bugs/issue-7c77e757321c2639daea013824ad1a14099815b1.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: in-buffer searches should move buffer horizontally when necessary +desc: "" +type: :feature +component: curses +release: "0.5" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-03-07 03:56:17.653639 Z +references: [] + +id: 7c77e757321c2639daea013824ad1a14099815b1 +log_events: +- - 2008-03-07 03:56:17.653674 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:56:21.870750 Z + - William Morgan + - changed status from unstarted to in_progress + - "" +- - 2008-04-20 20:44:07.668281 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-7d8474dfeeefaa50151c3ce48bee6b686d36a216.yaml b/bugs/issue-7d8474dfeeefaa50151c3ce48bee6b686d36a216.yaml new file mode 100644 index 0000000..a2906d8 --- /dev/null +++ b/bugs/issue-7d8474dfeeefaa50151c3ce48bee6b686d36a216.yaml @@ -0,0 +1,29 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: reply-to mode hook +desc: |- + need a hook for selecting the default setting of the reply-to + horizontal selector +type: :feature +component: hooks +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-06-04 03:04:10.253690 Z +references: [] + +id: 7d8474dfeeefaa50151c3ce48bee6b686d36a216 +log_events: +- - 2008-06-04 03:04:10.945071 Z + - William Morgan + - created + - "" +- - 2008-06-04 03:04:21.284329 Z + - William Morgan + - changed status from unstarted to in_progress + - branch 'reply-to-hook', merged into next +- - 2008-07-30 23:41:50.393799 Z + - William Morgan + - closed with disposition fixed + - merged into master +git_branch: reply-to-hook diff --git a/bugs/issue-829b449c51fca9a39047d00fabc552cc110c69b2.yaml b/bugs/issue-829b449c51fca9a39047d00fabc552cc110c69b2.yaml new file mode 100644 index 0000000..e17e213 --- /dev/null +++ b/bugs/issue-829b449c51fca9a39047d00fabc552cc110c69b2.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: don't crash when people.txt is corrupted +desc: |- + This was a debug check, but if Sup crashes when writing out people.txt, + this will prevent it from ever starting again! +type: :bugfix +component: sup +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:07:56.208521 Z +references: [] + +id: 829b449c51fca9a39047d00fabc552cc110c69b2 +log_events: +- - 2008-03-07 04:07:56.208558 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:21:04.553157 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-82c80f6dc2ce7b10b9e8f503d68253ced0ee8a1b.yaml b/bugs/issue-82c80f6dc2ce7b10b9e8f503d68253ced0ee8a1b.yaml new file mode 100644 index 0000000..86be9e0 --- /dev/null +++ b/bugs/issue-82c80f6dc2ce7b10b9e8f503d68253ced0ee8a1b.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: gpg generates invalid signature when :edit_signature is on +desc: |- + when :edit_signature is on and there's a signature, gpg signatures are invalid, + ccording to mutt and other clients. sup itself thinks they're fine. +type: :bugfix +component: crypto +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-19 21:19:23.267668 Z +references: [] + +id: 82c80f6dc2ce7b10b9e8f503d68253ced0ee8a1b +log_events: +- - 2008-05-19 21:19:24.611826 Z + - William Morgan + - created + - "" +- - 2008-05-19 21:19:49.649415 Z + - William Morgan + - closed issue with disposition fixed + - turns out it was a newline issue. patch directly applied to master. diff --git a/bugs/issue-8a5cf9242ca60fa6c81091e425f734b4fb03e41a.yaml b/bugs/issue-8a5cf9242ca60fa6c81091e425f734b4fb03e41a.yaml new file mode 100644 index 0000000..b91de0d --- /dev/null +++ b/bugs/issue-8a5cf9242ca60fa6c81091e425f734b4fb03e41a.yaml @@ -0,0 +1,53 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: index speedup +desc: | + I've just merged in a changeset that makes Sup store message body + content in the Ferret index. (They've always been indexed, but now + they're stored as well.) This means that changing the labels on a + message can be a copy operation of the previous Ferret document, rather + than requiring downloading and parsing the original message to create a + new Ferret document. + So, this should have two effects: + + 1. The Ferret index size will expand by about 50%. Sorry. + 2. Tweaking message labels should be much, much faster, since the + message no longer has to be downloaded from the source in order to + change the labels. If you've ever tried to label a large IMAP thread, + you no longer have to wait 5 minutes just to save. :) + + The index size increase is unfortunate, but it's something that has to + happen anyways if we want search-results-mode to have matching text in + the snippets, which is in the future TODO. + + The change was made in such a way that it's incrementally applied + whenever a message is saved or changed in the Ferret index. So, if you + want the above behavior on all messages immediately, you must do + sup-sync --all on a source (which will require downloading each + message). Otherwise, you will get the slow behavior (message body needs + to be downloaded from the source) the first time you save a message + after merging this change, and the fast behavior (no downloading + required) on all subsequent times. + +type: :feature +component: indexing +release: "0.5" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-03-07 02:48:23.885656 Z +references: [] + +id: 8a5cf9242ca60fa6c81091e425f734b4fb03e41a +log_events: +- - 2008-03-07 02:48:23.885693 Z + - William Morgan + - created + - "" +- - 2008-03-07 02:48:50.979828 Z + - William Morgan + - changed status from unstarted to in_progress + - "" +- - 2008-04-20 22:10:33.970635 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-8aa7ea95f066fd0668452093b85903bd142905c9.yaml b/bugs/issue-8aa7ea95f066fd0668452093b85903bd142905c9.yaml new file mode 100644 index 0000000..59c41c0 --- /dev/null +++ b/bugs/issue-8aa7ea95f066fd0668452093b85903bd142905c9.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "'q' asks and 'Q' quits without asking" +desc: "" +type: :feature +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-20 03:25:17.109472 Z +references: [] + +id: 8aa7ea95f066fd0668452093b85903bd142905c9 +log_events: +- - 2008-05-20 03:25:19.265580 Z + - William Morgan + - created + - "" +- - 2008-05-25 02:13:32.219668 Z + - William Morgan + - closed issue with disposition fixed + - fixed in master +- - 2008-05-25 02:13:40.344453 Z + - William Morgan + - assigned to release 0.6 from unassigned + - "" diff --git a/bugs/issue-8c0e627c500f679badca28f60ba76998fd65d46a.yaml b/bugs/issue-8c0e627c500f679badca28f60ba76998fd65d46a.yaml new file mode 100644 index 0000000..f31067e --- /dev/null +++ b/bugs/issue-8c0e627c500f679badca28f60ba76998fd65d46a.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: workaround for rubymail quoting bug in pgp MIME header +desc: gpg MIME headers are being double-quoted due to a rubymail bug +type: :bugfix +component: sup +release: "0.5" +reporter: Jan Spakula +status: :closed +disposition: fixed +creation_time: 2008-03-07 03:35:36.731751 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-February/001222.html +id: 8c0e627c500f679badca28f60ba76998fd65d46a +log_events: +- - 2008-03-07 03:35:36.731787 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:36:24.938159 Z + - William Morgan + - changed status from unstarted to fixed + - "" +- - 2008-03-08 22:22:59.515414 Z + - William Morgan + - added reference 1 + - "" diff --git a/bugs/issue-91e1549102c0bfa2c201476d9618f7d234d1a626.yaml b/bugs/issue-91e1549102c0bfa2c201476d9618f7d234d1a626.yaml new file mode 100644 index 0000000..ae6d02a --- /dev/null +++ b/bugs/issue-91e1549102c0bfa2c201476d9618f7d234d1a626.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: gpg should use exact match for email address +desc: otherwise substring matches can select the wrong key +type: :bugfix +component: crypto +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-25 02:15:58.006265 Z +references: [] + +id: 91e1549102c0bfa2c201476d9618f7d234d1a626 +log_events: +- - 2008-05-25 02:15:59.100203 Z + - William Morgan + - created + - "" +- - 2008-05-25 02:16:07.730483 Z + - William Morgan + - closed issue with disposition fixed + - fixed in master diff --git a/bugs/issue-9f7e28de46d74f7f1e445ae75ea4e230c7473374.yaml b/bugs/issue-9f7e28de46d74f7f1e445ae75ea4e230c7473374.yaml new file mode 100644 index 0000000..e711eea --- /dev/null +++ b/bugs/issue-9f7e28de46d74f7f1e445ae75ea4e230c7473374.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: threads with unsent draft messages are now shown in red +desc: "" +type: :feature +component: curses +release: "0.5" +reporter: Nicolas Pouillard +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:30:53.909487 Z +references: [] + +id: 9f7e28de46d74f7f1e445ae75ea4e230c7473374 +log_events: +- - 2008-03-07 04:30:53.909522 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:31:03.704713 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-a1a3427de5e8d4f74c0620f99e97ed92d21e924c.yaml b/bugs/issue-a1a3427de5e8d4f74c0620f99e97ed92d21e924c.yaml new file mode 100644 index 0000000..7c30f15 --- /dev/null +++ b/bugs/issue-a1a3427de5e8d4f74c0620f99e97ed92d21e924c.yaml @@ -0,0 +1,30 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: sup-config name guessing logic can generate nil and crash +desc: "" +type: :bugfix +component: sup +release: "0.5" +reporter: Jean-Hadrien CHABRAN +status: :closed +disposition: fixed +creation_time: 2008-03-09 17:45:46.095924 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-March/001260.html +id: a1a3427de5e8d4f74c0620f99e97ed92d21e924c +log_events: +- - 2008-03-09 17:45:46.095961 Z + - William Morgan + - created + - "" +- - 2008-03-09 17:46:21.702965 Z + - William Morgan + - added reference 1 + - "" +- - 2008-03-09 17:46:45.446763 Z + - William Morgan + - changed reporter + - "" +- - 2008-03-09 17:47:06.797832 Z + - William Morgan + - changed status from unstarted to fixed + - fixed in master diff --git a/bugs/issue-a1e622dbae0e1841b4d9a376d419aed1d91460e0.yaml b/bugs/issue-a1e622dbae0e1841b4d9a376d419aed1d91460e0.yaml new file mode 100644 index 0000000..aa6e31f --- /dev/null +++ b/bugs/issue-a1e622dbae0e1841b4d9a376d419aed1d91460e0.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: non-ascii characters in message id need to be normalized +desc: apparently this happens. in spam email, of course. +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-05-11 23:04:01.078305 Z +references: [] + +id: a1e622dbae0e1841b4d9a376d419aed1d91460e0 +log_events: +- - 2008-05-11 23:04:01.677838 Z + - William Morgan + - created + - "" +- - 2008-05-11 23:21:40.281018 Z + - William Morgan + - changed status from unstarted to in_progress + - branch non-ascii-message-id, merged into next +- - 2008-06-19 18:09:04.143173 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-a533480a30a18c3e823dbe20b759e1dcb32ca2b9.yaml b/bugs/issue-a533480a30a18c3e823dbe20b759e1dcb32ca2b9.yaml new file mode 100644 index 0000000..2021c6f --- /dev/null +++ b/bugs/issue-a533480a30a18c3e823dbe20b759e1dcb32ca2b9.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: forward/reply without saving in the editor drops all newlines +desc: "" +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-04-23 01:31:16.072859 Z +references: [] + +id: a533480a30a18c3e823dbe20b759e1dcb32ca2b9 +log_events: +- - 2008-04-23 01:31:16.640737 Z + - William Morgan + - created + - "" +- - 2008-04-23 01:39:10.304801 Z + - William Morgan + - changed status from unstarted to in_progress + - branch unedited-newlines, merged into next +- - 2008-05-25 04:22:44.178693 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-a68148169baa3838051f4bdb4c175e11cbf7f143.yaml b/bugs/issue-a68148169baa3838051f4bdb4c175e11cbf7f143.yaml new file mode 100644 index 0000000..e4ce8bf --- /dev/null +++ b/bugs/issue-a68148169baa3838051f4bdb4c175e11cbf7f143.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: all ferret access needs to be wrapped in a mutex +desc: |- + concurrent access breaks things. at least, that's what I *think* is + going on here. + + http://rubyforge.org/pipermail/sup-talk/2008-April/001333.html +type: :bugfix +component: indexing +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-01 01:09:39.706808 Z +references: [] + +id: a68148169baa3838051f4bdb4c175e11cbf7f143 +log_events: +- - 2008-05-01 01:09:40.747646 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-aae5ae6378afa9bd2a8e1b15d28ba7ccef867791.yaml b/bugs/issue-aae5ae6378afa9bd2a8e1b15d28ba7ccef867791.yaml new file mode 100644 index 0000000..ae2ebeb --- /dev/null +++ b/bugs/issue-aae5ae6378afa9bd2a8e1b15d28ba7ccef867791.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: remove email->name mapping +desc: it doesn't work and wouldn't buy that much even if it did +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-19 23:42:25.910550 Z +references: [] + +id: aae5ae6378afa9bd2a8e1b15d28ba7ccef867791 +log_events: +- - 2008-05-19 23:42:26.490587 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-ad82aa00f4064fc7e1332cee0dae2c2ae95bb217.yaml b/bugs/issue-ad82aa00f4064fc7e1332cee0dae2c2ae95bb217.yaml new file mode 100644 index 0000000..1802a8a --- /dev/null +++ b/bugs/issue-ad82aa00f4064fc7e1332cee0dae2c2ae95bb217.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: add more vi keys +desc: "" +type: :feature +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-04-26 22:23:43.675951 Z +references: [] + +id: ad82aa00f4064fc7e1332cee0dae2c2ae95bb217 +log_events: +- - 2008-04-26 22:23:44.484689 Z + - William Morgan + - created + - "" +- - 2008-04-26 22:24:00.893661 Z + - William Morgan + - changed status from unstarted to in_progress + - branch more-vi-keys. in next. +- - 2008-05-25 04:12:57.577438 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-b1f1579fd8350d8add15c5cb588169acfdc5ea24.yaml b/bugs/issue-b1f1579fd8350d8add15c5cb588169acfdc5ea24.yaml new file mode 100644 index 0000000..8c01f3a --- /dev/null +++ b/bugs/issue-b1f1579fd8350d8add15c5cb588169acfdc5ea24.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: offer to delete lockfile after trying to kill owner process +desc: |- + often the lockfile points to a dead process, so repeatedly offering to kill + it isn't all that useful. +type: :feature +component: sup +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-04-14 01:25:59.111165 Z +references: [] + +id: b1f1579fd8350d8add15c5cb588169acfdc5ea24 +log_events: +- - 2008-04-14 01:26:00.135062 Z + - William Morgan + - created + - "" +- - 2008-05-19 23:40:28.102694 Z + - William Morgan + - assigned to release 0.6 from unassigned + - "" diff --git a/bugs/issue-b80aa39ef3b8d33bd57e4988c55d89c7c0df5c96.yaml b/bugs/issue-b80aa39ef3b8d33bd57e4988c55d89c7c0df5c96.yaml new file mode 100644 index 0000000..f293a90 --- /dev/null +++ b/bugs/issue-b80aa39ef3b8d33bd57e4988c55d89c7c0df5c96.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: spurious messages appearing in inbox +desc: |- + this is because ThreadSet is claiming that non-relevant videos are actually + relevant +type: :bugfix +component: indexing +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 03:55:29.353904 Z +references: [] + +id: b80aa39ef3b8d33bd57e4988c55d89c7c0df5c96 +log_events: +- - 2008-03-07 03:55:29.353940 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:55:34.495965 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-bdd4415a9d4c8fd3602500111bf9268aa7c7c6a4.yaml b/bugs/issue-bdd4415a9d4c8fd3602500111bf9268aa7c7c6a4.yaml new file mode 100644 index 0000000..b8fc2ad --- /dev/null +++ b/bugs/issue-bdd4415a9d4c8fd3602500111bf9268aa7c7c6a4.yaml @@ -0,0 +1,27 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: configurable colors +desc: All colors should be user-configurable. +type: :feature +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-06-04 02:27:15.458560 Z +references: [] + +id: bdd4415a9d4c8fd3602500111bf9268aa7c7c6a4 +log_events: +- - 2008-06-04 02:27:16.721829 Z + - William Morgan + - created + - "" +- - 2008-06-04 02:27:27.256556 Z + - William Morgan + - changed status from unstarted to in_progress + - branch 'colors', merged into next. +- - 2008-07-30 23:41:33.553377 Z + - William Morgan + - closed with disposition fixed + - merged into master +git_branch: color diff --git a/bugs/issue-bff2527210b3aacae2f74029e5856fed82f1689c.yaml b/bugs/issue-bff2527210b3aacae2f74029e5856fed82f1689c.yaml new file mode 100644 index 0000000..802f1b0 --- /dev/null +++ b/bugs/issue-bff2527210b3aacae2f74029e5856fed82f1689c.yaml @@ -0,0 +1,33 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: wide characters break screen clearing +desc: |- + if you look at a message with wide characters using the new wide-char-aware + ncurses library, there will often be snippets of the previous screen + immediately to the right of the end of the lines that have wide characters + in them. + + some kind of line length issue maybe? (because everything is done in terms + of bytes still. thanks ruby!) +type: :bugfix +component: curses +release: +reporter: William Morgan +status: :closed +disposition: :wontfix +creation_time: 2008-04-26 21:35:31.519359 Z +references: [] + +id: bff2527210b3aacae2f74029e5856fed82f1689c +log_events: +- - 2008-04-26 21:35:32.384516 Z + - William Morgan + - created + - "" +- - 2008-04-26 21:44:04.152193 Z + - William Morgan + - unassigned from release 0.6 + - depends on {issue 23658477a445c2e61405fecb4cb641a2298caba6} and that's not necessarily destined for 0.6 yet. +- - 2008-04-28 02:36:51.698817 Z + - William Morgan + - closed issue with disposition wontfix + - dup of {issue c48f7fc58bba0b38ff6ae14cca01b08a5a7a6c33}. you'd think i'd'a remembered. diff --git a/bugs/issue-c48f7fc58bba0b38ff6ae14cca01b08a5a7a6c33.yaml b/bugs/issue-c48f7fc58bba0b38ff6ae14cca01b08a5a7a6c33.yaml new file mode 100644 index 0000000..b15f04a --- /dev/null +++ b/bugs/issue-c48f7fc58bba0b38ff6ae14cca01b08a5a7a6c33.yaml @@ -0,0 +1,21 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: wide characters screw up line cursor display +desc: |- + in a message with wide characters, the screen isn't cleared properly, or + something. probably due to the # of characters for something being calculated + wrong (bytes instead of chars). +type: :bugfix +component: curses +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-04-23 02:05:47.272610 Z +references: [] + +id: c48f7fc58bba0b38ff6ae14cca01b08a5a7a6c33 +log_events: +- - 2008-04-23 02:05:49.360399 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-c52f9762bc24a8f45863eb2e7beefa4201db34e8.yaml b/bugs/issue-c52f9762bc24a8f45863eb2e7beefa4201db34e8.yaml new file mode 100644 index 0000000..b5b573f --- /dev/null +++ b/bugs/issue-c52f9762bc24a8f45863eb2e7beefa4201db34e8.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: add a --compose option to spawn a compose-message buffer on startup +desc: "" +type: :feature +component: sup +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:28:32.198492 Z +references: [] + +id: c52f9762bc24a8f45863eb2e7beefa4201db34e8 +log_events: +- - 2008-03-07 04:28:32.198527 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:28:37.471873 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-c660ddfa9d633501140dd199bdfd7cd9fed5df0b.yaml b/bugs/issue-c660ddfa9d633501140dd199bdfd7cd9fed5df0b.yaml new file mode 100644 index 0000000..56c68c5 --- /dev/null +++ b/bugs/issue-c660ddfa9d633501140dd199bdfd7cd9fed5df0b.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: ctrl-g should interrupt thread search operation +desc: "" +type: :feature +component: sup +release: "0.5" +reporter: Marcus Williams +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:15:47.155992 Z +references: [] + +id: c660ddfa9d633501140dd199bdfd7cd9fed5df0b +log_events: +- - 2008-03-07 04:15:47.156031 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:15:52.274258 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-cef3096582de268c050f78223eb6a22ac2599606.yaml b/bugs/issue-cef3096582de268c050f78223eb6a22ac2599606.yaml new file mode 100644 index 0000000..1881fc4 --- /dev/null +++ b/bugs/issue-cef3096582de268c050f78223eb6a22ac2599606.yaml @@ -0,0 +1,31 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: ruby 1.8.7 breaks sup in weird ways +desc: |- + --- ArgumentError from thread: main + wrong number of arguments (2 for 1) + /home/benjamin/projects/sup/lib/sup/index.rb:422:in `respond_to?' + /home/benjamin/projects/sup/lib/sup/index.rb:422:in `flatten' + /home/benjamin/projects/sup/lib/sup/index.rb:422:in `load_sources' + /home/benjamin/projects/sup/lib/sup/index.rb:108:in `load' + /home/benjamin/projects/sup/lib/sup/util.rb:497:in `send' + /home/benjamin/projects/sup/lib/sup/util.rb:497:in `method_missing' + /home/benjamin/projects/sup/bin/sup:122 +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-06-04 17:39:39.013305 Z +references: [] + +id: cef3096582de268c050f78223eb6a22ac2599606 +log_events: +- - 2008-06-04 17:39:39.670176 Z + - William Morgan + - created + - "" +- - 2008-06-19 17:57:46.648682 Z + - William Morgan + - closed issue with disposition fixed + - fixed directly in master diff --git a/bugs/issue-cf09ec6ec7c35d7d8c002b0521f97b6e94dc9b3e.yaml b/bugs/issue-cf09ec6ec7c35d7d8c002b0521f97b6e94dc9b3e.yaml new file mode 100644 index 0000000..bbba370 --- /dev/null +++ b/bugs/issue-cf09ec6ec7c35d7d8c002b0521f97b6e94dc9b3e.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: invalid gecos can cause sup-config to crash +desc: "" +type: :bugfix +component: sup +release: "0.5" +reporter: Jean-Hadrien CHABRAN +status: :closed +disposition: fixed +creation_time: 2008-03-14 18:54:32.560987 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-March/001260.html +id: cf09ec6ec7c35d7d8c002b0521f97b6e94dc9b3e +log_events: +- - 2008-03-14 18:54:32.561241 Z + - William Morgan + - created + - "" +- - 2008-03-14 18:54:52.486259 Z + - William Morgan + - added reference 1 + - "" +- - 2008-03-14 18:55:10.323790 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-cfbfc65dc90280fa5ecc63094af01d2a47ff0c6e.yaml b/bugs/issue-cfbfc65dc90280fa5ecc63094af01d2a47ff0c6e.yaml new file mode 100644 index 0000000..5db69fa --- /dev/null +++ b/bugs/issue-cfbfc65dc90280fa5ecc63094af01d2a47ff0c6e.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: exception thrown when a forwarded attachment is not a known mime type +desc: a minor typo +type: :bugfix +component: sup +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-04-23 01:23:06.368926 Z +references: [] + +id: cfbfc65dc90280fa5ecc63094af01d2a47ff0c6e +log_events: +- - 2008-04-23 01:23:07.968757 Z + - William Morgan + - created + - "" +- - 2008-04-23 01:23:14.995087 Z + - William Morgan + - closed issue with disposition fixed + - fixed in master diff --git a/bugs/issue-d131464e921aefc35571c119aac4d9f1decdebae.yaml b/bugs/issue-d131464e921aefc35571c119aac4d9f1decdebae.yaml new file mode 100644 index 0000000..d49dcaf --- /dev/null +++ b/bugs/issue-d131464e921aefc35571c119aac4d9f1decdebae.yaml @@ -0,0 +1,30 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: blank message-id headers are treated as valid and crash indexing +desc: |- + specifically, they trigger the "just added message to index" debug exception + because the id consists of nothing but spaces. + + header parsing needs to be fixed to not grab headers that are empty. +type: :bugfix +component: mbox +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-04-26 21:07:33.463910 Z +references: [] + +id: d131464e921aefc35571c119aac4d9f1decdebae +log_events: +- - 2008-04-26 21:07:34.221325 Z + - William Morgan + - created + - "" +- - 2008-04-26 21:41:55.731750 Z + - William Morgan + - changed status from unstarted to in_progress + - branch header-parsing-fix. merged into next. +- - 2008-05-25 04:19:15.986573 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/issue-d994a360c9cb2a6e12a734962a39ffbc6486a725.yaml b/bugs/issue-d994a360c9cb2a6e12a734962a39ffbc6486a725.yaml new file mode 100644 index 0000000..3dbffee --- /dev/null +++ b/bugs/issue-d994a360c9cb2a6e12a734962a39ffbc6486a725.yaml @@ -0,0 +1,29 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: flags need a separate backup outside of the ferret index +desc: | + Ferret still occasionally barfs and corrupts its own index. Currently all + user state is stored in the index and only in the index, so that means + you lose big-time if that happens. You can sup-dump your labels, but really, + how often are you going to do that. + Sup should maintain a separate backup of all labels in some fast on-disk + hashtable (message ids to label sets). Bdb comes to mind. + +type: :feature +component: sup +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-07 04:22:50.236621 Z +references: [] + +id: d994a360c9cb2a6e12a734962a39ffbc6486a725 +log_events: +- - 2008-03-07 04:22:50.236657 Z + - William Morgan + - created + - "" +- - 2008-04-20 21:44:51.655741 Z + - William Morgan + - assigned to release 0.6 from 0.5 + - "" diff --git a/bugs/issue-d9e6be1b524c6c0a5c31c9c468bda170c2a8cb58.yaml b/bugs/issue-d9e6be1b524c6c0a5c31c9c468bda170c2a8cb58.yaml new file mode 100644 index 0000000..3909db1 --- /dev/null +++ b/bugs/issue-d9e6be1b524c6c0a5c31c9c468bda170c2a8cb58.yaml @@ -0,0 +1,28 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: temp files disappear on sup crash +desc: |- + because we're using the Tempfile library, Sup crashes mean that tempfiles + containing message bodies are lost. Sup needs to manage its own tempfiles. +type: :bugfix +component: sup +release: "0.6" +reporter: "Marko Myllym\xC3\xA4ki " +status: :unstarted +disposition: +creation_time: 2008-03-07 04:59:51.404664 Z +references: +- http://rubyforge.org/pipermail/sup-talk/2008-February/001174.html +id: d9e6be1b524c6c0a5c31c9c468bda170c2a8cb58 +log_events: +- - 2008-03-07 04:59:51.404701 Z + - William Morgan + - created + - "" +- - 2008-03-11 06:20:47.540967 Z + - William Morgan + - added reference 1 + - "" +- - 2008-04-20 21:45:00.615452 Z + - William Morgan + - assigned to release 0.6 from 0.5 + - "" diff --git a/bugs/issue-e43b18777ea3aef3566bd80acd126e9ef8a5883a.yaml b/bugs/issue-e43b18777ea3aef3566bd80acd126e9ef8a5883a.yaml new file mode 100644 index 0000000..0216c8b --- /dev/null +++ b/bugs/issue-e43b18777ea3aef3566bd80acd126e9ef8a5883a.yaml @@ -0,0 +1,34 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: long message ids (>255 characters) never get matched by ferret +desc: | + this is a ferret bug. + Apparently, constructing a TermQuery object with a field value of more than + 255 characters never successfully matches. + + This is not a good long-term solution. A good one would be to take the SHA1 + of every message id instead. That will require an index rebuild, so I will + save that patch until later. + +type: :bugfix +component: indexing +release: "0.5" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-03-07 03:40:55.475449 Z +references: [] + +id: e43b18777ea3aef3566bd80acd126e9ef8a5883a +log_events: +- - 2008-03-07 03:40:55.475485 Z + - William Morgan + - created + - "" +- - 2008-03-07 03:50:18.590242 Z + - William Morgan + - changed status from unstarted to in_progress + - "" +- - 2008-04-20 22:10:44.010446 Z + - William Morgan + - closed issue with disposition fixed + - "" diff --git a/bugs/issue-e7739718b4dbf49bbd3dd47133affbf7cb1e2361.yaml b/bugs/issue-e7739718b4dbf49bbd3dd47133affbf7cb1e2361.yaml new file mode 100644 index 0000000..5e471f9 --- /dev/null +++ b/bugs/issue-e7739718b4dbf49bbd3dd47133affbf7cb1e2361.yaml @@ -0,0 +1,24 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "maildir speedup: don't scan directory except when polling" +desc: |- + lots of useless scanning. removing it should make things faster for large + maildirs. +type: :feature +component: maildir +release: "0.5" +reporter: William Morgan +status: :closed +disposition: fixed +creation_time: 2008-03-07 04:20:32.735159 Z +references: [] + +id: e7739718b4dbf49bbd3dd47133affbf7cb1e2361 +log_events: +- - 2008-03-07 04:20:32.735194 Z + - William Morgan + - created + - "" +- - 2008-03-07 04:20:37.257919 Z + - William Morgan + - changed status from unstarted to fixed + - "" diff --git a/bugs/issue-e9c2f66a7ff4fb4525c2719e77ac8eedf3835dfd.yaml b/bugs/issue-e9c2f66a7ff4fb4525c2719e77ac8eedf3835dfd.yaml new file mode 100644 index 0000000..f0ffc9d --- /dev/null +++ b/bugs/issue-e9c2f66a7ff4fb4525c2719e77ac8eedf3835dfd.yaml @@ -0,0 +1,20 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: force hook reload feature +desc: |- + would be nice for hook debugging. otherwise you have to restart sup + each time. +type: :feature +component: hooks +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-05-19 23:19:38.202269 Z +references: [] + +id: e9c2f66a7ff4fb4525c2719e77ac8eedf3835dfd +log_events: +- - 2008-05-19 23:19:38.757600 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-f767a9d2071da7b0f66698ce74e642bf347be96b.yaml b/bugs/issue-f767a9d2071da7b0f66698ce74e642bf347be96b.yaml new file mode 100644 index 0000000..ce4ef23 --- /dev/null +++ b/bugs/issue-f767a9d2071da7b0f66698ce74e642bf347be96b.yaml @@ -0,0 +1,21 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: mbox file handle closing +desc: |- + currently an open file handle is maintained for every single mbox folder. + (well, every one that's accessed by polling or by opening a message therefrom.) + that is plum crazy. +type: :feature +component: mbox +release: +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-03-07 04:27:35.146273 Z +references: [] + +id: f767a9d2071da7b0f66698ce74e642bf347be96b +log_events: +- - 2008-03-07 04:27:35.146307 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-fd7c7a7d7caf41ff20e7d10ca3f074fc02c14a5b.yaml b/bugs/issue-fd7c7a7d7caf41ff20e7d10ca3f074fc02c14a5b.yaml new file mode 100644 index 0000000..3ebebf7 --- /dev/null +++ b/bugs/issue-fd7c7a7d7caf41ff20e7d10ca3f074fc02c14a5b.yaml @@ -0,0 +1,25 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: thread joining doesn't always work +desc: | + sometimes it works, and sometimes it doesn't, and i haven't found the + pattern yet. + + also, UpdateManager isn't being called properly (maybe even needs a + custom event). e.g. if you join in search-results-mode, the results + aren't joined in inbox-mode. + +type: :bugfix +component: indexing +release: "0.6" +reporter: William Morgan +status: :unstarted +disposition: +creation_time: 2008-04-29 00:09:38.366801 Z +references: [] + +id: fd7c7a7d7caf41ff20e7d10ca3f074fc02c14a5b +log_events: +- - 2008-04-29 00:09:38.998592 Z + - William Morgan + - created + - "" diff --git a/bugs/issue-fdfc906e8f4f6eb10f1ebdf39c416415d9ab6af9.yaml b/bugs/issue-fdfc906e8f4f6eb10f1ebdf39c416415d9ab6af9.yaml new file mode 100644 index 0000000..99cbd3e --- /dev/null +++ b/bugs/issue-fdfc906e8f4f6eb10f1ebdf39c416415d9ab6af9.yaml @@ -0,0 +1,26 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: archive-and-mark-read command in inbox-mode +desc: "" +type: :feature +component: curses +release: "0.6" +reporter: William Morgan +status: :closed +disposition: :fixed +creation_time: 2008-04-26 23:32:53.791207 Z +references: [] + +id: fdfc906e8f4f6eb10f1ebdf39c416415d9ab6af9 +log_events: +- - 2008-04-26 23:32:57.083084 Z + - William Morgan + - created + - "" +- - 2008-04-26 23:33:12.980220 Z + - William Morgan + - changed status from unstarted to in_progress + - branch read-and-archive. in next. +- - 2008-05-25 04:14:48.307896 Z + - William Morgan + - closed issue with disposition fixed + - merged into master diff --git a/bugs/project.yaml b/bugs/project.yaml new file mode 100644 index 0000000..d23fc1a --- /dev/null +++ b/bugs/project.yaml @@ -0,0 +1,49 @@ +--- !ditz.rubyforge.org,2008-03-06/project +name: sup +version: 0.0.1 +components: +- !ditz.rubyforge.org,2008-03-06/component + name: sup +- !ditz.rubyforge.org,2008-03-06/component + name: threading +- !ditz.rubyforge.org,2008-03-06/component + name: indexing +- !ditz.rubyforge.org,2008-03-06/component + name: curses +- !ditz.rubyforge.org,2008-03-06/component + name: hooks +- !ditz.rubyforge.org,2008-03-06/component + name: sup-sync +- !ditz.rubyforge.org,2008-03-06/component + name: sup-sync-back +- !ditz.rubyforge.org,2008-03-06/component + name: maildir +- !ditz.rubyforge.org,2008-03-06/component + name: imap +- !ditz.rubyforge.org,2008-03-06/component + name: mbox +- !ditz.rubyforge.org,2008-03-06/component + name: crypto +releases: +- !ditz.rubyforge.org,2008-03-06/release + name: "0.5" + status: :released + release_time: 2008-04-22 15:55:47.323776 Z + log_events: + - - 2008-03-07 02:37:54.903172 Z + - William Morgan + - created + - "" + - - 2008-04-22 15:55:47.323829 Z + - William Morgan + - released + - "" +- !ditz.rubyforge.org,2008-03-06/release + name: "0.6" + status: :unreleased + release_time: + log_events: + - - 2008-04-20 21:17:04.443432 Z + - William Morgan + - created + - "" -- 2.45.2