[p4] Why is xemacs / gvim /vim kind of editors not supported in p4?

[Hemantharaju Subbanna x4832]

Hi Jeff,
Appreciate your insight. I understand that you are supportive and defending 
perforce here.
As with any product, perforce needs some customization. When customization 
becomes repetative and a norm then companies adopt them as feature.

I wonder why xemacs/gvim  is not a yet a general customization request.
If my understanding is right more then half the unix users are  on xemacs.

As Jermey points out p4.el is very helpful, may be perforce can adapt it.
It is hard to sell to some groups when we say that xemacs is not a directly 
supported editor.

Anyway it is just a thought not a necessary condition.
--Raju
NOTE: One other thing may be that emacs itself is not a supported product.
But who is supporting "vi"?

>>X-Server-Uuid: d6ddd4b6-ef0b-4485-8736-a314bd30aabc
>>X-Sender: mail310006 at mail310006.popserver.pop.net
>>Date: Thu, 18 Apr 2002 19:31:44 -0700
>>To: "Hemantharaju Subbanna x4832" <raju at galaxy.nsc.com>, 
perforce-user at perforce.com
>>From: "Jeff A. Bowles" <jab at piccoloeng.com>
>>Subject: Re: [p4] Why is xemacs / gvim /vim kind of editors not supported in 
p4?
>>MIME-Version: 1.0
>>X-WSS-ID: 10A15E33133177-01-01
>>Content-Transfer-Encoding: 7bit
>>X-Mozilla-Status: 0000
>>X-Mozilla-Status2: 00000000
>>X-UIDL: +I&!!/S,!!8MF"!`4=!!
>>
>>At 01:50 PM 4/18/2002 -0700, Hemantharaju Subbanna x4832 wrote:
>>>Is their a way that this can be worked out?
>>
>>I think you're referring to the fact that Perforce's client program
>>runs "emacs" or "vi" or whatever, it runs it by calling the C library
>>routine "system" to run it.
>>
>>But what if the line
>>         retval = system("xemacs");
>>returns immediately, because 'xemacs' starts up, spawns off a
>>background version of the editor to run in another window, and then
>>exits the process that this 'system' invocation started?
>>
>>Well, that's what you're seeing.
>>
>>Is it possible that there's another version of your favorite editor
>>that runs synchronously, that is to say "in foreground" mode?
>>That's the one you should be running.
>>
>>Most editors have SOME way to invoke them in foreground mode,
>>either a separate executable that's f.g. or a special '/wait' option
>>or something.
>>
>>Look around to see what it is. It's not a deficiency of Perforce,
>>so much as a mismatch between which version of your favorite
>>editor it's launching and how it's launching it...
>>
>>         -Jeff Bowles
>>         Perforce Consulting Partner
>>
>>