On Wednesday, 5 October 2016 at 05:53:06 UTC, Suliman wrote:
> Please, add Sublime support

+1 for Sublime Support :)

On Tuesday, 4 October 2016 at 19:28:27 UTC, WebFreak001 wrote:
> I've been working a lot on the new features for code-d to improve the user experience for new users and lower the barrier of creating D projects.

What I really wish I had was integration with the compilation process (either pure (r)dmd or dub), since having to manually find in my editor the error lines mentioned by the compiler is quite inconvenient.

Debugging is probably a pipedream, no?

On Thursday, 6 October 2016 at 11:39:17 UTC, Luís Marques wrote:
> On Tuesday, 4 October 2016 at 19:28:27 UTC, WebFreak001 wrote:
>> I've been working a lot on the new features for code-d to improve the user experience for new users and lower the barrier of creating D projects.
>
> What I really wish I had was integration with the compilation process (either pure (r)dmd or dub), since having to manually find in my editor the error lines mentioned by the compiler is quite inconvenient.
>
> Debugging is probably a pipedream, no?

code-d runs dub to get the compiler errors and display them, just press the errors/warnings button at the bottom left.

Debugging is also implemented if you install my second extension if you search for `webfreak.debug` in the extension search. Then using the code-d debug button in the statusbar you can debug your app. Works on linux, windows and osx assuming you have the debuggers installed (on windows if you magically get gdb or lldb working then thats great but otherwise there is also Mago/MI support)

On Thursday, 6 October 2016 at 16:43:56 UTC, WebFreak001 wrote:
> code-d runs dub to get the compiler errors and display them, just press the errors/warnings button at the bottom left.

Nope, the errors/warnings is always empty for me. I'm on a Mac.

On Thursday, 6 October 2016 at 18:43:14 UTC, Luís Marques wrote:
> On Thursday, 6 October 2016 at 16:43:56 UTC, WebFreak001 wrote:
>> code-d runs dub to get the compiler errors and display them, just press the errors/warnings button at the bottom left.
>
> Nope, the errors/warnings is always empty for me. I'm on a Mac.

oh right there is some bug on mac causing most features to not work, not really sure why. It just gets stuck in some system call (process spawn)

But that should only affect auto completion, static code analysis and make code formatting delayed. Showing dub errors should still work

On Thursday, 6 October 2016 at 16:43:56 UTC, WebFreak001 wrote:
> Debugging is also implemented if you install my second extension if you search for `webfreak.debug` in the extension search. Then using the code-d debug button in the statusbar you can debug your app. Works on linux, windows and osx assuming you have the debuggers installed (on windows if you magically get gdb or lldb working then thats great but otherwise there is also Mago/MI support)

I don't see any code-d debug button in the statusbar. In any case, I don't know if this is supposed to work if the basic code-d building doesn't work (although without any visible errors; I fixed the only error, a wrong default import path setting).

On Tuesday, 4 October 2016 at 19:28:27 UTC, WebFreak001 wrote:
> I've been working a lot on the new features for code-d to improve the user experience for new users and lower the barrier of creating D projects.
Will there be support for looking for dscanner.ini in .config rather than in project directory?

On Saturday, 8 October 2016 at 00:30:32 UTC, Soulsbane wrote:
> On Tuesday, 4 October 2016 at 19:28:27 UTC, WebFreak001 wrote:
>> I've been working a lot on the new features for code-d to improve the user experience for new users and lower the barrier of creating D projects.
> Will there be support for looking for dscanner.ini in .config rather than in project directory?

good idea, added it as an issue to workspace-d: https://github.com/Pure-D/workspace-d/issues/47

On Tuesday, 4 October 2016 at 19:28:27 UTC, WebFreak001 wrote:
> * detection of missing tools & installation

I'm trying to use VSCode/mac-os and getting some errors.

First, I tried to install all the required tools, and got an error because the installation/compilation couldn't find the new experimental allocators. Updating dmd fixed this, but there didn't seem to be any explicit check/message that dmd was out of date IIRC.

After updating DMD, 3 of the tools seemed to have installed correctly, but I am still getting this error:

"workspace-d is not installed or points to a folder"

I tried setting "d.workspacedPath" in user settings to the executable in the /Users/me/.vscode/extensions/... folder, but it still doesn't work.

Also, unrelated to the above, I've set"d.stdlibPath" to the appropriate paths, but completion still doesn't work. I'm guessing workspace-d not being found has something to do with this..?

Anyways, thanks for the good work. Can't wait to get this thing up and running.

On Saturday, 8 October 2016 at 17:27:03 UTC, bitwise wrote:
> On Tuesday, 4 October 2016 at 19:28:27 UTC, WebFreak001 wrote:
>> * detection of missing tools & installation
>
> I'm trying to use VSCode/mac-os and getting some errors.
>
> First, I tried to install all the required tools, and got an error because the installation/compilation couldn't find the new experimental allocators. Updating dmd fixed this, but there didn't seem to be any explicit check/message that dmd was out of date IIRC.
>
> After updating DMD, 3 of the tools seemed to have installed correctly, but I am still getting this error:
>
> "workspace-d is not installed or points to a folder"
>
> I tried setting "d.workspacedPath" in user settings to the executable in the /Users/me/.vscode/extensions/... folder, but it still doesn't work.
>
> Also, unrelated to the above, I've set"d.stdlibPath" to the appropriate paths, but completion still doesn't work. I'm guessing workspace-d not being found has something to do with this..?
>
> Anyways, thanks for the good work. Can't wait to get this thing up and running.

auto completion won't appear when workspace-d is not installed, workspace-d is the thing that calls all of the other executables. Try deleting the executable from /Users/me/.vscode/extensions/code-d.../bin/workspace-d and then try to reinstall it again using code-d