1

I'm working off of a QHD+/WQHD dual monitor setup so nothing Qt powered works for me (TexStudio, TexMaker, etc...)

Does anyone who uses high resolution displays with upscaling know of a robust editor?

Or better yet, some magic trick to get Qt based editors to upscale (there are fixes for the icons but not text AFAIK).

Otherwise, what's the best alternative. I've read a lot about different options but after using primarily TeXWorks, I know what I'd like:

  1. Some sort of basic debugging. Should it really be that difficult for me to find the source of my error when it is just an accidental forgotten }, $, etc...

  2. WYSIWYG. This would be amazing. But as long as point 3 is satisfied, I'll live without.

  3. Faster compiling. My documents take TeXWorks around 30 seconds to render. They are mostly around10 pages. I have an i6 so I can't fathom why it takes so long...

  4. Macro Support. TeXWorks has custom macro support, but I want to make sure your recommendations also have it.

Improve this question
12
  • 2
    Welcome! To be honest, your question isn't very clear as neither of the editors you mention is WYSIWYG. Indeed, I'm not sure what editors would qualify as not even LyX claims this as far as I know. Compiling can't possibly be affected by your display or by your editor. Rendering is a different and quite separate issue. What do you mean by 'macro support'? Note that I don't know anything about the display stuff you're using as that kind of equipment is well beyond my reach: I'm just commenting on the question.
    – cfr
    Oct 21, 2016 at 2:50
  • @cfr I tried to clear up the question a bit. But the post is that Windows has a setting on high resolution monitors to basically magnify everything so that it's not tiny (unscaled text is impossible to read on my monitors). This works for almost every program out there except for those that use the Qt library. Most TeX IDEs are unfortunately Qt based.
    – Jordan Epstein
    Oct 21, 2016 at 3:02
  • @cfr I'm quite ignorant on the topic, but isn't it true that if you do a full compile, then make an edit, and then compile again the second compile can be faster than the first? And thus, if an editor always does a clean compile then it will be slower than if it instead kept some of the temporary files around? I'm just trying to think of a rational explanation for why differences in compilation speeds could potentially differ across editors.
    – scottkosty
    Oct 21, 2016 at 3:10
  • 1
    You haven't explained what you mean by macro support. And those editors are not WYSIWYG, so whatever you mean by that, you need to say. And your documents cannot take longer to compile because of your editor or your display. (Unless the editor simply waits 5 minutes before initiating the command which wouldn't extend the compilation time but might extend the perceive compilation time.) Compilation is not done by your editor and is not something you see. It does not involve rendering anything. Some text is output to the console, so that may be rendered, but it is not your document.
    – cfr
    Oct 21, 2016 at 3:11
  • @scottkosty I feel like that should be the case but it was taking me a weirdly long time on TeXWorks, I thought maybe different IDEs could handle compilation differently.
    – Jordan Epstein
    Oct 21, 2016 at 3:14

1 Answer 1

Reset to default
1

I don't have experience with monitors above HD, but a quick look around shows Emacs to run pretty well on higher resolutions. https://i.stack.imgur.com/c9sGE.jpg Emacs+Auctex takes some time to setup properly in Windows, but once it does, it's arguably one of the best out there. It's not WYSIWYG, but it does have Yasnippet, which allows you to create macros, and also compiles pretty quickly.

Also, take a look at this list: LaTeX Editors/IDEs to see more options.

Any Emacs specific questions, feel free to let me know and I'll do what I can to help.

Improve this answer
2
  • I like emacs so far but damn... can you say steep learning curve? The C-c C-a command lets me view my file at least 10x faster than it did in TeXWorks.
    – Jordan Epstein
    Oct 22, 2016 at 0:04
  • Yup, the learning curve is brutal. But once you get above the first peak, it gets so so so much easier. Take a look at this: tex.stackexchange.com/questions/20843/… for the key commands. The amount of customization available for it is insane as well. When you get a chance, look at Helm, it makes entering commands much quicker/easier, and requires less memorization.
    – Jacob Hoehler
    Oct 22, 2016 at 19:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .