Have you tried gvim? I never liked it and have been using vi for about 40 years now. I fought using it for years and kept using edt (on VMS). I finally gave up when we switched to Unix.

I just tried to install it on my Ubuntu 20 and it failed. Another reason why I think free Linux is overpriced.

sudo apt install vim
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libc6-dbg : Depends: libc6 (= 2.31-0ubuntu9.2) but 2.31-0ubuntu9.1 is to be installed
libc6-dev : Depends: libc6 (= 2.31-0ubuntu9.2) but 2.31-0ubuntu9.1 is to be installed
vim : Depends: vim-runtime (= 2:8.1.2269-1ubuntu5) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

 

Ebacs is written in lisp, a language that allows users of the program to add new code to it. So it is highly customizable. Not that I have ever found time to learn how.

Bob

 

I just tried to install it on my Ubuntu 20 and it failed. Another reason why I think free Linux is overpriced.

I haven't had any problems with Debian or Ubuntu; though I stopped using Ubuntu because Debian seems to be more popular with the SBC's I've been using (Raspberry Pi and C.H.I.P.)

Have you tried the suggestions given?

 

Ebacs is written in lisp, a language that allows users of the program to add new code to it. So it is highly customizable. Not that I have ever found time to learn how.

Bob

Since we’re talking about old editors, anyone use Teco? Used it on DEC systems. It was extensible with macros and I coded a game on it.

 

What is the best editor in peoples opinion and why to edit the text when writing code
Is it best to go for an IDE , with its integrated text editor,
or an IDE with another editor,
or what

I use Visual Studio with Visual GDB, this product is very very good (I'm a professional software developer, trust me I rarely say any software is very very good!).

So we get the huge IDE capability of Visual Studio which includes very powerful debugging tools.

I only use Visual GDB for recreational use though, and I like to use STM32 boards like the Nucleo and so on, but this setup works well for me, very comfortable and no real idiosyncracies, of course I use Visual Studio all the time for work and have used it for decades and I know it well so that helps.

It also has pretty decent Git support but for that I prefer a 3rd part GUI tool SmartGit, superb.

 

A lovely one line answer @bogsort

May be you could expand upon your reasoning for the statement

Could you highlight what you considered un civilised about other editors ?

Emacs is my default editor in Linux and Windows. Emacs was the original integrated editor, aka "editor as an OS". Its longevity and popularity mean that its available on any reasonable Linux system, and since I usually work in Linux, it's a huge win that my default editor is available on pretty much any Linux system I log onto or spin up.

Besides word-class editing features without needing to use a mouse, and syntax-highlighting for every conceivable language and configuration file, (even binary formats), one can manipulate the filesystem, execute and pipe-in the output of system commands, perform arbitrary precision calculations, get the phase of the moon, and innumerable other functions, all from within Emacs. It also includes great macro support, and fully programmable customization (though you have to learn Elisp).

Productive editing is all about muscle memory (if you're using a mouse you're doing it wrong), and Emacs has an awesome set of keybindings, which also align nicely with bash.

I will say that -- out of the box -- Emacs code awareness is not nearly as good or easy to set up as Intellisense in Visual Studio/Visual Code. But Emacs, despite its insane amount of functionality, is so much more lightweight than VS/VC. It takes milliseconds to open an Emacs editor on the terminal.

 

Have you tried the suggestions given?

Sure, it was fruitless, of course. The --fix-broken command gave me the following, and I'm not willing to try the suggested surgery as past experience has shown I may just break something useful.

A copy of the C library was found in an unexpected directory:
'/usr/lib/x86_64-linux-gnu/libc-2.31.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-0ubuntu9.2_amd64.deb (--unpack):
new libc6:amd64 package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/libc6_2.31-0ubuntu9.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Emacs is my default editor in Linux and Windows. Emacs was the original integrated editor, aka "editor as an OS". Its longevity and popularity mean that its available on any reasonable Linux system, and since I usually work in Linux, it's a huge win that my default editor is available on pretty much any Linux system I log onto or spin up.

Besides word-class editing features without needing to use a mouse, and syntax-highlighting for every conceivable language and configuration file, (even binary formats), one can manipulate the filesystem, execute and pipe-in the output of system commands, perform arbitrary precision calculations, get the phase of the moon, and innumerable other functions, all from within Emacs. It also includes great macro support, and fully programmable customization (though you have to learn Elisp).

Productive editing is all about muscle memory (if you're using a mouse you're doing it wrong), and Emacs has an awesome set of keybindings, which also align nicely with bash.

I will say that -- out of the box -- Emacs code awareness is not nearly as good or easy to set up as Intellisense in Visual Studio/Visual Code. But Emacs, despite its insane amount of functionality, is so much more lightweight than VS/VC. It takes milliseconds to open an Emacs editor on the terminal.

If your looking for an all round good code editor that runs on Mac, Linux and Windows and has huge intellisense support for a vast number of languages then "VS Code" is the one to look at.

This is free, because I use Visual Studio for my work I never look at VS Code, but even seasoned developers love it and its free.

 

Emacs is my default editor in Linux and Windows. Emacs was the original integrated editor, aka "editor as an OS". Its longevity and popularity mean that its available on any reasonable Linux system, and since I usually work in Linux, it's a huge win that my default editor is available on pretty much any Linux system I log onto or spin up.

Besides word-class editing features without needing to use a mouse, and syntax-highlighting for every conceivable language and configuration file, (even binary formats), one can manipulate the filesystem, execute and pipe-in the output of system commands, perform arbitrary precision calculations, get the phase of the moon, and innumerable other functions, all from within Emacs. It also includes great macro support, and fully programmable customization (though you have to learn Elisp).

Productive editing is all about muscle memory (if you're using a mouse you're doing it wrong), and Emacs has an awesome set of keybindings, which also align nicely with bash.

I will say that -- out of the box -- Emacs code awareness is not nearly as good or easy to set up as Intellisense in Visual Studio/Visual Code. But Emacs, despite its insane amount of functionality, is so much more lightweight than VS/VC. It takes milliseconds to open an Emacs editor on the terminal.

Thank you @bogosort

a very interesting and elegant report, very interesting,

Personally , I never go handle on emacs or vi, but i used to know many that did,
unfortunately, ret there soul, most have now passed to the great editor debate in the sky.

 

The --fix-broken command gave me the following, and I'm not willing to try the suggested surgery as past experience has shown I may just break something useful.

If you have a broken installation, you need to be willing to fix it.

If you don't want to risk breaking the application that broke your install, you could try moving the offending directory, installing vim, and then moving the directory back.

Another option is to reinstall build-essential. If it complains about the shared library, I'd remove it and let whatever broke your install be broken.

 

Vendor IDE + VSCode