Hi Bram,
On 15 April 2011 15:00, Bram Moolenaar wrote:
> It's easy enough to add "mksh" and "pdksh" next to "ksh" in src/option.c
Agreed, attached please find a patch that addresses the issue.
Thank you,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
James Vega wrote:
> On Thu, Apr 14, 2011 at 08:22:22PM -0400, Chris Sutcliffe wrote:
> > On 14 April 2011 20:11, Chris Sutcliffe wrote:
> > > On 14 April 2011 16:38, Chris Sutcliffe wrote:
> > >> I've noticed an issue with vim while running under mksh and pdksh.
> > >> Specifically, the stderr ou
On Thu, Apr 14, 2011 at 08:22:22PM -0400, Chris Sutcliffe wrote:
> On 14 April 2011 20:11, Chris Sutcliffe wrote:
> > On 14 April 2011 16:38, Chris Sutcliffe wrote:
> >> I've noticed an issue with vim while running under mksh and pdksh.
> >> Specifically, the stderr output by gcc (i.e. compilation
On 14 April 2011 20:11, Chris Sutcliffe wrote:
> On 14 April 2011 16:38, Chris Sutcliffe wrote:
>> I've noticed an issue with vim while running under mksh and pdksh.
>> Specifically, the stderr output by gcc (i.e. compilation warnings and
>> errors) is not captured in the QuickFix window. I see th
On 14 April 2011 16:38, Chris Sutcliffe wrote:
> I've noticed an issue with vim while running under mksh and pdksh.
> Specifically, the stderr output by gcc (i.e. compilation warnings and
> errors) is not captured in the QuickFix window. I see the stderr
> output in the terminal window during the
Hi All,
I've noticed an issue with vim while running under mksh and pdksh.
Specifically, the stderr output by gcc (i.e. compilation warnings and
errors) is not captured in the QuickFix window. I see the stderr
output in the terminal window during the compilation process, however,
when vim returns
