On 4/18/2013 7:50 AM, Nazri Ramliy wrote:
Here's another attempt. This time we check if the expanded path ends
with a path separator then we replace it with forward slash, and we do
this only on windows/msdos.
Updated patch attached.
I tried the patch to src/misc1.c (but not the patches for t
On Thu, Apr 18, 2013 at 10:11 PM, Nazri Ramliy wrote:
> Thanks for the notice. I'll look into this again. My initial approach at
> solving this was to replace all backslashes in the expanded path parts
> into forward slashes but that seemed a bit too blankety of a solution
> at that time.
>
> Mayb
On Thu, Apr 18, 2013 at 9:06 PM, Ingo Karkat wrote:
> Please note that for the root directory, C:\ is different than C: (which
> means the current working directory of the C drive), so leaving off the
> trailing path separator may cause problems in this case. (I haven't
> checked your patch, but :
On Thu, April 18, 2013 15:45, Ingo Karkat wrote:
> It's not silly, you're just not used to it! (I started with CP/M and
> MS-DOS 5; maybe I have a different perspective.)
That is the case. I started with MS-DOS 4.X and have never come across
that. But ok, may be it is just my expectation.
regard
On 18-Apr-2013 15:15 +0200, Christian Brabandt wrote:
> On Thu, April 18, 2013 15:32, Ingo Karkat wrote:
>> On 18-Apr-2013 15:15 +0200, Christian Brabandt wrote:
>>
>>> On Thu, April 18, 2013 15:06, Ingo Karkat wrote:
Please note that for the root directory, C:\ is different than C:
(whi
On Thu, April 18, 2013 15:32, Ingo Karkat wrote:
> On 18-Apr-2013 15:15 +0200, Christian Brabandt wrote:
>
>> On Thu, April 18, 2013 15:06, Ingo Karkat wrote:
>>> Please note that for the root directory, C:\ is different than C:
>>> (which
>>> means the current working directory of the C drive), so
On 18-Apr-2013 15:15 +0200, Christian Brabandt wrote:
> On Thu, April 18, 2013 15:06, Ingo Karkat wrote:
>> Please note that for the root directory, C:\ is different than C: (which
>> means the current working directory of the C drive), so leaving off the
>> trailing path separator may cause probl
On Thu, April 18, 2013 15:06, Ingo Karkat wrote:
> Please note that for the root directory, C:\ is different than C: (which
> means the current working directory of the C drive), so leaving off the
> trailing path separator may cause problems in this case. (I haven't
> checked your patch, but :echo
On 18-Apr-2013 14:14 +0200, Nazri Ramliy wrote:
> On Tue, Apr 16, 2013 at 4:31 PM, Nazri Ramliy wrote:
>> I can reproduce this with my gvim 7.3.46 (on linux vim 7.3.892 there's> no
>> problem). I'll investigate and hopefully post a fix soon.
>
> I found the problem and the solution.
>
> Proble
On Tue, Apr 16, 2013 at 4:31 PM, Nazri Ramliy wrote:
> I can reproduce this with my gvim 7.3.46 (on linux vim 7.3.892 there's> no
> problem). I'll investigate and hopefully post a fix soon.
I found the problem and the solution.
Problem summary:
expand_path_option() leaves trailing path separat
On Mon, Apr 15, 2013 at 6:56 PM, Suresh Govindachar
wrote:
> My c:\opt is not below the pwd. Anyway, for the test,
> leave path at the default value of ".,,".
>
> > :pwd
> > D:\foo
>
> When starting from d:, :pwd will show d:\
>
> > Now doing
>
> In gvim, open file
On 4/14/2013 10:56 PM, Nazri Ramliy wrote:
> Hi Suresh!
> On Mon, Apr 15, 2013 at 10:22 AM, Suresh Govindachar
wrote:
>
>> Hitting after entering a partial argument to :find will
>> offer suggestions for completing the command line by searching
>> inside non-trivial components of
On Mon, Apr 15, 2013 at 1:56 PM, Nazri Ramliy wrote:
> Is there anything different in my settings here that might not show the
> problem that you're seeing?
>
I forgot to add my vim version (it's older than yours):
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
MS-Windows 32
On Mon, Apr 15, 2013 at 1:56 PM, Nazri Ramliy wrote:
> 15/04/2013 01:32 PM11 700_vimrc
> 15/04/2013 01:33 PM10 fish.txt
> 15/04/2013 01:33 PM12 fish.txt
>
One of those fishes should really be a finger.txt ;)
nazri
--
--
You received th
Hi Suresh!
On Mon, Apr 15, 2013 at 10:22 AM, Suresh Govindachar
wrote:
> Hitting after entering a partial argument to :find will offer
> suggestions for completing the command line by searching inside
> non-trivial components of the 'path' -- but it does not search in "."
> and in ",," component
Hello,
Hitting after entering a partial argument to :find will offer
suggestions for completing the command line by searching inside
non-trivial components of the 'path' -- but it does not search in "."
and in ",," components of the path.
Here's what I see: On vim's command line, the fol
16 matches
Mail list logo
