Subject: Various bugs and suggestions to pine 4.00

From: "Marcin 'Qrczak' Kowalczyk" <[email-masked]>
Date: Thu, 9 Jul 1998 18:56:03 +0200 (CEST)

Please tell if I should split it into separate messages next time.

1. I have Linux and glibc-2.0.7-13 and had to add -lcrypt manually to
   build pine.

2. Folder list, W something, ^X. This doesn't rearrange folder names
   correctly (as selecting with `:' does).

3. It would be nice if TAB TAB displayed possible completions for
   e.g. name of file to attach or insert, not only for folders.

4. When selectable items are in every line near the bottom of message,
   first DOWN key scrolls the text one line, second one selects the link
   that just appeared, third scrolls next line, fourth selects next link...
   So I think it would be more convenient if scrolling by one line
   selected the last link on that line as well (or first link, when
   scrollong up), so continuous scrolling would be more even.

5. When I am in postponed-msgs folder and attempt to continue postponed 
   composition, I get:
   [>Another Pine is accessing Inbox.  Session now Read-Only.<]
   Then some evil things may occur, e.g. garbage in that message.

6. If .signature file already begins with "-- ", pine should not add the
   second one. Some people may keep it there for other programs.

7. Pine could make links from email addresses without mailto: as well.

8. It would be nice if the string "On [someday], [somebody] wrote:" was
   configurable, wouldn't it?

9. Sometimes crossposts are deleted, sometimes not... Unfortunately now
   I can't detect and say exactly when. But one thing is obviously true:
   after unexclusion of a large newsgroup with `&' and then exiting it,
   smart enough program shouldn't have to examine all previously deleted
   messages for crossposts!

10. When you have time to think about improving a composer, I would
    suggest to start with writing a block to a file and piping a block
    through a command. Yes, I know I can attach an external editor, but
    it would not integrate with the rest of pine so nice :-)

11. I hope that the bugs I've told about, long time ago, to
    [email-masked], will be fixed sometime, as some of them
    still remain in version 4.00... I guess there is no need to repeat
    them here now, or am I wrong?

12. Is there a sense in telling about much larger wishes about pine?
    Unicode? Threading?

Thanks for pine, I found it the most convenient mailer and newsreader!
Version 4.00 is much better. But it still has bugs :-|

I may try to dig into sources and correct some of these bugs myself,
but unfortunately not until September.

-- 
 __("<   Marcin Kowalczyk * [email-masked] http://qrczak.home.ml.org/
 \__/       GCS/M d- s+:-- a21 C+++>+++$ UL++>++++$ P+++ L++>++++$ E->++
  ^^                W++ N+++ o? K? w(---) O? M- V? PS-- PE++ Y? PGP->+ t
QRCZAK                  5? X- R tv-- b+>++ DI D- G+ e>++++ h! r--%>++ y-

-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Jeff <[email-masked]>
Date: Thu, 9 Jul 1998 14:14:20 -0400 (EDT)

> 1. I have Linux and glibc-2.0.7-13 and had to add -lcrypt manually to

I too am attempting to build under a glibc system- RedHat 5.0 with
glibc-2.0.7-13. I've tried a few things, and likely the large breakfast of
caffeine is clouding my memory, but- could you describe how you went about
adding -lcrypt manually? Also... there exist lnx, slx, and sl5
builds/ports for Linux... if using shadow passwords and glibc, am i
correct in assuming that i need to use slx to build?

Many, many thanks-

-jeff

---

From: "Marcin 'Qrczak' Kowalczyk" <[email-masked]>
Date: Thu, 9 Jul 1998 23:19:26 +0200 (CEST)

On Thu, 9 Jul 1998, Jeff wrote:

> could you describe how you went about adding -lcrypt manually? Also...
> there exist lnx, slx, and sl5 builds/ports for Linux... if using
> shadow passwords and glibc, am i correct in assuming that i need to
> use slx to build?

Oops, slx works for me (I previously did lnx), SORRY!

I didn't ever know that slx exists, as there was only lnx in 3.96. Tried
lnx, got linker errors about crypt, remembered that glibc AFAIK moved
crypt into separate library, thought they maybe used some other glibc
version? added BASELDFLAGS="-lcrypt" into imap/src/osdep/unix/Makefile
under lnx and it worked. But it was my fault, as I should have read six
lines above where I added -lcrypt :-)

This Makefile says that slx is correct for glibc with shadow passwords.
I have no idea about your problems :-(

Ah, one more probable bug in pine: pine's Setup Newpassword looks for
/bin/passwd, and I have it in /usr/bin/passwd (from passwd-0.50-11.*.rpm).