6 ms·

Everything up to and including spell checking, yes. In fact none of those first items are remotely unreasonable to do in a terminal, rather surprising to see th

Everything up to and including spell checking, yes. In fact none of those first items are remotely unreasonable to do in a terminal, rather surprising to see them being used as arguments against the terminal. - vim, neovim, Emacs configured with LSP - https://git-scm.com/ https://git-scm.com/ - http://aspell.net/ http://aspell.net/ - https://github.com/tmux/tmux https://github.com/tmux/tmux - https://github.com/dbcli https://github.com/dbcli Emacs also exists which runs in the terminal mostly (I only miss image rendering personally). Collaborative editing is something I don't do much of but would guess there's a neovim plugin which could be used for backend sync. Interacting with your issue tracker depends on the issue tracker software you use (flat file would work for example, Jira has unofficial clients, etc). - https://www.emacswiki.org/emacs/JiraMode https://www.emacswiki.org/emacs/JiraMode - https://marketplace.atlassian.com/apps/6398/jira-command-line-interface-cli?tab=overview&hosting=cloud https://marketplace.atlassian.com/apps/6398/jira-command-lin...

29athrowaway 4y ago
IntelliJ does all that much better than what any vim plugin can. DataGrip wipes the floor with pgcli How do you find duplicate code with that setup?
- reissbaker 4y ago
  I've used IntelliJ plenty, and it's pretty bad at most of those tasks. Using the git CLI is much better for version control than the Jetbrains GUI wrapper; using Docker itself rather than a wrapper is much better for containers; etc etc. I'm sort of amazed the question of "can you do version control in a terminal" is even being asked... That's where git originated! That's the git team's primary development focus even today! "Can you run multiple static analyzers simultaneously"... That's sort of the point of *nix systems: multiple processes running simultaneously. Using the shell is of course going to allow that, especially with something like tmux! Most of the editor questions were also answered by my original post (and the answer was yes).
  - 29athrowaway 4y ago
    > Using the git CLI is much better for version control than the Jetbrains GUI wrapper For some things. But for reviewing activity in git, and tracking changes across time, doing it in the terminal is unproductive and sucks. (e.g.: 10 levels deep of git blame) > That's sort of the point of *nix systems: multiple processes running simultaneously. Using the shell is of course going to allow that, especially with something like tmux! I meant getting a consolidated list of from them, and also having the ability to run corrective actions. > Most of the editor questions were also answered by my original post (and the answer was yes). Sure, but how much crap do you have to memorize? It's not a unified experience. It's a duct-taped Frankenstein where every subsystem works differently.
    - nequo 4y ago
      >> Using the git CLI is much better for version control than the Jetbrains GUI wrapper > For some things. But for reviewing activity in git, and tracking changes across time, doing it in the terminal is unproductive and sucks. (e.g.: 10 levels deep of git blame) Magit[1] in Emacs is quite okay. It doesn’t feel duct-taped. I haven’t used fugitive[2] in Vim but that’s a thing that exists too. [1] https://magit.vc/ https://magit.vc/ [2] https://github.com/tpope/vim-fugitive https://github.com/tpope/vim-fugitive
      - alwillis 4y ago
        Fugitive is legendary for using Git inside of Vim/Neovim.
    - viraptor 4y ago
      > But for reviewing activity in git, and tracking changes across time, doing it in the terminal is unproductive and sucks tig is great at that. "tig blame" and "," is the way to go for researching the history of some code.
    - reissbaker 4y ago
      Sure, but how much crap do you have to memorize? It's not a unified experience. It's a duct-taped Frankenstein where every subsystem works differently. IDK, my experience with JetBrains is it's leaky abstractions all the way down, outside the core edit/refactor features. Using JetBrains Git without knowing git... I mean, I've seen people do it, but they seem pretty frustrated and confused when things go wrong. I'd rather just learn the underlying tool once, rather than the underlying tool and also the leaky wrapper around it too.
- bananadonkey 4y ago
  I find duplicate code by using a tool such as Sonar for a large codebase, or by reading and knowing the codebase if it is small enough. But I think you mean how do I refactor duplicate code? lsp-mode (https://emacs-lsp.github.io/lsp-mode/page/main-features/ https://emacs-lsp.github.io/lsp-mode/page/main-features/) for smart code navigation or projectile-replace (mentioned in https://with-emacs.com/posts/tutorials/search-and-replacement-techniques/ https://with-emacs.com/posts/tutorials/search-and-replacemen...) for dumb replacements.

29athrowaway 4y ago

IntelliJ does all that much better than what any vim plugin can. DataGrip wipes the floor with pgcli How do you find duplicate code with that setup?

reissbaker 4y ago
I've used IntelliJ plenty, and it's pretty bad at most of those tasks. Using the git CLI is much better for version control than the Jetbrains GUI wrapper; using Docker itself rather than a wrapper is much better for containers; etc etc. I'm sort of amazed the question of "can you do version control in a terminal" is even being asked... That's where git originated! That's the git team's primary development focus even today! "Can you run multiple static analyzers simultaneously"... That's sort of the point of *nix systems: multiple processes running simultaneously. Using the shell is of course going to allow that, especially with something like tmux! Most of the editor questions were also answered by my original post (and the answer was yes).
- 29athrowaway 4y ago
  > Using the git CLI is much better for version control than the Jetbrains GUI wrapper For some things. But for reviewing activity in git, and tracking changes across time, doing it in the terminal is unproductive and sucks. (e.g.: 10 levels deep of git blame) > That's sort of the point of *nix systems: multiple processes running simultaneously. Using the shell is of course going to allow that, especially with something like tmux! I meant getting a consolidated list of from them, and also having the ability to run corrective actions. > Most of the editor questions were also answered by my original post (and the answer was yes). Sure, but how much crap do you have to memorize? It's not a unified experience. It's a duct-taped Frankenstein where every subsystem works differently.
  - nequo 4y ago
    >> Using the git CLI is much better for version control than the Jetbrains GUI wrapper > For some things. But for reviewing activity in git, and tracking changes across time, doing it in the terminal is unproductive and sucks. (e.g.: 10 levels deep of git blame) Magit[1] in Emacs is quite okay. It doesn’t feel duct-taped. I haven’t used fugitive[2] in Vim but that’s a thing that exists too. [1] https://magit.vc/ https://magit.vc/ [2] https://github.com/tpope/vim-fugitive https://github.com/tpope/vim-fugitive
    - alwillis 4y ago
      Fugitive is legendary for using Git inside of Vim/Neovim.
  - viraptor 4y ago
    > But for reviewing activity in git, and tracking changes across time, doing it in the terminal is unproductive and sucks tig is great at that. "tig blame" and "," is the way to go for researching the history of some code.
  - reissbaker 4y ago
    Sure, but how much crap do you have to memorize? It's not a unified experience. It's a duct-taped Frankenstein where every subsystem works differently. IDK, my experience with JetBrains is it's leaky abstractions all the way down, outside the core edit/refactor features. Using JetBrains Git without knowing git... I mean, I've seen people do it, but they seem pretty frustrated and confused when things go wrong. I'd rather just learn the underlying tool once, rather than the underlying tool and also the leaky wrapper around it too.
bananadonkey 4y ago
I find duplicate code by using a tool such as Sonar for a large codebase, or by reading and knowing the codebase if it is small enough. But I think you mean how do I refactor duplicate code? lsp-mode (https://emacs-lsp.github.io/lsp-mode/page/main-features/ https://emacs-lsp.github.io/lsp-mode/page/main-features/) for smart code navigation or projectile-replace (mentioned in https://with-emacs.com/posts/tutorials/search-and-replacement-techniques/ https://with-emacs.com/posts/tutorials/search-and-replacemen...) for dumb replacements.