On Tuesday, 29 August 2017 at 08:15:08 UTC, Vadim Lopatin wrote:
> On Sunday, 27 August 2017 at 10:05:29 UTC, Nicholas Wilson wrote:
>> So I will be doing a workshop on programming for the biology department at my university and I was wondering what would best suit the users.
>>
>> The following are a must:
>>     support windows & mac ( the more consistent between the two the better)
>>     free
>>     no large install footprint, preferably simple install procedure (running on laptops)
>>     syntax highlighting
>>     straightforward to use
>>
>> anything else is a bonus.
>>
>> Whats your experience with what you use?
>>
>> Many thanks
>> Nic
>
> Try DlangIDE : https://github.com/buggins/dlangide
>
> Simple IDE with DUB based project format, uses DUB to fetch dependencies, build and run projects. Support of basic debugging.
> Syntax highlight, code completion, go to definition - using DCD.
>
> Supports Windows, mac, linux.
> Precompiled binaries for Windows: https://github.com/buggins/dlangide/releases
>
> Distribution size for Windows - 5.4Mb zipped. Includes DUB and mago-mi debugger.
>
>
> For Mac, it's easy to build it using DUB.

New DlangIDE version v0.7.60 is released.
Windows binaries are available here https://github.com/buggins/dlangide/releases

On Sunday, 27 August 2017 at 10:28:29 UTC, Dukc wrote:
> The problem with geany is that it's syntax highlighting and auto-completion depend on having the file where the symbol's defined open.

No, Geany supports generation and automatic loading of global tags files:
http://www.geany.org/manual/current/#symbols-and-tags-files

On Sunday, 27 August 2017 at 12:11:14 UTC, Petar Kirov [ZombineDev] wrote:
> vim or SublimeText

I want to get into vim. It has to be vim, can't be Neovim or gvim or any other clone; I'm doing it for a Linux class. I'm on Arch Linux (or Manjaro), so I have plenty available from the official repos and plenty more from the user AUR repos.

The wiki page on vim[1] lists several plugins which I assume are mutually exclusive. DSnips[2] was very easy to install by just installing UltiSnips and placing d.snippets in its appropriate place, but it seems to only provide, as the name suggests, boilerplate snippets. Dutyl[3] seems much more interesting but also more daunting, considering that my vim knowledge so far largely consists of :wq and :q!.

Are those the two alternatives available to me?


[1]: https://wiki.dlang.org/D_in_Vim
[2]: https://github.com/kiith-sa/DSnips
[3]: https://github.com/idanarye/vim-dutyl

On Wednesday, 30 August 2017 at 11:28:35 UTC, Anonymouse wrote:
> On Sunday, 27 August 2017 at 12:11:14 UTC, Petar Kirov [ZombineDev] wrote:
>> vim or SublimeText
>
> I want to get into vim. It has to be vim, can't be Neovim or gvim or any other clone; I'm doing it for a Linux class. I'm on Arch Linux (or Manjaro), so I have plenty available from the official repos and plenty more from the user AUR repos.
>
> The wiki page on vim[1] lists several plugins which I assume are mutually exclusive. DSnips[2] was very easy to install by just installing UltiSnips and placing d.snippets in its appropriate place, but it seems to only provide, as the name suggests, boilerplate snippets. Dutyl[3] seems much more interesting but also more daunting, considering that my vim knowledge so far largely consists of :wq and :q!.
>
> Are those the two alternatives available to me?
>
>
> [1]: https://wiki.dlang.org/D_in_Vim
> [2]: https://github.com/kiith-sa/DSnips
> [3]: https://github.com/idanarye/vim-dutyl

To be honest, I'm not the right one to ask. I prefer vim (to be specific, now I use Neovim, though not to the level that I can tell difference :D) mainly because it works inside the terminal, it's easy to use (well, after I learned it), offers a ton a customization, requires no complex setup and I can find it on almost any machine.
I don't use any D specific plugins, the D syntax file that's included in the default installation is good enough for me. A couple of years ago I was into setting up IDEs and language specific plugins on editors, but nowadays I just don't bother.

My advice would be to start a basic vim installation, learn the difference between the different modes (normal, insert, visual, terminal - specific to nvim, etc.), learn the basic normal mode commands, windows splitting, macros, and so on. The best way to learn vim is to make it your default editor so that you're forced to be proficient with it. At first your productivity will be quite low, because you will be constantly looking basic stuff up, but after a while it will become part of your muscle memory, just like Ctrl+A/Z/X/C/V are probably now. There are plenty of good guides to follow, e.g.:

http://www.terminally-incoherent.com/blog/2012/03/21/why-vim/
https://scotch.io/tutorials/getting-started-with-vim-an-interactive-guide
https://gist.github.com/bpierre/0a0025d348b6001394e0
https://danielmiessler.com/study/vim/#gs.rvBIWrI

On Wednesday, 30 August 2017 at 11:28:35 UTC, Anonymouse wrote:
> Dutyl[3] seems much more interesting but also more daunting, considering that my vim knowledge so far largely consists of :wq and :q!.

Yeah, haha, that's the basic command you need to know when the time comes to rebase a git branch in console mode.

On Wednesday, 30 August 2017 at 15:27:43 UTC, b4s1L3 wrote:
> On Wednesday, 30 August 2017 at 11:28:35 UTC, Anonymouse wrote:
>> Dutyl[3] seems much more interesting but also more daunting, considering that my vim knowledge so far largely consists of :wq and :q!.
>
> Yeah, haha, that's the basic command you need to know when the time comes to rebase a git branch in console mode.

You can use any editor you want for git interactive rebase, or any other git command that needs an editor. Vi(m) is just the default if you haven't configured core.editor. For more info see: https://git-scm.com/book/tr/v2/Customizing-Git-Git-Configuration

On Sunday, 27 August 2017 at 18:08:52 UTC, Moritz Maxeiner wrote:
>> The requirements are rather vague, you can interpret it in a number of ways.
>
> The sensible interpretation imho is "as low an install footprint as possible while still fulfilling the other requirements". I'm not aware of anything below ~20MB install footprint that fulfills the other requirements, but I'd be interested if you know any.

The install requirement is arbitrary, and why 20MB? It just seems like you are trying to advertise that program for some reason.

>> I wouldn't consider 200MB gigantic in comparison to 20MB cause there is literally no difference of use for me.
>
> The thread is about OP's requirements.

So replace me with anyone.

>> You'd have to have a really shitty laptop for it to be an issue.
>
> Not relevant.

It is relevant, shit, even with a shitty laptop you can upgrade the hdd and then it becomes a non-issue anyways.

On Wednesday, August 30, 2017 11:28:35 Anonymouse via Digitalmars-d wrote:
> On Sunday, 27 August 2017 at 12:11:14 UTC, Petar Kirov
>
> [ZombineDev] wrote:
> > vim or SublimeText
>
> I want to get into vim. It has to be vim, can't be Neovim or gvim or any other clone; I'm doing it for a Linux class. I'm on Arch Linux (or Manjaro), so I have plenty available from the official repos and plenty more from the user AUR repos.

gvim and vim are the exact same program (in fact on my system, gvim is literally a symlink to vim). It's just that gvim starts vim in a Window, so you can actually do stuff like resize it. It does come with some GUI menu junk on the top by default, and using that certainly wouldn't help you learn vim, but if you use gvim and just don't use the menu stuff at the top, you're using normal vim except in a window. And if you put

" hide menu
set guioptions-=m

" hide toolbar
set guioptions-=T

in your .gvimrc, all of the GUI stuff goes away. That's what I did, and I almost always use gvim, because then it's not tied to the terminal, and it's nice and resizable. But if I do need to use vim in a terminal (e.g. because I'm using ssh without X forwarding or because the machine I'm using doesn't have X installed), it's exactly the same as in the GUI window. The only hickup there that I'm aware of is that the coloring works differently between gvim and running vim in a terminal, because gvim has a better range of colors. So, your .vimrc defines the colors for them separately, and if you're picky about the colors, you have different options in gvim than in the terminal. But all of the commands are identical, because it's the same program.

> The wiki page on vim[1] lists several plugins which I assume are mutually exclusive. DSnips[2] was very easy to install by just installing UltiSnips and placing d.snippets in its appropriate place, but it seems to only provide, as the name suggests, boilerplate snippets. Dutyl[3] seems much more interesting but also more daunting, considering that my vim knowledge so far largely consists of :wq and :q!.
>
> Are those the two alternatives available to me?
>
>
> [1]: https://wiki.dlang.org/D_in_Vim
> [2]: https://github.com/kiith-sa/DSnips
> [3]: https://github.com/idanarye/vim-dutyl

All I use is the D syntax file so that the syntax highlighting works correctly. I've never seen any need for anything else.

- Jonathan M Davis

On Wednesday, 30 August 2017 at 21:30:44 UTC, Jerry wrote:
> On Sunday, 27 August 2017 at 18:08:52 UTC, Moritz Maxeiner wrote:
>>> The requirements are rather vague, you can interpret it in a number of ways.
>>
>> The sensible interpretation imho is "as low an install footprint as possible while still fulfilling the other requirements". I'm not aware of anything below ~20MB install footprint that fulfills the other requirements, but I'd be interested if you know any.
>
> The install requirement is arbitrary, and why 20MB? It just seems like you are trying to advertise that program for some reason.

Because of the programs recommended until that post nothing was below that while meeting the other requirements (there were others in the same range, vim being one). The (later) DlangIDE recommendation, however, lowered that to about ~5MB (beating both my recommendation and vim in the process).

>
>>> I wouldn't consider 200MB gigantic in comparison to 20MB cause there is literally no difference of use for me.
>>
>> The thread is about OP's requirements.
>
> So replace me with anyone.
>
>>> You'd have to have a really shitty laptop for it to be an issue.
>>
>> Not relevant.
>
> It is relevant, shit, even with a shitty laptop you can upgrade the hdd and then it becomes a non-issue anyways.

Your argument implicitly assumed a specific reason (albeit a generally sensible one) as to why low install size was a (must) requirement (physical storage limitations being only one possible reason; shared devices with fixed disk quotas or devices owned by the university with certain policies being other possibilities). That is why I didn't (and don't) think it as relevant to the specific point about being as low as possible I was making.

On Wed, Aug 30, 2017 at 04:24:47PM -0600, Jonathan M Davis via Digitalmars-d wrote:
> On Wednesday, August 30, 2017 11:28:35 Anonymouse via Digitalmars-d wrote:
> > On Sunday, 27 August 2017 at 12:11:14 UTC, Petar Kirov
> >
> > [ZombineDev] wrote:
> > > vim or SublimeText
> >
> > I want to get into vim. It has to be vim, can't be Neovim or gvim or any other clone; I'm doing it for a Linux class. I'm on Arch Linux (or Manjaro), so I have plenty available from the official repos and plenty more from the user AUR repos.
[...]
> All I use is the D syntax file so that the syntax highlighting works correctly. I've never seen any need for anything else.
[...]

I use vim for D coding (well, all coding... and actually, I'm also typing this in vim), and I don't even use a syntax file.  D is not like Java where you need an IDE to deal with the verbosity; it's actually quite comfortable to write, and if formatted properly, easy to read without needing any special highlighting.

But that's just my personal preference.  YMMV.


T

-- 
There are 10 kinds of people in the world: those who can count in binary, and those who can't.