Re: KDevelop is nice but...

Javier Guerra Giraldez <[email protected]>
Newsgroups gmane.comp.kde.users.kdevelop
Message-ID <CAFkDaoSP94n+0Gogcw7LLyJDsKpKGVHL8d5tpevEvirAjRV53w@mail.gmail.com>
On Tue, 12 Feb 2019 at 09:11, Sven Brauch <mail-ITmcY+a7/[email protected]> wrote:
> On Tuesday, 12 February 2019 01:26:52 CET Praise wrote:
> > 1) I cannot see what file are modified or need an update on git. CLion makes
> > me see file names in a different color.
>
> The VCS code is a little convoluted, but that sounds useful and doable.

Personal preference:  use the "Documents" pane from Kate.  it does
show modified files, and it's far easier to see how open files are a
subset of the filesystem.  (it also looks better)


> > 4) When creating a new cpp file I would really love to select CMake’s target
> > to add it immediately, and to add it to git.
>
> We once had code modifying cmake files, but I think it died together with the
> cmake-parser-based cmake support ...
> The simple case may be realistic to get right, in the general case cmake is a
> very complex language to modify automatically.


how about a simple CLI tool that outputs the list of project files
(with optional filters), it could be used from Makefiles and (most?)
other scripts.

something like:

#> kdev_proj_files $projectdir  *.cpp
src/main.cpp
lib/myusefulobj.cpp

#> kdev_proj_files $projectdir *.h
src/config.h
lib/myusefulobj.h




-- 
Javier
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.