[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: kate lsp client plugin
From: Dominik Haumann <dhaumann () kde ! org>
Date: 2019-06-26 9:40:15
Message-ID: CALi_srC=c3pHw8XVhzS4GGGaO3SV_vXFw8Jc+HWhWcGnUkrMXA () mail ! gmail ! com
[Download RAW message or body]
Hi Mark,
in that case, I suggest you ask the KDE sysadmins for a KDE contributor
account.
To do so, follow
https://community.kde.org/index.php?title=Infrastructure/Get_a_Developer_Account
You can refer to this discussion
https://marc.info/?l=kwrite-devel&m=156149161801136&w=2 when asking for the
account.
Best regards
Dominik
On Tue, Jun 25, 2019 at 11:59 PM Mark Nauwelaerts <
mark.nauwelaerts@gmail.com> wrote:
> On 25/06/19 21:40, Christoph Cullmann wrote:
> > On 2019-06-25 14:53, Christoph Cullmann wrote:
> >> Hi,
> >>
> >>> Thanks for the positive feedback and reception! I will continue to
> >>> work on it and if/when useful post some spam^Hupdate on progress. I
> >>> will also have a look at supporting standalone compilation, as
> >>> suggested ...
> >>
> >> Given one can just copy the plugin directory into the addons directory
> of
> >> the normal kate.git (and add it to cmakelists.txt) I would not spend
> time on the
> >> standalone compile.
> >>
> >> Actually, one could develop later on it even if we don't directly
> release it
> >> per default in the normal kate.git and just keep it default off for
> >> the compilation.
> > Hi,
> >
> > I have given your plugin a try here ;=)
> >
> > I must confess, it does all things better than my quick hack!
> >
> > Actually, to get more people out there testing it, I would think
> > it might make sense to move development to the normal kate.git
> > and just not activate the compile of the plugin per default.
> >
> > Would that be interesting for you or do you want to keep developing
> > it on your own repo?
> >
> > Greetings
> > Christoph
> >
> Thanks, nice to hear it also works elsewhere rather than just Works For Me
> ;-)
>
> It's written to be used/tested and to be(come) part of Kate, so if I can
> put/push things there so it's picked up easier (and by more people), then
> moving
> that way (with optional compilation and so) is fine by me :-)
>
> At least, that is assuming that it can be arranged that I can somehow
> still
> carry on (hopefully fast paced) development (in coming weeks) in an easy
> way,
> i.e. with some fairly discretionary "commit and push" ability (on plugin
> code).
> Whether we are then talking about master or (more likely) some other
> (lspclient?) branch. I am not up to specs on applied development
> practices
> (yet) in such regard ... And suffice it to say I don't have any such
> access to
> kate.git at this time ;-).
>
> Regards,
> Mark.
>
[Attachment #3 (text/html)]
<div dir="ltr"><div>Hi Mark,</div><div><br></div><div>in that case, I suggest you ask \
the KDE sysadmins for a KDE contributor account.</div><div>To do so, follow <a \
href="https://community.kde.org/index.php?title=Infrastructure/Get_a_Developer_Account \
">https://community.kde.org/index.php?title=Infrastructure/Get_a_Developer_Account</a></div><div><br></div><div>You \
can refer to this discussion <a \
href="https://marc.info/?l=kwrite-devel&m=156149161801136&w=2">https://marc.info/?l=kwrite-devel&m=156149161801136&w=2</a> \
when asking for the account.</div><div></div><div><br></div><div>Best \
regards</div><div>Dominik<br></div><div><br></div><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Tue, Jun 25, 2019 at 11:59 PM Mark Nauwelaerts <<a \
href="mailto:mark.nauwelaerts@gmail.com">mark.nauwelaerts@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 25/06/19 21:40, \
Christoph Cullmann wrote:<br> > On 2019-06-25 14:53, Christoph Cullmann wrote:<br>
>> Hi,<br>
>><br>
>>> Thanks for the positive feedback and reception! I will continue to<br>
>>> work on it and if/when useful post some spam^Hupdate on progress. \
I<br> >>> will also have a look at supporting standalone compilation, as<br>
>>> suggested ...<br>
>><br>
>> Given one can just copy the plugin directory into the addons directory \
of<br> >> the normal kate.git (and add it to cmakelists.txt) I would not spend \
time on the<br> >> standalone compile.<br>
>><br>
>> Actually, one could develop later on it even if we don't directly \
release it<br> >> per default in the normal kate.git and just keep it default \
off for<br> >> the compilation.<br>
> Hi,<br>
><br>
> I have given your plugin a try here ;=)<br>
><br>
> I must confess, it does all things better than my quick hack!<br>
><br>
> Actually, to get more people out there testing it, I would think<br>
> it might make sense to move development to the normal kate.git<br>
> and just not activate the compile of the plugin per default.<br>
><br>
> Would that be interesting for you or do you want to keep developing<br>
> it on your own repo?<br>
><br>
> Greetings<br>
> Christoph<br>
><br>
Thanks, nice to hear it also works elsewhere rather than just Works For Me ;-)<br>
<br>
It's written to be used/tested and to be(come) part of Kate, so if I can <br>
put/push things there so it's picked up easier (and by more people), then moving \
<br> that way (with optional compilation and so) is fine by me :-)<br>
<br>
At least, that is assuming that it can be arranged that I can somehow still <br>
carry on (hopefully fast paced) development (in coming weeks) in an easy way, <br>
i.e. with some fairly discretionary "commit and push" ability (on plugin \
code). <br> Whether we are then talking about master or (more likely) some other \
<br> (lspclient?) branch. I am not up to specs on applied development practices \
<br> (yet) in such regard ... And suffice it to say I don't have any such access \
to <br> kate.git at this time ;-).<br>
<br>
Regards,<br>
Mark.<br>
</blockquote></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic