4 ms·

In general: There are a few theoretical advantages when it comes to doing advanced syntax "highlighting". Not that I've seen any GUI IDE/editor ever do syntax h

by phire 5y ago

In general: There are a few theoretical advantages when it comes to doing advanced syntax "highlighting". Not that I've seen any GUI IDE/editor ever do syntax highlighting that couldn't be done in a terminal. There are a few examples in the GUI based disassemblers world (like IDA pro) which use graphical arrows to show where branch/jump instructions goto. The usefulness of those is enough to convince me that perhaps more research needs to be done in this direction. There is also the small advantage of being able to have more than one font type/size on the screen. Your navigator panel can be a smaller font size, Your inline documentation viewer can use a variable-width font. The counter-argument to all that is always: "Is it worth giving up the ability to be used in a terminal to add those few features?" Everything else can be defined as "style" and gets very subjective. nvui looks like it has nice animations and smooth scrolling.

jcelerier 5y ago
> Not that I've seen any GUI IDE/editor ever do syntax highlighting that couldn't be done in a terminal. A very basic feature is that IDEs underlines in yellow for warnings and in red for errors, as well as show fix-it popups when hovering the mouse around the error area I don't believe a terminal can do that while keeping syntax highlighting no ?
- Lio 5y ago
  Many terminals can display coloured undercurls that are different to the current text colour if that's what you mean. E.g. here's a plugin for simple-term to add support for it: https://github.com/hexoctal/st-undercurl https://github.com/hexoctal/st-undercurl The Kitty terminal has all kinds of graphics addons including coloured undercurls and images too: https://sw.kovidgoyal.net/kitty/underlines/ https://sw.kovidgoyal.net/kitty/underlines/ Vim and NeoVim both support coloured undercurls too.
da39a3ee 5y ago
If you run your editor in a terminal, how do you do things like ctrl+click on a compiler error in the terminal and have the file opened in your editor at the correct line?
- bjoli 5y ago
  I focus the interaction window and press the keyboard shortcut for opening the editor at the point of the error? You don't need a mouse to navigate text. I updated some Emacs package recently and now it opens any errors in a list buffer.
- sagarm 5y ago
  People who prefer the terminal don't click on things much. Vanilla Vi users would use :make to populate the location list, and then :cn or :cp to navigate back and forth. :cope to open up the quick fix window where you can use all your regular VI keybindings to navigate. Enter opens the location under the cursor in your previous VIM split. There are also plenty of plugins that add inline diagnostics. It's common to use bindings for navigating these that ape the spell check navigation bindings ]s and [s.
  - da39a3ee 5y ago
    If I'm understanding you correctly that means you have to do your compilation from within vim. Isn't that constraining at times?
    - sagarm 5y ago
      I don't always use :make. Navigating manually is fast: Specific lines is just :NN, jumping to an open buffer is just :b substr<tab><enter>. Or, :tag FunctionName (which has completion) to jump to a symbol. Or, forward incremental search to jump to a string in a file. I also have a plugin to invoke fzf, (\tb to search buffers and \t to search for files by name), but I don't use it that often. VIM has many tools to navigate through text. Everyone's got their own preferred methods.
      - da39a3ee 5y ago
        So if you issue a compile command in a terminal, outside vim, and the compiler emits something like `myfile:17:7` to stdout, how do you then open vim on line 17 of myfile?

by phire 5y ago

jcelerier 5y ago

> Not that I've seen any GUI IDE/editor ever do syntax highlighting that couldn't be done in a terminal. A very basic feature is that IDEs underlines in yellow for warnings and in red for errors, as well as show fix-it popups when hovering the mouse around the error area I don't believe a terminal can do that while keeping syntax highlighting no ?

Lio 5y ago
Many terminals can display coloured undercurls that are different to the current text colour if that's what you mean. E.g. here's a plugin for simple-term to add support for it: https://github.com/hexoctal/st-undercurl https://github.com/hexoctal/st-undercurl The Kitty terminal has all kinds of graphics addons including coloured undercurls and images too: https://sw.kovidgoyal.net/kitty/underlines/ https://sw.kovidgoyal.net/kitty/underlines/ Vim and NeoVim both support coloured undercurls too.

da39a3ee 5y ago

If you run your editor in a terminal, how do you do things like ctrl+click on a compiler error in the terminal and have the file opened in your editor at the correct line?

bjoli 5y ago
I focus the interaction window and press the keyboard shortcut for opening the editor at the point of the error? You don't need a mouse to navigate text. I updated some Emacs package recently and now it opens any errors in a list buffer.
sagarm 5y ago
People who prefer the terminal don't click on things much. Vanilla Vi users would use :make to populate the location list, and then :cn or :cp to navigate back and forth. :cope to open up the quick fix window where you can use all your regular VI keybindings to navigate. Enter opens the location under the cursor in your previous VIM split. There are also plenty of plugins that add inline diagnostics. It's common to use bindings for navigating these that ape the spell check navigation bindings ]s and [s.
- da39a3ee 5y ago
  If I'm understanding you correctly that means you have to do your compilation from within vim. Isn't that constraining at times?
  - sagarm 5y ago
    I don't always use :make. Navigating manually is fast: Specific lines is just :NN, jumping to an open buffer is just :b substr<tab><enter>. Or, :tag FunctionName (which has completion) to jump to a symbol. Or, forward incremental search to jump to a string in a file. I also have a plugin to invoke fzf, (\tb to search buffers and \t to search for files by name), but I don't use it that often. VIM has many tools to navigate through text. Everyone's got their own preferred methods.
    - da39a3ee 5y ago
      So if you issue a compile command in a terminal, outside vim, and the compiler emits something like `myfile:17:7` to stdout, how do you then open vim on line 17 of myfile?