[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Open Header plugin for OCaml
From:       Dominik Haumann <dhaumann () kde ! org>
Date:       2019-12-30 22:22:22
Message-ID: CALi_srCoQBxCVAxH6K+XiX0pD==xhxgrOXmqO99fKghoE1acJA () mail ! gmail ! com
[Download RAW message or body]

Hi Christoph,

this is a really good idea.

+1

Dominik

Christoph Cullmann <christoph@cullmann.io> schrieb am Mo., 30. Dez. 2019,
20:43:

> On 2019-12-29 21:43, Christoph Cullmann wrote:
> >> My idea what to adapt the Open Header to do the job done in
> >> PluginKateOpenHeader::slotOpenHeader() for sources/headers also for
> >> OCaml implementations/interfaces, and mention .ml/.mli in UI strings &
> >> documentation. The work done is not really difficult, I have most of
> >> locally already.
> >>
> >> Before I go ahead and push it, is there anything wrong in the approach
> >> I took?
> >
> > Hi,
> >
> > No, I think that is the way to go.
> >
> > Using ocaml sometimes, too, this sounds like a nice enhancement.
> Hi,
>
> I thought about a different way to tackle this with a more "generic"
> approach:
>
> We could:
>
> 1) Get the list of all files in the same dir that match the current
> basename with any extension
>
> 2) Get the syntax highlighting definition for each of these files (and
> our original one) via the matching KSyntaxHighlighting function
>
> 3) Then open the file that has the same definition than the original
> file
>
> This should work for any language that has pairs of XX.foo XX.bar files.
>
> Btw., I see you have taken care of the changes in OCaml Merlin ;=)
>
> Nice!
>
> I need to work on OCaml stuff at company, too.
>
> Greetings
> Christoph
>
> --
> Ignorance is bliss...
> https://cullmann.io | https://kate-editor.org
>

[Attachment #3 (text/html)]

<div dir="auto">Hi Christoph,<div dir="auto"><br></div><div dir="auto">this is a \
really good idea.</div><div dir="auto"><br></div><div dir="auto">+1</div><div \
dir="auto"><br></div><div dir="auto">Dominik</div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Christoph Cullmann &lt;<a \
href="mailto:christoph@cullmann.io">christoph@cullmann.io</a>&gt; schrieb am Mo., 30. \
Dez. 2019, 20:43:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On 2019-12-29 21:43, Christoph \
Cullmann wrote:<br> &gt;&gt; My idea what to adapt the Open Header to do the job done \
in<br> &gt;&gt; PluginKateOpenHeader::slotOpenHeader() for sources/headers also \
for<br> &gt;&gt; OCaml implementations/interfaces, and mention .ml/.mli in UI strings \
&amp;<br> &gt;&gt; documentation. The work done is not really difficult, I have most \
of<br> &gt;&gt; locally already.<br>
&gt;&gt; <br>
&gt;&gt; Before I go ahead and push it, is there anything wrong in the approach<br>
&gt;&gt; I took?<br>
&gt; <br>
&gt; Hi,<br>
&gt; <br>
&gt; No, I think that is the way to go.<br>
&gt; <br>
&gt; Using ocaml sometimes, too, this sounds like a nice enhancement.<br>
Hi,<br>
<br>
I thought about a different way to tackle this with a more &quot;generic&quot; <br>
approach:<br>
<br>
We could:<br>
<br>
1) Get the list of all files in the same dir that match the current <br>
basename with any extension<br>
<br>
2) Get the syntax highlighting definition for each of these files (and <br>
our original one) via the matching KSyntaxHighlighting function<br>
<br>
3) Then open the file that has the same definition than the original <br>
file<br>
<br>
This should work for any language that has pairs of XX.foo XX.bar files.<br>
<br>
Btw., I see you have taken care of the changes in OCaml Merlin ;=)<br>
<br>
Nice!<br>
<br>
I need to work on OCaml stuff at company, too.<br>
<br>
Greetings<br>
Christoph<br>
<br>
-- <br>
Ignorance is bliss...<br>
<a href="https://cullmann.io" rel="noreferrer noreferrer" \
target="_blank">https://cullmann.io</a> | <a href="https://kate-editor.org" \
rel="noreferrer noreferrer" target="_blank">https://kate-editor.org</a><br> \
</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]