Re: Patch: problems with filename contains '~' in file-marks

2007-09-26 Fir de Conversatie Tony Mechelynck
Ben Schmidt wrote: The only thing that requires a little care (IIUC) is to make sure that if the tilde is followed by a backslash, the latter is a true backslash and not an escaper backslash for something else than a backslash: in ~\foo, ~ means $HOME while in ~\ foo it doesn't, and

VC8 make file patch

2007-09-26 Fir de Conversatie Mike Williams
Hi, The following is a resend of a patch from 6 months ago to enable optimized building with to use VC8 features and remove compiler option warnings. TTFN Mike -- Cogito Ergo Mortalis... I think, therefore I'm Doomed. --~--~-~--~~~---~--~~ You received this

RE: Patch: problems with filename contains '~' in file-marks

2007-09-26 Fir de Conversatie Doug Cook
Profiles really only have a strong meaning under NT. There was a per-user desktop on Windows 9x, but it was pretty weak. For NT, to accurately get the profile for a user, you can use GetUserProfileDirectory -- but you have to get the user's token first. Which for all intents and purposes means

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie krischik
On Sep 26, 3:53 pm, Gregory Seidman [EMAIL PROTECTED] wrote: I have a Fink-built vim/gvim (X11) 7.1.116 package on my Mac. I've used a Fink-built package in the past on a previous Mac, but this one is behaving strangely. For some reason, gvim will not background itself. It's as if it is

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie Gregory Seidman
On Wed, Sep 26, 2007 at 09:18:00AM -0700, krischik wrote: On Sep 26, 3:53 pm, Gregory Seidman [EMAIL PROTECTED] wrote: I have a Fink-built vim/gvim (X11) 7.1.116 package on my Mac. I've used a Fink-built package in the past on a previous Mac, but this one is behaving strangely. For

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie Nikolai Weibull
On 9/26/07, Gregory Seidman [EMAIL PROTECTED] wrote: Does anyone have any suggestions? Here's the output of gvim --version: #if defined(UNIX) !defined(__BEOS__) !defined(MACOS_X) # define MAY_FORK int dofork = TRUE; #endif So no, it seems you simply can't fork under MACOS_X. I

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie Gregory Seidman
On Wed, Sep 26, 2007 at 06:59:02PM +0200, Nikolai Weibull wrote: On 9/26/07, Gregory Seidman [EMAIL PROTECTED] wrote: Does anyone have any suggestions? Here's the output of gvim --version: #if defined(UNIX) !defined(__BEOS__) !defined(MACOS_X) # define MAY_FORK int

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie Tony Mechelynck
Gregory Seidman wrote: On Wed, Sep 26, 2007 at 06:59:02PM +0200, Nikolai Weibull wrote: On 9/26/07, Gregory Seidman [EMAIL PROTECTED] wrote: Does anyone have any suggestions? Here's the output of gvim --version: #if defined(UNIX) !defined(__BEOS__) !defined(MACOS_X) # define MAY_FORK

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie Gregory Seidman
On Wed, Sep 26, 2007 at 07:12:45PM +0200, Tony Mechelynck wrote: Gregory Seidman wrote: On Wed, Sep 26, 2007 at 06:59:02PM +0200, Nikolai Weibull wrote: On 9/26/07, Gregory Seidman [EMAIL PROTECTED] wrote: Does anyone have any suggestions? Here's the output of gvim --version: #if

Re: VC8 make file patch

2007-09-26 Fir de Conversatie Bram Moolenaar
Mike - The following is a resend of a patch from 6 months ago to enable optimized building with to use VC8 features and remove compiler option warnings. I had a few problems with this patch, which is why I didn't send it out yet. Also, it collides with a patch from George Reilly for

Re: gvim won't run in the background

2007-09-26 Fir de Conversatie Bram Moolenaar
Gregory Seidman wrote: On Wed, Sep 26, 2007 at 06:59:02PM +0200, Nikolai Weibull wrote: On 9/26/07, Gregory Seidman [EMAIL PROTECTED] wrote: Does anyone have any suggestions? Here's the output of gvim --version: #if defined(UNIX) !defined(__BEOS__) !defined(MACOS_X) #

Re: patch 7.1.123

2007-09-26 Fir de Conversatie Bill McCarthy
On Wed 26-Sep-07 3:35pm -0600, Bram Moolenaar wrote: Patch 7.1.123 Problem:Win32: :edit foo ~ foo expands ~. Solution: Change the call to expand_env(). Files: src/ex_docmd.c, src/misc1.c, src/proto/misc1.pro, src/option.c You appear to have eliminated the problem. Thanks! --