I started with TeXworks (+ XeTeX, which both happen to have been created by Jonathan Kew) and I found no reason to change since then. The only slight drawback is that autocomplete support exists but is rudimentary, however it doesn’t bother me that much.

Which editor do you prefer?

    • scrooge101
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I second this. Getting started started takes some effort, but writing in Neovim is such a joy on its own. Especially implementing comments from other people is much faster and if you use git, you can also easily switch back to earlier versions and/or compare your changes.

  • qwertyasdef@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    MiKTeX, because it’s the first one I stumbled upon in high school and I don’t use LaTeX enough to be bothered to optimize my choice of editor.

  • Remavas@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I myself use TeXStudio with a texlive-full install. I may switch to something else, but currently it is a convenient setup.

  • TruePe4rl
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    3 months ago

    Usually Neovim and :!tectonic main.tex, nothing fancy. For preview ideally Zathura or Preview on Mac.

    Also VSCode is quite usable, since there are some pdf preview plugins.

  • jormaig@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    VS Code with the LaTeX workshop plugin. Works like a charm. You need to have LaTeX installed in your system

  • eyolf@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    TeXStudio for the convenience of compiling and managing multi-file projects; (neo)vim for serious work with the tex files.

  • GarlicToast@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    TexStudio, the multi view and jump to source/output is great on big projects. Zotero macro is very helpful. Compile/clean buttons that also work on multi file projects are huge time savers.

  • Unsafe@discuss.online
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    Nvim. autopair.nvim let’s you autoclose “begin[]” macros. Luasnip let’s you create custom snippets for every macro you use. I also use Emmet LSP for inline svg.