RE: Maildir and Cygwin
*** GARY VANSICKLE ([EMAIL PROTECTED]) wrote in the...: :) On Thu, Apr 22, 2004 at 08:26:00AM -0700, Eduardo Chappa wrote: :) :) :) that Cygwin is different (e.g. we could do this in the cygwin :) :) applications mailing list). :) :) :) :) Why do you want to change so many programs when all you need is :) :) a cygwin managed mount? :) :) IMO, the correct solution for mutt to make everyone happy would be a :) new configuration variable to specify the character (presumably :) defaulting to non-: for cygwin). I think I've seen both ; and - :) suggested in different places. :) :) No, all that would do is guarantee that a mutt using ; couldn't read :) a Maildir written by a fetchmail using - (i.e. the disagreement would :) simply move from being hardcoded to being defined at compile time). :) The correct solution is to implement a corrected spec. A correct spec will not solve the problem, because we already have the problem. I believe that the solution is to take action and not to wait for someone else to act upon this. What are the chances that we all agree on using - for cygwin? (I think - is a bad choice because a dash could be part of a domain name, but it's not a problem if that's what is decided upon). Who is the maintainer of fetchmail, so that we can get him/her into this thread? Eduardo http://www.math.washington.edu/~chappa/pine/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Maildir and Cygwin
On Thu, Apr 22, 2004 at 11:33:13PM -0500, GARY VANSICKLE wrote: On Thu, Apr 22, 2004 at 08:26:00AM -0700, Eduardo Chappa wrote: :) that Cygwin is different (e.g. we could do this in the cygwin :) applications mailing list). :) :) Why do you want to change so many programs when all you need is a :) cygwin managed mount? IMO, the correct solution for mutt to make everyone happy would be a new configuration variable to specify the character (presumably defaulting to non-: for cygwin). I think I've seen both ; and - suggested in different places. No, all that would do is guarantee that a mutt using ; couldn't read a Maildir written by a fetchmail using - (i.e. the disagreement would simply move from being hardcoded to being defined at compile time). The correct solution is to implement a corrected spec. configuration variables is what mutt calls user settings; settable in .muttrc by the user. Perhaps it would even work to have a folder hook override it so one Maildir folder could use one thing and another use another. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Maildir and Cygwin
On Wed, Apr 21, 2004 at 11:27:21AM -0700, Eduardo Chappa wrote: This is pretty much the point that I wanted to address at this time. I realize that I don't know all the players of the game either, but we could all agree on one way to play the game and those who want to join to game will have to follow the rules. I do not believe that changing : by other character (e.g. ;) is an essential change (correct me if I am wrong) and asking for everyone to agree on this seems like a minor point, given all the benefits that it carries out. We should not need to go upstream, simply make common knowledge that Cygwin is different (e.g. we could do this in the cygwin applications mailing list). Eduardo http://www.math.washington.edu/~chappa/pine/ Why do you want to change so many programs when all you need is a cygwin managed mount? Gruss Olaf Föllinger -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Maildir and Cygwin
*** Olaf Föllinger ([EMAIL PROTECTED]) wrote in the cygwin...: :) On Wed, Apr 21, 2004 at 11:27:21AM -0700, Eduardo Chappa wrote: :) :)This is pretty much the point that I wanted to address at this :) time. I realize that I don't know all the players of the game either, :) but we could all agree on one way to play the game and those who want :) to join to game will have to follow the rules. I do not believe that :) changing : by other character (e.g. ;) is an essential change :) (correct me if I am wrong) and asking for everyone to agree on this :) seems like a minor point, given all the benefits that it carries out. :) We should not need to go upstream, simply make common knowledge :) that Cygwin is different (e.g. we could do this in the cygwin :) applications mailing list). :) :) Why do you want to change so many programs when all you need is a :) cygwin managed mount? I do not want to change programs. This is more or less like a #ifdef CYGWIN within a program, this does not change the program in any way, it's a one line of code added to the program to make it work in a specific platform. Most programs (designed for different platforms) are full of those lines. This is just another one liner addition to a program (ok, maybe 2, or 20 lines, but it should be an easy addition to every program supporting maildir). Many programs need to be modified just to make them work in Cygwin (e.g. Lynx, Pine for windows, etc.), why can't we do this with programs that support Maildir? Managed Mounts is not the solution to the problem. The user does not need to know what these things are, they have nothing to do with Maildir. That's just a trick to get around a problem, not a solution (the solution to a leak in the roof is not moving the couch!) That's the reason why I think that an easy modification specific to Cygwin is the solution. Eduardo http://www.math.washington.edu/~chappa/pine/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Maildir and Cygwin
On Thu, Apr 22, 2004 at 08:26:00AM -0700, Eduardo Chappa wrote: :) that Cygwin is different (e.g. we could do this in the cygwin :) applications mailing list). :) :) Why do you want to change so many programs when all you need is a :) cygwin managed mount? IMO, the correct solution for mutt to make everyone happy would be a new configuration variable to specify the character (presumably defaulting to non-: for cygwin). I think I've seen both ; and - suggested in different places. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Maildir and Cygwin
On Thu, Apr 22, 2004 at 08:26:00AM -0700, Eduardo Chappa wrote: :) that Cygwin is different (e.g. we could do this in the cygwin :) applications mailing list). :) :) Why do you want to change so many programs when all you need is a :) cygwin managed mount? IMO, the correct solution for mutt to make everyone happy would be a new configuration variable to specify the character (presumably defaulting to non-: for cygwin). I think I've seen both ; and - suggested in different places. No, all that would do is guarantee that a mutt using ; couldn't read a Maildir written by a fetchmail using - (i.e. the disagreement would simply move from being hardcoded to being defined at compile time). The correct solution is to implement a corrected spec. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Maildir and Cygwin
*** GARY VANSICKLE ([EMAIL PROTECTED]) wrote in the...: :) I've been testing the maildir patch (for Pine) and changing : to :) ; works perfectly well, so I was wondering how compatible is this :) with other tools designed for maildir. I am not advocating for the :) use of ;, I am asking the questions as to Can we agree to use :) something different than ':'? and Can we use ';'?. :) :) I guess it depends on who the we is, and how many wes there are. :) Maildir is, AFAICT, less of a spec and more of a web page somebody put :) up. I have no idea how many apps are using this format, though I guess :) the only thing we care about for the most part is which Cygwin ports :) use it. What would be best though is to clean up the Maildir spec and :) push it upstream; probably a rather Herculean task. Gary, This is pretty much the point that I wanted to address at this time. I realize that I don't know all the players of the game either, but we could all agree on one way to play the game and those who want to join to game will have to follow the rules. I do not believe that changing : by other character (e.g. ;) is an essential change (correct me if I am wrong) and asking for everyone to agree on this seems like a minor point, given all the benefits that it carries out. We should not need to go upstream, simply make common knowledge that Cygwin is different (e.g. we could do this in the cygwin applications mailing list). Eduardo http://www.math.washington.edu/~chappa/pine/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Maildir and Cygwin
Hello, I have been trying to fix a patch for maildir for Pine, and while thinking about this I recalled that support for Maildir in Cygwin (e.g Mutt) has been discussed a couple of times. It seems to be that the only thing stopping people from being able to use it is a agreement on the format of the name among the different programs that do maildir. Explicitly this means to deprecate the use of : in the filename. I've been testing the maildir patch (for Pine) and changing : to ; works perfectly well, so I was wondering how compatible is this with other tools designed for maildir. I am not advocating for the use of ;, I am asking the questions as to Can we agree to use something different than ':'? and Can we use ';'?. Thanks for your feedback! Well first of all, remember that managed mounts do seem to allow Maildirs to work on Cygwin, so that's an interim solution. However, to get to the core of the problem: I guess it depends on who the we is, and how many wes there are. Maildir is, AFAICT, less of a spec and more of a web page somebody put up. I have no idea how many apps are using this format, though I guess the only thing we care about for the most part is which Cygwin ports use it. What would be best though is to clean up the Maildir spec and push it upstream; probably a rather Herculean task. To have any chance of success, I'd almost guarantee[1] that any Maildir 2 spec would have to add more value than POSIX-compatible filenames. I don't know what that might be, but there's always something that can be improved or added to anything. As sometimes-maintainer of Mutt, I'm certainly willing to agree to use something different than ':'. However, I'm also an upstream release behind, and not seeing the light at the end of the no-time tunnel. -- Gary R. Van Sickle Brewer. Patriot. [1] This is not a guarantee. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
