Okay, but I still don't see why this implies #ifdef WIN32 code in the
client. You try to pop up an editor, based on various clues (an
environment variable, an init file, whatever). If you fail to pop up
an editor, you fail, no big deal. The commit can either proceed with
empty log message, or bail with an error about requiring a log
message.
"Bill Tutt" <rassilon@lyra.org> writes:
> > From: Greg Stein [mailto:gstein@lyra.org]
> >
> > If you believe contrary, then outline what the EDITOR concept means on
> > Windows. "popping up an editor" just isn't normal Win32 behavior.
> >
>
> Yeah, this is real rats nest for Win32, the easiest way out is to just
> use notepad by default for the command line client, or a GUI that has a
> text editing control for the commit message. There's nothing wrong with
> using the EDITOR environment variable on Win32, it's just very unlikely
> that it's actually set to something.
>
> Some folks I know that use Perforce on Win32 went and wrote a custom
> Perforce forms UI for editing the necessary Perforce forms.
>
> Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:59 2006