[gmx-developers] gerrit syntax highlighting for CUDA/OpenCL sources

Szilárd Páll pall.szilard at gmail.com
Thu Apr 11 00:11:12 CEST 2019


On Thu, Apr 11, 2019 at 12:04 AM Benson Muite <benson_muite at emailplus.org>
wrote:

> Possible solutions:
>
> a) View the code through another site that will add syntax highlighting,
> for example using highlight.js (https://highlightjs.org)
>
I want the diff view in gerrit to have highlighting; if I have to do
something extra, I might as well just switch back to the old site layout
and pick the language manually.

> b) Add a plugin to Gerrit:
>
> https://gerrit.googlesource.com/gerrit/+/master/SUBMITTING_PATCHES
>

I don't see which plugin are you suggesting to add.

--
Szilárd

>
> On 4/10/19 11:46 PM, Szilárd Páll wrote:
>
> Sure, most editors and IDE's have syntax highlighting build in or easily
> enabled through plugins for both CUDA and OpenCL.
>
> Cheers,
> --
> Szilárd
>
>
> On Wed, Apr 10, 2019 at 3:57 PM Benson Muite <benson_muite at emailplus.org>
> wrote:
>
>> Hi,
>>
>> How do you typically get syntax highlighting when writing code locally?
>> For example do you use any of the items below:
>>
>> https://github.com/podgib/atom-opencl
>>
>> https://streamhpc.com/blog/2011-02-01/gedit-opencl-syntax-highlighting/
>>
>> https://github.com/bfrg/vim-cuda-syntax
>>
>> http://ftp.vim.org/vim/runtime/syntax/cuda.vim
>>
>> https://github.com/petRUShka/vim-opencl
>> Regards,
>> Benson
>> On 4/10/19 3:45 PM, Szilárd Páll wrote:
>>
>> Hi,
>>
>> Traditionally, syntax highlighting of .cu/.cuh/.clh files has been a bit
>> of a pain and I've always had to manually visit the diff preferences every
>> time I opened one of these files and set C++ or C in the "Language"
>> drop-down.
>>
>> While the new interface with the recent upgrade is a decent improvement
>> that almost made me switch, they removed the ability to manually set the
>> language in the diff view prefs. Reviewing CUDA and OpenCL without syntax
>> highlighting is too much of a pain, so I thought I'd ask:
>> - does anybody had a workaround?
>> - does anyone know of a plugin or server-side config that would allow
>> implementing a workaround e.g. permanently mapping these sources to have
>> C++ syntax highlighting?
>>
>> Cheers,
>> --
>> Szilárd
>>
>> --
>> Gromacs Developers mailing list
>>
>> * Please search the archive at
>> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
>> posting!
>>
>> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>>
>> * For (un)subscribe requests visit
>> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
>> or send a mail to gmx-developers-request at gromacs.org.
>
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20190410/d42c97a9/attachment-0001.html>


More information about the gromacs.org_gmx-developers mailing list