ctags plug-in/part broken, patch included

[mwoehlke]

Jens Dagerbo wrote:
> On Friday 15 September 2006 17:07, mwoehlke wrote:
>> Jens Dagerbo wrote:
>>> On 9/15/06, mwoehlke <mwoehlke at tibco.com> wrote:
>>>> mwoehlke wrote:
>>>>> My ctags plug-in (or is it a part?) does not remember that I want to
>>>>> use custom options (KDevelop 3.3.91). The attached patch (remember if
>>>>> 'use custom arguments' is checked) appears to fix the problem. Can
>>>>> someone review this and check it in?
>>>>>
>>>>> Thanks!
>>>> No comments?
>>>> (patch: http://article.gmane.org/gmane.comp.kde.devel.kdevelop/16285)
>>> Errr.. didn't I check that in?
>> If you did, you didn't reply here with the commit. (I don't watch
>> commits except what makes it either here or to a bug report, so if you
>> can CC the list that would be nice!)
>>
>>> [looks]
>>>
>>> Ooops. I thought I did. Will have a go at it tonight.
>>>
>>> Thanks for the patch! :)
>> Ah, well in that case... if you can just CC the list when you commit
>> and/or post a reply here, that would be great. And thanks!
> 
> Ok, I committed a fix to the "real" problem. The custom string was in effect, 
> even if the checkbox wasn't checked and the lineedit greyed out.
> 
> See http://lists.kde.org/?l=kde-commits&m=115835866818249&w=2 for details.
> 
> Thanks again for pointing out the problem!

Ah, well, since I was *using* said custom string, I guess I didn't 
notice, except that KDevelop kept "forgetting" that I wanted to use it. :-)

I guess this means the only way to turn off custom args is to remove 
them? I don't care if that's the case, but someone else might (or maybe 
I am reading the diff wrong?). Just food for thought.

Anyway, thanks again for the fix!

-- 
Matthew
Download. Untar. Configure. Make. Install. Lather. Rinse. Repeat.