https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #8 from Christoph Cullmann ---
(In reply to Albert Astals Cid from comment #7)
> (In reply to Dominik Haumann from comment #6)
> > I second that: Without Kate being able to access arbitrary tools, Kate's
> > functionality will be very limite
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #7 from Albert Astals Cid ---
(In reply to Dominik Haumann from comment #6)
> I second that: Without Kate being able to access arbitrary tools, Kate's
> functionality will be very limited, and we'll get bug reports about it.
>
> Packaging g
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #6 from Dominik Haumann ---
I second that: Without Kate being able to access arbitrary tools, Kate's
functionality will be very limited, and we'll get bug reports about it.
Packaging git is not the correct approach. Can't access to the syst
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #5 from Christoph Cullmann ---
Hmm, can't we have just access to the system?
Git will not be enough, for example for the LSP stuff, we need a lot more
tools.
Same for "External Commands".
For LSP that would be all we have here:
https://i
https://bugs.kde.org/show_bug.cgi?id=431223
--- Comment #4 from Albert Astals Cid ---
If being able to run git is needed for this that is defenitely the case.
I'll see how hard is to package git in the kate flatpak
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431223
Christoph Cullmann changed:
What|Removed |Added
Resolution|DUPLICATE |---
Summary|Projects plugin doe
