[go-nuts] Re: go language sensitive editor?

Okay, while some of us are reminiscing about ed, here is my story. When I first used Unix in 1980, I learned vi, and that was my primary editor for many years. However, I learned about ed and found it to be useful in the days before windowing systems. When I would get a compile error, I

[go-nuts] Re: go language sensitive editor?

Thanks for pointing out. I have updated the README: https://github.com/serge-v/micro/blob/master/README.md#fork-changes On Saturday, November 24, 2018 at 10:25:41 AM UTC-5, Mandolyte wrote: > > Hmmm, couldn't we follow directions to build from zyedidia, substituting > your repo as needed? If

[go-nuts] Re: go language sensitive editor?

Hmmm, couldn't we follow directions to build from zyedidia, substituting your repo as needed? If so, have you documented anywhere how to use your extensions? I didn't notice any mods to the README. Cheers! On Wednesday, November 21, 2018 at 4:57:05 PM UTC-5, Serge Voilokov wrote: > > I am

Re: [go-nuts] Re: go language sensitive editor?

On Fri, Nov 23, 2018 at 11:40 AM Serge Voilokov wrote: > > No, no plans to PR for a while since I implemented the features directly > in the source tree. > I need to think how to wrap them as plugins for dynamic download. > What you believe can benefit yourself can surely benefit the Go

[go-nuts] Re: go language sensitive editor?

A vote for Goland from me. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit

Re: [go-nuts] Re: go language sensitive editor?

Hi Rob, Thanks for the link to that talk. I had many of the same early experiences, including using an IBM keypunch and interacting with an IBM 360 (programming in APL) over a modem line. My first programming job was in 1981 on a VAX11/780 running UNIX/32V (with 7th edition manuals) in the

Re: [go-nuts] Re: go language sensitive editor?

Agree on this. Gorename and gofmt etc provide only a small subset of what is on GoLands roadmap. I toggle between vs code, vim(-go), and GoLand. There’s bits I like about all 3 but if I had to choose only one I’d probably go with GoLand. On Tue, Nov 20, 2018 at 20:24, robert engels wrote: > I

[go-nuts] Re: go language sensitive editor?

Tong, No, no plans to PR for a while since I implemented the features directly in the source tree. I need to think how to wrap them as plugins for dynamic download. On Thursday, November 22, 2018 at 10:41:47 PM UTC-5, Tong Sun wrote: > > Nice added features Serge. > > Any plan to PR them back,

[go-nuts] Re: go language sensitive editor?

Nice added features Serge. Any plan to PR them back, or you'd rather keep your fork to your self? Thx. On Wednesday, November 21, 2018 at 4:57:05 PM UTC-5, Serge Voilokov wrote: > > I am using micro editor: https://github.com/zyedidia/micro . It is > terminal-based, supports mouse, uses

Re: [go-nuts] Re: go language sensitive editor?

And 15 years later, so one hopes for an improvement. The thing people ignore, or perhaps just don't know, about ed was that it was a breath of fresh air compared to all the commercial editors available at time. People judge it by the standards of today; by the standards of the time it was

Re: [go-nuts] Re: go language sensitive editor?

But sam is a pretty solid improvement over ed. On Tue, Nov 20, 2018 at 6:04 PM Rob Pike wrote: > > Ed is the standard text editor. > > -rob > > > On Wed, Nov 21, 2018 at 8:15 AM wrote: >> >> >> Another vote for VS Code. I'm a hobbyist and have tried lots of editors. >> >> On Tuesday, November

Re: [go-nuts] Re: go language sensitive editor?

http://man.cat-v.org/unix-6th/1/ed On Fri, Nov 23, 2018 at 12:48 AM Anirudh Vyas wrote: > Could never get this one - Ed is the standard editor, is there a > historical context of this? Did people say this a lot back when there were > vim emacs and Ed only as choices of editors? > On Nov 22,

Re: [go-nuts] Re: go language sensitive editor?

https://www.gnu.org/fun/jokes/ed-msg.html On Thursday, 22 November 2018 13:49:09 UTC, Anirudh Vyas wrote: > > Could never get this one - Ed is the standard editor, is there a > historical context of this? Did people say this a lot back when there were > vim emacs and Ed only as choices of

Re: [go-nuts] Re: go language sensitive editor?

Could never get this one - Ed is the standard editor, is there a historical context of this? Did people say this a lot back when there were vim emacs and Ed only as choices of editors? On Nov 22, 2018, 05:28 -0800, Volker Dobler , wrote: > As emacs has not been recommended yet: Emacs! > > V. > >

[go-nuts] Re: go language sensitive editor?

As emacs has not been recommended yet: Emacs! V. On Tuesday, 20 November 2018 21:52:11 UTC+1, Pat Farrell wrote: > > I know, this is both a FAQ and an unanswerable question. I'm an old > programmer who has used nearly every editor known to man. I am not a fan of > whole-universe IDEs, but can

[go-nuts] Re: go language sensitive editor?

LiteIDE here. https://github.com/visualfc/liteide On Wednesday, November 21, 2018 at 12:52:11 AM UTC+4, Pat Farrell wrote: > > I know, this is both a FAQ and an unanswerable question. I'm an old > programmer who has used nearly every editor known to man. I am not a fan of > whole-universe IDEs,

[go-nuts] Re: go language sensitive editor?

I am using micro editor: https://github.com/zyedidia/micro . It is terminal-based, supports mouse, uses ctrl+zxcv and shift+arrows for text manipulation, has a multi cursor feature, syntax highlighting. Written in golang. Easy to configure and change. I am using my fork

[go-nuts] Re: go language sensitive editor?

If you using vim: https://github.com/fatih/vim-go On Tuesday, November 20, 2018 at 12:52:11 PM UTC-8, Pat Farrell wrote: > > I know, this is both a FAQ and an unanswerable question. I'm an old > programmer who has used nearly every editor known to man. I am not a fan of > whole-universe IDEs,

Re: [go-nuts] Re: go language sensitive editor?

On Wed, Nov 21, 2018, 12:37 PM wrote: > I recommend Sublime Text with the GoSublime > addon package. There's a free > trial for Sublime Text . > I started with this, and have also tried AnacondaGo for Sublime, but went back

[go-nuts] Re: go language sensitive editor?

I recommend Sublime Text with the GoSublime addon package. There's a free trial for Sublime Text . -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from

Re: [go-nuts] Re: go language sensitive editor?

I used both VSCode and Intellij/GoLand. I suggest Intellij/GoLand for anything but trivial projects. The refactoring and navigation tools are far superior to those available in VS code, and it makes working in larger projects with lots of dependencies far easier IMO. > On Nov 20, 2018, at 3:15

Re: [go-nuts] Re: go language sensitive editor?

Ed is the standard text editor. -rob On Wed, Nov 21, 2018 at 8:15 AM wrote: > > Another vote for VS Code. I'm a hobbyist and have tried lots of editors. > > On Tuesday, November 20, 2018 at 1:52:11 PM UTC-7, Pat Farrell wrote: >> >> I know, this is both a FAQ and an unanswerable question. I'm

[go-nuts] Re: go language sensitive editor?

Another vote for VS Code. I'm a hobbyist and have tried lots of editors. On Tuesday, November 20, 2018 at 1:52:11 PM UTC-7, Pat Farrell wrote: > > I know, this is both a FAQ and an unanswerable question. I'm an old > programmer who has used nearly every editor known to man. I am not a fan of >