How to modify .kdev4 file in script?

Milian Wolff mail at milianw.de
Sun Nov 2 22:27:07 GMT 2014


On Friday 31 October 2014 12:19:05 Aleksey Midenkov wrote:
> On Thu, Oct 30, 2014 at 5:09 PM, Alvin Beach <alvinbeach at gmail.com> wrote:
> > On 30/10/14 09:32, Aleksey Midenkov wrote:
> >> I see now there is some strangely encoded multiline strings (though
> >> IMO it would be better to make separate section for each multiline
> >> string):
> >> 
> >> [CustomDefinesAndIncludes][ProjectPath0]
> >> Defines=\x00\x00\x00\x00
> >> Includes=\x00\x00\x00\x04\x00\x00\x00`\x00/\x00h\x00o\x00m\x00e...
> >> Path=.
> >> 
> >> How to properly decode and encode them with bash/perl script?
> > 
> > I asked about something along these lines before (i.e.
> > BuildItems=@Variant(\x00\x00\x00...)). I too manipulate the .kdev4
> > project files via script.
> > 
> > I was told that these are written by KConfig and was directed to look at
> > kreadconfig and kwriteconfig. I've only had a quick look at those
> > programs. In the end I just cleared the value (everything after the '=').
> > This wouldn't be a solution if you would like to edit the values though.
> > 
> > Perhaps you will have better luck with kreadconfig and kwriteconfig. If
> > you figure it out, please do share.
> Probably, we better ask authors of kreadconfig and kwriteconfig. It is
> their fault to make such ugly design. Human-readable files must be
> human-readable!
> 
> I'm totally in the mood of indignation of how much hope KDE3 given and
> how much mutilation and perversion KDE4 brought.

Or, you know, you could just spent the time in reporting a bug report (or 
better yet, supply a patch) so we write out plain text. It's not like someone 
did this on purpose to annoy you.

Please take a step back and re-read what you wrote above. I hope you see that 
this is not how you interact with people.

Cheers

-- 
Milian Wolff
mail at milianw.de
http://milianw.de



More information about the KDevelop mailing list