[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: Re: [Bug 99469] New: WISH qmake project gui should preserve hand written .pro code
From: kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date: 2005-02-16 15:24:41
Message-ID: 1835eb020502160724730eedf0 () mail ! gmail ! com
[Download RAW message or body]
I use hand-written .pro files in kdevelop all the time. My
hand-written lines are preserved.
Maybe give an example of a file that gets cripled?
Greetz,
JeDi
On Tue, 15 Feb 2005 09:57:10 -0800 (PST),
kdevelop-bugs-admin@barney.cs.uni-potsdam.de
<kdevelop-bugs-admin@barney.cs.uni-potsdam.de> wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=99469
> Summary: WISH qmake project gui should preserve hand written .pro
> code
> Product: kdevelop
> Version: 3.1.92
> Platform: unspecified
> OS/Version: Linux
> Status: UNCONFIRMED
> Severity: wishlist
> Priority: NOR
> Component: trollproject
> AssignedTo: kdevelop-bugs kdevelop org
> ReportedBy: maciek ict pwr wroc pl
>
> Version: 3.1.92 (using KDE 3.3.2, compiled sources)
> Compiler: gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)
> OS: Linux (i686) release 2.4.22-1.2188.nptl
>
> qmake project gui should preserve hand-written code in .pro files. QMake is very \
> powerful tool, and limiting it to gui-configurable simple dependency and compiler \
> options manager cripples it.
> idea: Simple way to do separate machine-generated and hand-writte code is to \
> enclose the machine part in some kind of brackets in comments:
> .. my code
> # {{{KDEVELOP
> ... kdevelop
> # }}}KDEVELOP
> .. my code
>
> _______________________________________________
> KDevelop-bugs mailing list
> KDevelop-bugs@barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic