Excerpts from florent.becker's message of Mon Nov 17 12:04:28 +0100 2008: > Trent W. Buck wrote: > > > Eric Kow <[EMAIL PROTECTED]> writes: > > > >> On Sat, Nov 15, 2008 at 19:11:29 +0100, Florent Becker wrote: > >>> >> We could have an out-of-band description (anything that follows the > >>> >> line > >>> >> *END OF DESCRIPTION* > >>> >> is ignored) > >>> > > >>> > I think that's orthogonal to my suggestion (i.e. we could do both). > >>> > >>> If you have a responsive mail server, then when you see that advice it's > >>> already too late to use it (you won't be able to kill darcs before the > >>> mail is sent). > >> > >> The idea would be to kill darcs while you are still in your text editor > >> (which is what I already do, so I thought maybe making the advice > >> explicit could be handy). > > > > Right, it could say something like: > > > > > > If you have reached this point and decided NOT to send the mail, you > > currently have to kill the darcs process. For example, in vim type > > > > ^[!killall darcs^M > > > > or in Emacs, type > > > > M-! killall darcs RET > > Here is another idea from myself on #darcs instead of asking a question, add > a line in the editor (under *END OF DESCRIPTION*) that says > > #you may uncomment one or more of the following lines if you changed your > # mind about sending this patch: > # cancel the whole sending > # dump mail to file: REPLACE/ME/WITH/PATH/TO/FILE.eml > # dump bundle to file: REPLACE/ME/WITH/PATH/TO/FILE.dpatch > > This way, you can get the result of -O or cancel, or get a copy of the whole > mail (as was discussed a little while ago) after you have selected your > patches. This also looks more elegant than saying "go to another terminal > and kill this program" without adding flags or questions to the UI. What do > you think?
I agree, that just great! -- Nicolas Pouillard aka Ertai _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
