4 ms·

I still wonder why editors don't understand line numbers on the CLI <editor> file:5 The editor should try to find if 'file:5' exist and open it if so, if it do

• oftenwrong 4y ago
  vim does: vim file +5
  • renox 4y ago
    But compiler error messages are file:5 so this isn't good enough.
    • imran-iq 4y ago
      That's why you have `:make` which uses `errorfmt` to populate your quickfix list, which is covered in the help `:h make`
      • renox 4y ago
        I'm not sure if you're joking or not but if you're not: I usually don't call the compiler from my vim session..
        • imran-iq 4y ago
          Right but if you want to edit and fix files that failed compilation, using `:make` and the quickfix list is the vim way of doing it
• euiq 4y ago
  Visual Studio Code does this (see "File links"): <https://code.visualstudio.com/docs/terminal/basics#_links https://code.visualstudio.com/docs/terminal/basics#_links>
  • renox 4y ago
    I don't think it works from the CLI: code <file>:5 doesn't do what's expected.
    • Measter 4y ago
      You have to use the `-g` command line option: `code -g <file>:<line>`
      • renox 4y ago
        Thanks I didn't know this.
      • 1-more 4y ago
        huge, tysm
• matsemann 4y ago
  JetBrains products do this for lots of stuff if you use the built in terminal to launch stuff or their runner.
• masklinn 4y ago
  > The editor should try to find if 'file:5' exist and open it if so, if it doesn't it should try to open 'foo' and then go to line 5. Opening a file is often done in creation, and `file:5` is a perfectly valid filename, so it's a bit debatable for a default. OTOH in Emacs you should be able to define a find-file-not-found-functions hook[0] and implement whatever fallback you want. I assume `emacs <file>` calls `find-file` after it's initialised the editor itself. [0] https://www.gnu.org/software/emacs/manual/html_node/elisp/Visiting-Functions.html#index-find_002dfile_002dnot_002dfound_002dfunctions https://www.gnu.org/software/emacs/manual/html_node/elisp/Vi...
  • Measter 4y ago
    > Opening a file is often done in creation, and `file:5` is a perfectly valid filename, so it's a bit debatable for a default. It gets even more fun on Windows! Giving a filename of `foo:5` can result in a file called `foo` with an alternate datastream called `5`.
  • renox 4y ago
    > Opening a file is often done in creation, and `file:5` is a perfectly valid filename, so it's a bit debatable for a default You're right, but even as an option I think it'd be nice.
• LtWorf 4y ago
  It works with kwrite/kate/kdevelop.
• yakubin 4y ago
  That works in Emacs compilation buffers. You can also define custom patterns to match the output formats of different compilers.