What is the best way to develop for pandocs?

What is the best way to develop for pandocs?

['Johannes Aram Unruh' via pandoc-discuss]

[-- Attachment #1.1: Type: text/plain, Size: 959 bytes --]

I am rather new to Haskell and I am trying to set up a dev environment 
using VSCode and and the "Haskel" extension relying on the "Haskell 
Language Server". 
I can not get the VSCode to properly work with the pandoc repo. 
Autocomplete doesn't work and going to definitions does neither. 
Can someone tell me what a good setup would look like and what best 
practices would be.

Also I do not seem to have *Paths_pandoc *in the source code when I clone 
it. VSCode tells me it cant finde the import.

Thank you very much.
Best regards, 
Johannes

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/170e68ae-579e-4859-9110-ae8d40533231n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1283 bytes --]

Re: What is the best way to develop for pandocs?

[Albert Krewinkel]

Hello Johannes,

'Johannes Aram Unruh' via pandoc-discuss writes:

> I am rather new to Haskell and I am trying to set up a dev environment
> using VSCode and and the "Haskel" extension relying on the "Haskell
> Language Server".
> I can not get the VSCode to properly work with the pandoc repo.
> Autocomplete doesn't work and going to definitions does neither.
> Can someone tell me what a good setup would look like and what best
> practices would be.

Thanks for your interest in pandoc development! I do not have much
experience with VSCode, but the Haskell discourse forum would be a good
place to get more information: <https://discourse.haskell.org>

> Also I do not seem to have *Paths_pandoc *in the source code when I clone
> it. VSCode tells me it cant finde the import.

The `Paths_*` packages are auto-generated by cabal during compilation:
<https://cabal.readthedocs.io/en/3.4/cabal-package.html#accessing-data-files-from-package-code>
Apparently this is tripping the VSCode plugin up. It might help to
compile the project at least once.

Cheers,
Albert

--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124

Re: What is the best way to develop for pandocs?

['Johannes Aram Unruh' via pandoc-discuss]

[-- Attachment #1.1: Type: text/plain, Size: 2154 bytes --]

Thank you for your response. I will take a look at the 
discourse.haskell.org.

Regarding the "Paths_*" module:
I did that already using ```stack build```. But this command installs this 
file into 
```./.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/build/pandoc/autogen/Paths_pandoc.hs``` 
in my case. So my guess would be that this is the reason for the VSCode not 
finding that file. Where should I copy it to in ordere to make this work?

Best regards,

Johannes

Albert Krewinkel schrieb am Montag, 26. Oktober 2020 um 14:55:38 UTC+1:

> Hello Johannes,
>
> 'Johannes Aram Unruh' via pandoc-discuss writes:
>
> > I am rather new to Haskell and I am trying to set up a dev environment
> > using VSCode and and the "Haskel" extension relying on the "Haskell
> > Language Server".
> > I can not get the VSCode to properly work with the pandoc repo.
> > Autocomplete doesn't work and going to definitions does neither.
> > Can someone tell me what a good setup would look like and what best
> > practices would be.
>
> Thanks for your interest in pandoc development! I do not have much
> experience with VSCode, but the Haskell discourse forum would be a good
> place to get more information: <https://discourse.haskell.org>
>
> > Also I do not seem to have *Paths_pandoc *in the source code when I clone
> > it. VSCode tells me it cant finde the import.
>
> The `Paths_*` packages are auto-generated by cabal during compilation:
> <
> https://cabal.readthedocs.io/en/3.4/cabal-package.html#accessing-data-files-from-package-code
> >
> Apparently this is tripping the VSCode plugin up. It might help to
> compile the project at least once.
>
> Cheers,
> Albert
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/3bc5bbdf-7e0e-4b04-921b-660554fafcb4n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3511 bytes --]

Re: What is the best way to develop for pandocs?

[Leonard Rosenthol]

[-- Attachment #1: Type: text/plain, Size: 3373 bytes --]

My setup for VSCode and Haskell is working fine - though I do all the
building myself on the command line/terminal (but that's only because I
haven't setup the debug configs).

I have the following Haskell extensions installed in VSCode:
- Haskell (1.2)
- Haskell GHCi Debug Adapter (0.25)
- Haskell Syntax Highlighting (3.3)
- Haskell-linter (0.0.6)
- Haskelly (0.5.5)

Not sure if I need all, but that's what I have...

Leonard

On Mon, Oct 26, 2020 at 10:06 AM 'Johannes Aram Unruh' via pandoc-discuss <
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:

> Thank you for your response. I will take a look at the
> discourse.haskell.org.
>
> Regarding the "Paths_*" module:
> I did that already using ```stack build```. But this command installs this
> file into
> ```./.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/build/pandoc/autogen/Paths_pandoc.hs```
> in my case. So my guess would be that this is the reason for the VSCode not
> finding that file. Where should I copy it to in ordere to make this work?
>
> Best regards,
>
> Johannes
>
> Albert Krewinkel schrieb am Montag, 26. Oktober 2020 um 14:55:38 UTC+1:
>
>> Hello Johannes,
>>
>> 'Johannes Aram Unruh' via pandoc-discuss writes:
>>
>> > I am rather new to Haskell and I am trying to set up a dev environment
>> > using VSCode and and the "Haskel" extension relying on the "Haskell
>> > Language Server".
>> > I can not get the VSCode to properly work with the pandoc repo.
>> > Autocomplete doesn't work and going to definitions does neither.
>> > Can someone tell me what a good setup would look like and what best
>> > practices would be.
>>
>> Thanks for your interest in pandoc development! I do not have much
>> experience with VSCode, but the Haskell discourse forum would be a good
>> place to get more information: <https://discourse.haskell.org>
>>
>> > Also I do not seem to have *Paths_pandoc *in the source code when I
>> clone
>> > it. VSCode tells me it cant finde the import.
>>
>> The `Paths_*` packages are auto-generated by cabal during compilation:
>> <
>> https://cabal.readthedocs.io/en/3.4/cabal-package.html#accessing-data-files-from-package-code>
>>
>> Apparently this is tripping the VSCode plugin up. It might help to
>> compile the project at least once.
>>
>> Cheers,
>> Albert
>>
>> --
>> Albert Krewinkel
>> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/3bc5bbdf-7e0e-4b04-921b-660554fafcb4n%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/3bc5bbdf-7e0e-4b04-921b-660554fafcb4n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CALu%3Dv3%2B8aj_3panz3a3gm6j%2Bn8fR6co4xbLFC8x_44u9n-iVOw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 4942 bytes --]

Re: What is the best way to develop for pandocs?

['Johannes Aram Unruh' via pandoc-discuss]

[-- Attachment #1.1: Type: text/plain, Size: 3671 bytes --]

Thank you for your input. My setup also works for other projects, I just 
don't seem to be able to get it working for Pandoc.

Leonard Rosenthol schrieb am Montag, 26. Oktober 2020 um 15:20:58 UTC+1:

> My setup for VSCode and Haskell is working fine - though I do all the 
> building myself on the command line/terminal (but that's only because I 
> haven't setup the debug configs).
>
> I have the following Haskell extensions installed in VSCode:
> - Haskell (1.2)
> - Haskell GHCi Debug Adapter (0.25)
> - Haskell Syntax Highlighting (3.3)
> - Haskell-linter (0.0.6)
> - Haskelly (0.5.5)
>
> Not sure if I need all, but that's what I have...
>
> Leonard
>
> On Mon, Oct 26, 2020 at 10:06 AM 'Johannes Aram Unruh' via pandoc-discuss <
> pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
>
>> Thank you for your response. I will take a look at the 
>> discourse.haskell.org.
>>
>> Regarding the "Paths_*" module:
>> I did that already using ```stack build```. But this command installs 
>> this file into 
>> ```./.stack-work/dist/x86_64-osx/Cabal-2.4.0.1/build/pandoc/autogen/Paths_pandoc.hs``` 
>> in my case. So my guess would be that this is the reason for the VSCode not 
>> finding that file. Where should I copy it to in ordere to make this work?
>>
>> Best regards,
>>
>> Johannes
>>
>> Albert Krewinkel schrieb am Montag, 26. Oktober 2020 um 14:55:38 UTC+1:
>>
>>> Hello Johannes, 
>>>
>>> 'Johannes Aram Unruh' via pandoc-discuss writes: 
>>>
>>> > I am rather new to Haskell and I am trying to set up a dev environment 
>>> > using VSCode and and the "Haskel" extension relying on the "Haskell 
>>> > Language Server". 
>>> > I can not get the VSCode to properly work with the pandoc repo. 
>>> > Autocomplete doesn't work and going to definitions does neither. 
>>> > Can someone tell me what a good setup would look like and what best 
>>> > practices would be. 
>>>
>>> Thanks for your interest in pandoc development! I do not have much 
>>> experience with VSCode, but the Haskell discourse forum would be a good 
>>> place to get more information: <https://discourse.haskell.org> 
>>>
>>> > Also I do not seem to have *Paths_pandoc *in the source code when I 
>>> clone 
>>> > it. VSCode tells me it cant finde the import. 
>>>
>>> The `Paths_*` packages are auto-generated by cabal during compilation: 
>>> <
>>> https://cabal.readthedocs.io/en/3.4/cabal-package.html#accessing-data-files-from-package-code> 
>>>
>>> Apparently this is tripping the VSCode plugin up. It might help to 
>>> compile the project at least once. 
>>>
>>> Cheers, 
>>> Albert 
>>>
>>> -- 
>>> Albert Krewinkel 
>>> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124 
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "pandoc-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/3bc5bbdf-7e0e-4b04-921b-660554fafcb4n%40googlegroups.com 
>> <https://groups.google.com/d/msgid/pandoc-discuss/3bc5bbdf-7e0e-4b04-921b-660554fafcb4n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a74cbdbe-a93f-419b-8c59-57ff47261de9n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 6347 bytes --]