Re: textmode web browsers and their setup.hint descriptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harold L Hunt II wrote: | I don't see the point in discussing it. Just propose a set of new | sdesc's and ldesc's. If they are fine, I'll put them in the | packages that I maintain. Honestly, it isn't easy to come up with | good descriptions since the home page of each project has roughly | the same descriptive sentence. I agree it's not easy to differentiate them, but at least let's try not to let them "clash" with each other (like "lynx has good support for tables" and "unlike lynx it supports tables") 0=) Some possible sdesc could be: lynx = "The first text-mode WWW browser" links = "Improved text-mode WWW browser with support for frames" elinks = "An extension of links, a text-mode WWW browser" Maybe we could also point out that links and elinks are "alive", while lynx' last release is in 2001. - -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAj/udOsACgkQaJiCLMjyUvvKSgCgmPyFFr5fYXaWnB4wQ2b6tGuf dq0An1RUzn0WrxAwI9dCkxmRgoq/Ne5S =k5E+ -END PGP SIGNATURE-
Re: textmode web browsers and their setup.hint descriptions
Lapo, I don't see the point in discussing it. Just propose a set of new sdesc's and ldesc's. If they are fine, I'll put them in the packages that I maintain. Honestly, it isn't easy to come up with good descriptions since the home page of each project has roughly the same descriptive sentence. Harold Lapo Luchini wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harold L Hunt II wrote: | I would like to contribute and maintain elinks when we will have "lynx", "links" and "elinks" I think it culd be very useful to differentiate descriptions a bit. lynx = "Text-mode WWW Browser" "Lynx is a terminal based WWW browser. While it does not make any attempt at displaying graphics, it has good support for HTML text formatting, forms, and tables. This version includes support for SSL encryption." links = "Text mode web browser" "Links is a very capable text-mode web browser. It obeys keyboard commands similar to lynx but unlike lynx, links supports the HTML TABLE tag. Links also allows you to download files in the background." elinks = "Text mode web browser" "ELinks is a program for browsing the web in text mode." At least "links" tries to be "better" than "lynx" in the ldesc, but ldescs are not yet used by setup.exe, imho they should be different in the sdesc also. The ldesc of elinks is way too underscriptive IMHO. The differences in the sdesc od "lynx" and "links" are also quite ridicolous: if we really want to use that description then let's use the *very* same for both, not a sligthly modified version of the same description. BTW: lynx's ldesc talks about support for tables, links's ldesc negates that... where is the truth? - -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAj/uXS4ACgkQaJiCLMjyUvtDcwCgikx5MSYVZCqlLly0uUGrEZcs TUUAn0ocEUJcfFYa13L0R0dDknj6xmyl =M7+M -END PGP SIGNATURE-
textmode web browsers and their setup.hint descriptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harold L Hunt II wrote: | I would like to contribute and maintain elinks when we will have "lynx", "links" and "elinks" I think it culd be very useful to differentiate descriptions a bit. lynx = "Text-mode WWW Browser" "Lynx is a terminal based WWW browser. While it does not make any attempt at displaying graphics, it has good support for HTML text formatting, forms, and tables. This version includes support for SSL encryption." links = "Text mode web browser" "Links is a very capable text-mode web browser. It obeys keyboard commands similar to lynx but unlike lynx, links supports the HTML TABLE tag. Links also allows you to download files in the background." elinks = "Text mode web browser" "ELinks is a program for browsing the web in text mode." At least "links" tries to be "better" than "lynx" in the ldesc, but ldescs are not yet used by setup.exe, imho they should be different in the sdesc also. The ldesc of elinks is way too underscriptive IMHO. The differences in the sdesc od "lynx" and "links" are also quite ridicolous: if we really want to use that description then let's use the *very* same for both, not a sligthly modified version of the same description. BTW: lynx's ldesc talks about support for tables, links's ldesc negates that... where is the truth? - -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP & X.509 keys available) http://www.lapo.it (ICQ UIN: 529796) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAj/uXS4ACgkQaJiCLMjyUvtDcwCgikx5MSYVZCqlLly0uUGrEZcs TUUAn0ocEUJcfFYa13L0R0dDknj6xmyl =M7+M -END PGP SIGNATURE-
joe-2.9.8 and ce-1.3.0
Hello. I've tried to contact the developers of these packages but it appears to exist some problem with the mail (mine or their). This message is only to tell you that I could compile succesfully both editors under cygwin. The joe editor has its own ./configure, but ce editor needs a little hack. Cheers Sergio
vim / cream
Some members of this list expressed interest in packaging http://cream.sourceforge.net/ for Cygwin. Here is why I doubt this will happen soon: I chatted with Steve Hall, the author, and unfortunately, Cream is only effective, when run as a gui with menus. Cream is partially useful for console mode, but not much is planned to pursue that direction. Note that porting Cream to be used with Cygnome's gvim makes sense. This brings back the issues I faced in packaging EMacro: how to centralize the startup, or deal with distributing .vimrc-s to each HOME directory. Some versions of Vim do support /etc/vimrc for startup. This may not work so well with Cream, which was written to work in HOME directories, AFAIK. Happy Holidays!
