[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: global feature request: allow blanks in filenames

From: Tony E. Bennett
Subject: Re: global feature request: allow blanks in filenames
Date: Thu, 18 Jan 2001 13:22:27 -0500

I'll take option #2 and switch to cscope.  It has same bug with
blanks in filenames but is trivially fixed.

Thanks for considering this anyway.


>>>>> "Shigio" == Shigio Yamaguchi <address@hidden> writes:

>> I think this would do it for keys 1,3, but not for key 2
>> (linenum).  Assumes all filenames wrapped by '"'.  I
>> $ sort -t '"' -k 1,1 -k 2,2

Shigio> We cannot assume all filenames wrapped by '"'.

>> But if the input could be changed to look like this:
>> (1)  (2)             (3)
>> +----------------------------------------------------------
>> |main^   32^             ./src/m in.c^      main(argc, argv)
>> |main^    22^            ./a b/f u n c.c^   main(argc, argv)
>> |func^     5^            ./abc/func.c^      func()
>> |func2^   10^            ./abc/func.c^      func2()
>> then this command should do it:
>> $ sort -b -t '^' -k 1,1 -k 3,3 -k 2,2n
>> The '^' is field separator.  '-b' says to ignore *leading* blanks
>> (left in for readability, but could be removed).

Shigio> Introducing new separator also create another new bad character
Shigio> which cannot be used in file names.
Shigio> Hmm..., it is difficult.

Shigio> Sorry but please select 1 or 2:

Shigio> 1. exclude blanks from your file names.
Shigio> 2. give up to use global.

Shigio> I have a policy that GLOBAL should be 80% complete.
Shigio> --
Shigio> Shigio Yamaguchi - Tama Communications Corporation
Shigio> Mail: address@hidden, (Spare mail: address@hidden)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]